Re: Bug#651962: Fwd: Bug#651962: python-argparse redundant?
On 12/14/2011 05:30 PM, Jameson Graef Rollins wrote: > On Wed, 14 Dec 2011 16:43:07 +0900, Arnaud Fontaine 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. signature.asc Description: OpenPGP digital signature
Re: Bug#651962: Fwd: Bug#651962: python-argparse redundant?
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 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. signature.asc Description: OpenPGP digital signature
Re: Bug#651962: Fwd: Bug#651962: python-argparse redundant?
On Saturday, December 17, 2011 04:32:04 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 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. The presumption behind the recommendation is that argparse provided as part of 2.7 makes python-argparse redundant/obsolete. I'm guessing from your comment that's not true? Scott K -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2167612.6NVsPprRkU@scott-latitude-e6320
Re: Bug#651962: Fwd: Bug#651962: python-argparse redundant?
On Dec 17, 2011, at 10:44 AM, Scott Kitterman wrote: >The presumption behind the recommendation is that argparse provided as part >of 2.7 makes python-argparse redundant/obsolete. I'm guessing from your >comment that's not true? It makes it largely unnecessary, but not incompatible (afaik). -Barry -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111217110911.6b1ff...@limelight.wooz.org
Re: Bug#651962: Fwd: Bug#651962: python-argparse redundant?
On 12/17/2011 04:49 PM, Julian Taylor wrote: 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 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. I think it would be easier from the long-term maintenance point of view to use the python-standard-library-argparse. The argparse homepage [1] says "All new development on argparse will continue in the Python repository. Get Python 2.7 or 3.2 for the latest argparse updates!" and also "argparse package ... is based on the python 2.7 stdlib code, backported to older python versions". Pulling in 2.6 because of argparse would of course be bad. Maybe it would be easiest if python2.7 could have Provides:python-argparse. The other way: changing all packages with Depends:python-argparse seems to be much more work. The third option: packaging both, seems to be a duplication of disk-space and packaging time. So I guess that this is a question of finding the easiest way to reduce current and future work. Best, Zbyszek [1] http://code.google.com/p/argparse/ 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. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4eecc341.1070...@in.waw.pl
