[opensuse-packaging] Python 3 porting status
Since several people are now actively involved in porting python packages to python 3, I created a wiki page to keep track of the effort. You can help by filling in the "Unknown" status of most of the packages and adding other repositories. http://en.opensuse.org/openSUSE:Python_3_Status -Todd -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Hi, Le mardi 22 mai 2012, à 15:47 +0200, todd rme a écrit :
Since several people are now actively involved in porting python packages to python 3, I created a wiki page to keep track of the effort. You can help by filling in the "Unknown" status of most of the packages and adding other repositories.
What should we put for modules that won't have a python 3 version? For instance, most of the old GNOME python bindings will never be ported to python 3 because they're using obsolete technologies. Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tue, May 22, 2012 at 4:05 PM, Vincent Untz <vuntz@opensuse.org> wrote:
Hi,
Le mardi 22 mai 2012, à 15:47 +0200, todd rme a écrit :
Since several people are now actively involved in porting python packages to python 3, I created a wiki page to keep track of the effort. You can help by filling in the "Unknown" status of most of the packages and adding other repositories.
What should we put for modules that won't have a python 3 version? For instance, most of the old GNOME python bindings will never be ported to python 3 because they're using obsolete technologies.
Thanks,
Vincent
Probably "Unmaintained", both for those packages and for packages that haven't been developed upstream in a long time. -Todd -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Le mardi 22 mai 2012, à 16:08 +0200, todd rme a écrit :
On Tue, May 22, 2012 at 4:05 PM, Vincent Untz <vuntz@opensuse.org> wrote:
Hi,
Le mardi 22 mai 2012, à 15:47 +0200, todd rme a écrit :
Since several people are now actively involved in porting python packages to python 3, I created a wiki page to keep track of the effort. You can help by filling in the "Unknown" status of most of the packages and adding other repositories.
What should we put for modules that won't have a python 3 version? For instance, most of the old GNOME python bindings will never be ported to python 3 because they're using obsolete technologies.
Thanks,
Vincent
Probably "Unmaintained", both for those packages and for packages that haven't been developed upstream in a long time.
I guess my question was more about green vs red vs orange :-) Anyway, I've updated the page (using green). Cheers, Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 05/22/2012 03:47 PM, todd rme wrote:
Since several people are now actively involved in porting python packages to python 3, I created a wiki page to keep track of the effort. You can help by filling in the "Unknown" status of most of the packages and adding other repositories.
Starting with the latest stable release for python3 maybe is a better idea in the beginning Python 3.2.3 was released on April 10, 2012 but I can only find 3.2.2.99rc2 in the build service Togan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tue, May 22, 2012 at 4:13 PM, Togan Muftuoglu <toganm@opensuse.org> wrote:
On 05/22/2012 03:47 PM, todd rme wrote:
Since several people are now actively involved in porting python packages to python 3, I created a wiki page to keep track of the effort. You can help by filling in the "Unknown" status of most of the packages and adding other repositories.
Starting with the latest stable release for python3 maybe is a better idea in the beginning
Python 3.2.3 was released on April 10, 2012 but I can only find 3.2.2.99rc2 in the build service
Togan
Ideally openSUSE packages should support 3.1 if upstream does, since that is the version that was shipped with openSUSE 11.4. Unfortunately the python 3.1 packages are a little broken so supporting it normally required some hacks, but what is required should be obvious from looking at the existing python 3 packages. -Todd -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 05/22/2012 04:17 PM, todd rme wrote:
On Tue, May 22, 2012 at 4:13 PM, Togan Muftuoglu <toganm@opensuse.org> wrote:
On 05/22/2012 03:47 PM, todd rme wrote:
Since several people are now actively involved in porting python packages to python 3, I created a wiki page to keep track of the effort. You can help by filling in the "Unknown" status of most of the packages and adding other repositories.
Starting with the latest stable release for python3 maybe is a better idea in the beginning
Python 3.2.3 was released on April 10, 2012 but I can only find 3.2.2.99rc2 in the build service
Togan
Ideally openSUSE packages should support 3.1 if upstream does, since that is the version that was shipped with openSUSE 11.4. Unfortunately the python 3.1 packages are a little broken so supporting it normally required some hacks, but what is required should be obvious from looking at the existing python 3 packages.
I guess you are misreading what I meant. Current version of python3 is Python 3.2.3 but openSUSE has 3.2.2.99rc2 (which is a release canditate). Hence all I am suggesting is first make sure that packaged version is in sync with the upstream stable release . Togan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tue, May 22, 2012 at 4:27 PM, Togan Muftuoglu <toganm@opensuse.org> wrote:
On 05/22/2012 04:17 PM, todd rme wrote:
On Tue, May 22, 2012 at 4:13 PM, Togan Muftuoglu <toganm@opensuse.org> wrote:
On 05/22/2012 03:47 PM, todd rme wrote:
Since several people are now actively involved in porting python packages to python 3, I created a wiki page to keep track of the effort. You can help by filling in the "Unknown" status of most of the packages and adding other repositories.
Starting with the latest stable release for python3 maybe is a better idea in the beginning
Python 3.2.3 was released on April 10, 2012 but I can only find 3.2.2.99rc2 in the build service
Togan
Ideally openSUSE packages should support 3.1 if upstream does, since that is the version that was shipped with openSUSE 11.4. Unfortunately the python 3.1 packages are a little broken so supporting it normally required some hacks, but what is required should be obvious from looking at the existing python 3 packages.
I guess you are misreading what I meant. Current version of python3 is Python 3.2.3 but openSUSE has 3.2.2.99rc2 (which is a release canditate). Hence all I am suggesting is first make sure that packaged version is in sync with the upstream stable release .
Togan
python 3.2.3 package was submitted by someone a few days ago, the submission just hasn't been approved yet. That is not something I have control over. -Todd -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tue, May 22, 2012 at 10:47 AM, todd rme <toddrme2178@gmail.com> wrote:
Since several people are now actively involved in porting python packages to python 3, I created a wiki page to keep track of the effort. You can help by filling in the "Unknown" status of most of the packages and adding other repositories.
I have a technical question regarding python3 packaging (and I bet I'm not the only one). I have ipaddr working in py3 (it's just a matter of running it through 2to3). The build could easily be done in the same project, since I could build py2, 2to3, build py3. In fact, there's a hint of that in the wiki about packaging python[0]. However, I'm not sure how to split it into a subpackage. I wouldn't want to make the rpm depend on both python versions), and "%package name" appends a suffix, rather than replacing the name. Is there an example anywhere? Every example I checked uses the method below: The other possibility is to have a python3-ipaddr.spec, and create a link in d:l:p so that python3-ipaddr uses the same sources as python-ipaddr, only it builds the py3k version. That's how jinja2[1] does it (i've been hunting for examples). How do I do that? (a SR to d:l:p wouldn't result in a link, just a separate package). [0] http://en.opensuse.org/openSUSE:Packaging_Python [1] https://build.opensuse.org/package/files?package=python3-Jinja2&project=devel%3Alanguages%3Apython -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
What about pushing some python3 packages into factory, to make python3 in upcoming 12.2 more usefull? Wiki table with list of python3 packages in factory and python packages from factory that need to be built with python3 could be usefull too. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (5)
-
Claudio Freire -
todd rme -
Togan Muftuoglu -
Vincent Untz -
Vitaliy Tomin