On Wed, Mar 07, 2012 at 08:03:14PM -0800, Dan Ports wrote:
> It's happening because this port sets python.default_version before
> python.versions rather than after. That seems to be a pretty reasonable
> thing to do (and some 35 other ports do the same thing) so i'd call it
> a bug in the portgrou
On Wed, Mar 07, 2012 at 10:15:26PM -0500, Jeremy Lavergne wrote:
> Does the python 1.0 PortGroup need some more love, or is this specific to
> py-tornado?
It's happening because this port sets python.default_version before
python.versions rather than after. That seems to be a pretty reasonable
th
> It is dependent on py-curl which is not unified and while there is a
> py32-tornado, there is no py32-curl port.
Ah, thanks for the quick find.
smime.p7s
Description: S/MIME cryptographic signature
___
macports-dev mailing list
macports-dev@lists.
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 whil
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::
