crankiness in py-tornado

[Frank Schima]

On Mar 7, 2012, at 8:15 PM, Jeremy Lavergne wrote:

> From `port -d livecheck py-tornado` there's a debug blip:
> DEBUG: error during unset trace (options::export): can't unset "PortInfo(replaced_by)": no such element in array can't unset "PortInfo(replaced_by)": no such element in array while executing "unset PortInfo($option)" (procedure "options::export" line 8) invoked from within "$p $optionName delete" 
> 
> I don't see this in other unified ports (e.g. py-xlrd).
> 
> Does the python 1.0 PortGroup need some more love, or is this specific to py-tornado?

It is dependent on py-curl which is not unified and while there is a py32-tornado, there is no py32-curl port. 


Cheers!
Frank