[Pyparsing] pyparsing python2 python3 tarball, future plans

[Julian Taylor]

Hello,
In the 2.0.0 the splitting of the source in two tarballs for python2 and
python3 was troublesome for some distributions, e.g. Debian had to add a
second source package in order to package it.
Now I discovered that in 2.0.1 this splitting was reverted again.

So to avoid unnecessary work in Debian (and all its derivatives) I'd
like to inquire if this same source python2 and python3 tarball is
intended to stay for the foreseeable future or if it might be split
again in the next release.

Best Regards,
Julian Taylor

[Paul McGuire]

[Julian Taylor [mailto:]]

Julian -

No, this is the way things will stay for the foreseeable future. This single
version 2.0.1 and onward works for Python 2.6, 2.7, and 3.x. 1.5.7 is
retained only for versions of Python 2.5 and older.

Thanks for asking!
-- Paul


-----Original Message-----
From: Julian Taylor [mailto:***@googlemail.com]
Sent: Tuesday, August 27, 2013 12:20 PM
To: pyparsing-***@lists.sourceforge.net
Cc: Thomas Goirand
Subject: pyparsing python2 python3 tarball, future plans

Hello,
In the 2.0.0 the splitting of the source in two tarballs for python2 and
python3 was troublesome for some distributions, e.g. Debian had to add a
second source package in order to package it.
Now I discovered that in 2.0.1 this splitting was reverted again.

So to avoid unnecessary work in Debian (and all its derivatives) I'd like to
inquire if this same source python2 and python3 tarball is intended to stay
for the foreseeable future or if it might be split again in the next
release.

Best Regards,
Julian Taylor

[Thomas Goirand]

Post by Julian Taylor
Hello,
In the 2.0.0 the splitting of the source in two tarballs for python2 and
python3 was troublesome for some distributions, e.g. Debian had to add a
second source package in order to package it.

Yes, it was. I had to go through Debian experimental for the upload,
then migrate both packages to SID once the new package was done.

Post by Julian Taylor
Now I discovered that in 2.0.1 this splitting was reverted again.

This is really annoying. I'm not even sure how I will be able to deal
with this, probably I will have to ping the Debian FTP masters, and go
through Experimental once more.

Post by Julian Taylor
So to avoid unnecessary work in Debian (and all its derivatives) I'd
like to inquire if this same source python2 and python3 tarball is
intended to stay for the foreseeable future or if it might be split
again in the next release.

Likewise. I also would recommend that 2 packages are created (and by
that, I mean with 2 different names!!!), as it is very confusing for
everyone. Something like "pyparsing-oldpython" would do, for example.

Anyway, thanks Julian for letting me know. Otherwise, I would have
missed it.

Thomas

[Paul McGuire]

[Thomas Goirand]

Post by Thomas Goirand [mailto:]
Thomas -
Sorry about this inconvenience, I tried my best to maintain cross-version
compatibility overall, but Python3 had just one incompatible syntax
feature too many, forcing me to cut the Gordian Knot.
Assuming that the default Python version installed on Debian is at least
version 2.6, then you should be safe in adopting the version-unified
pyparsing 2.0.1 and beyond, as this version works with Python 2.6 and up
in the 2.x path, and Python 3.0 and up on the 3.x path.

FYI Wheezy has v2.6 & 2.7, and Sid/Jessie only 2.7.

Thomas

[Thomas Goirand [mailto:]]

Thomas -

Sorry about this inconvenience, I tried my best to maintain cross-version
compatibility overall, but Python3 had just one incompatible syntax feature
too many, forcing me to cut the Gordian Knot.

Assuming that the default Python version installed on Debian is at least
version 2.6, then you should be safe in adopting the version-unified
pyparsing 2.0.1 and beyond, as this version works with Python 2.6 and up in
the 2.x path, and Python 3.0 and up on the 3.x path.

I tried to convey this to Julian earlier this week, would you please inform
the rest of the Debian team?

Thanks,
-- Paul



-----Original Message-----
From: Thomas Goirand [mailto:***@debian.org]
Sent: Wednesday, August 28, 2013 2:37 PM
To: Julian Taylor
Cc: pyparsing-***@lists.sourceforge.net
Subject: Re: [Pyparsing] pyparsing python2 python3 tarball, future plans

Post by Julian Taylor
Hello,
In the 2.0.0 the splitting of the source in two tarballs for python2
and
python3 was troublesome for some distributions, e.g. Debian had to add
a second source package in order to package it.

Yes, it was. I had to go through Debian experimental for the upload, then
migrate both packages to SID once the new package was done.

Post by Julian Taylor
Now I discovered that in 2.0.1 this splitting was reverted again.

This is really annoying. I'm not even sure how I will be able to deal with
this, probably I will have to ping the Debian FTP masters, and go through
Experimental once more.

Post by Julian Taylor
So to avoid unnecessary work in Debian (and all its derivatives) I'd
like to inquire if this same source python2 and python3 tarball is
intended to stay for the foreseeable future or if it might be split
again in the next release.

Likewise. I also would recommend that 2 packages are created (and by that, I
mean with 2 different names!!!), as it is very confusing for everyone.
Something like "pyparsing-oldpython" would do, for example.

Anyway, thanks Julian for letting me know. Otherwise, I would have missed
it.

Thomas


----------------------------------------------------------------------------
--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk