On 12/17/2011 04:42 PM, Zbigniew Jędrzejewski-Szmek wrote: > On 12/17/2011 04:32 PM, Julian Taylor wrote: >> On 12/14/2011 05:30 PM, Jameson Graef Rollins wrote: >>> On Wed, 14 Dec 2011 16:43:07 +0900, Arnaud >>> Fontaine<arnau@debian.org> wrote: >>>> About #651962, I guess that something like '<< 2.7' should be >>>> added to >>>> X-Python-Version... >>> >>> Yes, if python-argparse can be used by versions earlier that 2.7, but is >>> incompatible with 2.7 or later, then the dependencies definitely need to >>> reflect that. Thanks. >>> >>> jamie. >> >> in what way is it incompatible with 2.7? >> I have been using it since always with 2.7 and never had any issues >> (besides some pkg-resources warnings one can ignore) >> >> The change of python-argparse to 2.6 only now pulls the 2.6 interpreter >> for every package depending on it for optional 2.6 support (like ipython) >> >> I'd prefer it to have the dependency of argparse reverted to 2.6 | 2.7 >> instead of having to split my packages or ship embedded argparse. >> > It's not incompatible, it's built-in into 2.7, so there's no need to use > the external version with 2.7. > > Zbyszek > then why not keep its depends 2.6 or 2.7. there is no need for it to pull in 2.6 for all its rdepends. also argparse in unstable is newer than that in python 2.7 (1.1 vs 1.2), but I don't know anything important that was fixed in the new version.
Attachment:
signature.asc
Description: OpenPGP digital signature