Re: How to properly provide packages for python3.x
* Sandro Tosi , 2010-04-14, 07:20:
I've seen that some modules/extensions are starting to ship
python3- packages, thus allowing to be installed for python3.x
interpreter. Well, I didn't see a discussion about that so I'm
starting one right away.
In particular I'd want to ask:
- was there a discussion and I simply don't remember about it?
I don't think there was.
- do the python helper tools support python3 packages?
python-central seems to have some (at least rudimentary) support for
3.X.
I was told that python-support does not support 3.X (see bug #573560).
- how to do that properly? simply build with python3.x and then ship
the /usr/lib/python3.x/ dir?
s|python3.x|python3.x/dist-packages|
However, that would be wrong for pure-Python modules. If root imports
such a module, it will be byte-compiled, but then *.pyc won't be removed
on purge.
On the other hand, almost the same can be said about modules for 2.X
(even when managed by python-{central,support}): if root imports one
with -O, .pyo will be created but never removed.
- shouldn't we just try to organize how to do that before creating
such packages and then impose their structure/method because "we are
already doing it this way" (in particular because the python
maintainer was the first to ship py3 mod/ext for his packages)?
We should.
--
Jakub Wilk
signature.asc
Description: Digital signature
Re: How to properly provide packages for python3.x
On Apr 14, 2010, at 04:14 PM, Jakub Wilk wrote:
>python-central seems to have some (at least rudimentary) support for
>3.X.
>
>I was told that python-support does not support 3.X (see bug #573560).
I am hoping that none will be necessary. PEP 3147 is very close to acceptance
and merging into the py3k upstream trunk, perhaps as soon as this Friday. Of
course that means that symlink farms will no longer be necessary starting with
Python 3.2, but I would happily back port the essential parts of the patch to
3.1 or even 2.6 and 2.7 if folks here want it, and think it will help. I do
not think it would be difficult, and if it means simplifying Python
installations on Debian, I think it would be a big win.
(For backward compatibility, Pythons < 3.2 would need a -Xcachedir flag to
enable PEP 3147 style pyc files, as specified in the PEP. This means it would
be enabled by default only for system installed Python packages, but that
would still allow us to get rid of the symlink farm for apt packages.)
>>- how to do that properly? simply build with python3.x and then ship
>>the /usr/lib/python3.x/ dir?
>
>s|python3.x|python3.x/dist-packages|
>
>However, that would be wrong for pure-Python modules. If root imports
>such a module, it will be byte-compiled, but then *.pyc won't be removed
>on purge.
>
>On the other hand, almost the same can be said about modules for 2.X
>(even when managed by python-{central,support}): if root imports one
>with -O, .pyo will be created but never removed.
Isn't compileall used to create the pyc files? I think all pyc and pyo files
should be placed on the system by the time the package is installed.
-Barry
signature.asc
Description: PGP signature
RFS: pyamf
Hi mentors, I am looking for a sponsor for my package "pyamf". * Package name: pyamf Version : 0.5.1-1 Upstream Author : The PyAMF Project * URL : http://pyamf.org/ * License : MIT Section : python It builds these binary packages: python-pyamf - Action Message Format support for Python python-pyamf-doc - documentation for the Python AMF support The package appears to be lintian clean. The upload would fix these bugs: 499617 My motivation for maintaining this package is: I'm developing software that Depends on this. I would like to maintain this under Debian Python Modules Team. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/pyamf - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/pyamf/pyamf_0.5.1-1.dsc - Vcs-Svn: svn://svn.debian.org/python-modules/packages/pyamf/trunk/ I would be glad if someone uploaded this package for me. Regards, -- Miguel Landaeta, miguel at miguel.cc secure email with PGP 0x7D8967E9 available at http://keyserver.pgp.com/ "Faith means not wanting to know what is true." -- Nietzsche -- 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/x2h86aeadee1004140905uec35cfc0oc01071f631f37...@mail.gmail.com
Re: How to properly provide packages for python3.x
Le mercredi 14 avril 2010 à 10:29 -0400, Barry Warsaw a écrit : > >I was told that python-support does not support 3.X (see bug #573560). > > I am hoping that none will be necessary. PEP 3147 is very close to acceptance > and merging into the py3k upstream trunk, perhaps as soon as this Friday. Of > course that means that symlink farms will no longer be necessary starting with > Python 3.2, but I would happily back port the essential parts of the patch to > 3.1 or even 2.6 and 2.7 if folks here want it, and think it will help. I do > not think it would be difficult, and if it means simplifying Python > installations on Debian, I think it would be a big win. Even with PEP 3147, a helper is still necessary, at the very least to generate dependencies. Furthermore - unless I’m missing something - this PEP doesn’t say anything about supported Python versions by a given module. So even without a symlink farm, there is at least some magic needed to indicate which versions are supported, maybe in the .py files themselves. Cheers, -- .''`. Josselin Mouette : :' : `. `' “If you behave this way because you are blackmailed by someone, `-[…] I will see what I can do for you.” -- Jörg Schilling signature.asc Description: This is a digitally signed message part
Re: How to properly provide packages for python3.x
On Apr 14, 2010, at 07:01 PM, Josselin Mouette wrote: >Le mercredi 14 avril 2010 à 10:29 -0400, Barry Warsaw a écrit : >> >I was told that python-support does not support 3.X (see bug #573560). >> >> I am hoping that none will be necessary. PEP 3147 is very close to >> acceptance >> and merging into the py3k upstream trunk, perhaps as soon as this Friday. Of >> course that means that symlink farms will no longer be necessary starting >> with >> Python 3.2, but I would happily back port the essential parts of the patch to >> 3.1 or even 2.6 and 2.7 if folks here want it, and think it will help. I do >> not think it would be difficult, and if it means simplifying Python >> installations on Debian, I think it would be a big win. > >Even with PEP 3147, a helper is still necessary, at the very least to >generate dependencies. > >Furthermore - unless I’m missing something - this PEP doesn’t say >anything about supported Python versions by a given module. So even >without a symlink farm, there is at least some magic needed to indicate >which versions are supported, maybe in the .py files themselves. You're right about that. So a helper may still be necessary, but hopefully simpler. Would it make more sense to adapt python-support or python-central or to create a third tool (like we need yet another one :). -Barry signature.asc Description: PGP signature
Re: How to properly provide packages for python3.x
On Wed, Apr 14, 2010 at 07:20:45AM +0200, Sandro Tosi wrote: > Hello, > I've seen that some modules/extensions are starting to ship > python3- packages, thus allowing to be installed for python3.x > interpreter. Well, I didn't see a discussion about that so I'm > starting one right away. > > In particular I'd want to ask: > > - was there a discussion and I simply don't remember about it? > - do the python helper tools support python3 packages? > - how to do that properly? simply build with python3.x and then ship > the /usr/lib/python3.x/ dir? > - shouldn't we just try to organize how to do that before creating > such packages and then impose their structure/method because "we are > already doing it this way" (in particular because the python > maintainer was the first to ship py3 mod/ext for his packages)? The only option for now is to use python-central with DH_PYCENTRAL=nomove. Apart from porting python-apt code to Python 3, this was the only change I had to do. As others already said, it's not possible to do this with python-support due to Bug#573560 which I reported while looking at converting python-apt to python-support, which I tried until I realized that python-support did not meet the requirements of python-apt. -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. pgpuHiWAsikv1.pgp Description: PGP signature
Re: How to properly provide packages for python3.x
[Jakub Wilk, 2010-04-14] > * Sandro Tosi , 2010-04-14, 07:20: >> I've seen that some modules/extensions are starting to ship >> python3- packages, thus allowing to be installed for python3.x >> interpreter. Well, I didn't see a discussion about that so I'm >> starting one right away. >> >> In particular I'd want to ask: >> >> - was there a discussion and I simply don't remember about it? > > I don't think there was. Message-ID: <62993.72.81.252.22.1263573295.squir...@webmail6.pair.com> nobody protested back then (hope it wasn't due to misleading Subject/In-Reply-To headers) >> - do the python helper tools support python3 packages? Few weeks ago I started working on new dh_python that will support PEP3147 (but also python2.X for those who will decide to use my helper tool in Squeeze), but I was slowed down due to personal reasons. Some things changed since my last dh_python mail (due to PEP3147), you can guess some of them from pycompile[1] and pyclean[2] which are mostly ready. Matthias will include them in python package (and backport my tiny py_compile.py change[3] which was accepted upstream (thanks Barry)). [1] http://people.debian.org/~piotr/pycompile [2] http://people.debian.org/~piotr/pyclean [3] http://bugs.python.org/issue8233 >> - how to do that properly? simply build with python3.x and then ship >> the /usr/lib/python3.x/ dir? I hope we'll use /usr/lib/python3/ or paths like: /usr/lib/python3/-3.2/foo /usr/lib/python3/foo/3.2-3.4/bar.py only, but for now[5] the only one that works is: /usr/lib/python3.1/dist-packages/ [4] almost ready in pycompile, still waiting for http://www.python.org/dev/peps/pep-0382/ (and 3147), though I used these maintainer scripts in my python3-sqlalchemy package: http://svn.debian.org/viewsvn/python-modules/packages/sqlalchemy/trunk/debian/python3-sqlalchemy.postinst?revision=12597 http://svn.debian.org/viewsvn/python-modules/packages/sqlalchemy/trunk/debian/python3-sqlalchemy.prerm?revision=12597 unfortunately python3.1 is hardcoded for as it's not in supported versions yet -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 -- 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/20100414192657.gj6...@piotro.eu
Re: How to properly provide packages for python3.x
On Apr 14, 2010, at 09:26 PM, Piotr Ożarowski wrote: >[4] almost ready in pycompile, still waiting for >http://www.python.org/dev/peps/pep-0382/ (and 3147), though PEPs 382 and 384 are next on my list. -Barry signature.asc Description: PGP signature
Re: zynjacku package - build log
* Asheesh Laroia , 2010-04-14, 00:51: Thanks! The package seems pretty good, and I think I will sponsor it. Do you see anything else possibly troublesome as far as its Python packaging? I didn't notice anything unusual. -- Jakub Wilk signature.asc Description: Digital signature
Re: RFS: pyamf
Miguel Landaeta scrisse: > I am looking for a sponsor for my package "pyamf". > [...] > My motivation for maintaining this package is: > I'm developing software that Depends on this. I would like to > maintain this under Debian Python Modules Team. As I was the one who opened the RFP, I'd be glad to sponsor this if nobody step up in some days (but I'd _really_ prefer to have it uploaded by someone inside the DPMT, as I'm not so much skilled in python modules). Ciao, Luca -- .''`. ** Debian GNU/Linux ** | Luca Bruno (kaeso) : :' : The Universal O.S.| lucab (AT) debian.org `. `'` | GPG Key ID: 3BFB9FB3 `- http://www.debian.org | Debian GNU/Linux Developer pgpWGormJIceF.pgp Description: PGP signature
