On 12/18/2011 04:31 PM, Julian Taylor wrote:
On 12/17/2011 05:28 PM, Zbigniew Jędrzejewski-Szmek wrote:I think it would be easier from the long-term maintenance point of view to use the python-standard-library-argparse.is argparse really such a heavy maintenance package that its unfeasible to just keep it? I'd prefer it to be in the archive for 2.6 _and_ 2.7 until all dependencies have disappeared (which won't happen before 2.6 removal) You can't let python2.7 provide it as packages having 2.7 and 2.6 executables will not run anymore for 2.6 as argparse will never get installed. Using python (>= 2.7) | python-argparse Depends has the same problem.
Right.I see that python-argparse has Provides:python2.7-argparse. Python2.7 could have this too, except that it currently will not change anything.
Given that we have to maintain argparse until 2.6 removal in any case I think the least work solution is to just keep argparse for 2.7 too.
Yes.Note that the separate argparse module will not be used at all with python2.7: '/usr/lib/python2.7' is before '/usr/lib/python2.7/dist-packages' on sys.path.
I'm not sure how much of a problem this will be: we know thatzope will complain (the original bug report), but nothing worse than the occasional warning should happen.
Maybe python-argparse package should be modified to skip installation of the symlinks for python2.7.
Best, Zbyszek