On 04/set/2012, at 11:51, Joshua Root <[email protected]> wrote: >> Revision: 97362 >> https://trac.macports.org/changeset/97362 >> Author: g5pw at macports.org >> Date: 2012-09-04 01:09:14 -0700 (Tue, 04 Sep 2012) >> Log Message: >> ----------- >> python/py-argparse: >> argparse is compatible with python3, too. >> >> Modified Paths: >> -------------- >> trunk/dports/python/py-argparse/Portfile >> >> Modified: trunk/dports/python/py-argparse/Portfile >> =================================================================== >> --- trunk/dports/python/py-argparse/Portfile 2012-09-04 08:05:49 UTC (rev >> 97361) >> +++ trunk/dports/python/py-argparse/Portfile 2012-09-04 08:09:14 UTC (rev >> 97362) >> @@ -24,7 +24,7 @@ >> checksums rmd160 4ba4f413fab2a5f566b9b9bf1572714cd762fc66 \ >> sha256 >> ddaf4b0a618335a32b6664d4ae038a1de8fbada3b25033f9021510ed2b3941a4 >> >> -python.versions 24 25 26 >> +python.versions 24 25 26 27 31 32 > > But as it says in the description, this is a backport from the Python > 2.7 standard library. There is literally no point having this as a port > for python >= 2.7. (Actually I'm not sure about 3.1, but certainly > 2.7/3.2+.)
Ah, you're right! actually, i modified it as a dependency of skypipe, but now I see that it's completely unnecessary. Feel free to rollback, I'll patch the skypipe requirements to ignore argparse. > > - Josh Aljaž Srebrnič -- -- My public key: http://bit.ly/g5pw_pubkey _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
