Marc Dequènes wrote:
> As you may have heard, Python packaging is moving fast these days. We
> plan the move the current Python version to 2.4 and in the same time
> are drafting a new policy and creating new tools to greatly improve
> the current situation. All this leads to the need for a newer c
Raphael Hertzog writes:
> On Tue, 13 Jun 2006, Marc Dequènes wrote:
> > Coin,
> [...]
> > You can find the current class here :
> > http://perso.duckcorp.org/duck/soya-new-policy/
>
> Some things to fix:
> > cdbs_python_build_versions := $(patsubst python%, %, $(shell pyversions -r
> > debian/
On Tue, 13 Jun 2006, Marc Dequènes wrote:
> Coin,
[...]
> You can find the current class here :
> http://perso.duckcorp.org/duck/soya-new-policy/
Some things to fix:
> cdbs_python_build_versions := $(patsubst python%, %, $(shell pyversions -r
> debian/control | grep -E "^python[0-9.]+( python[
Hi,
> > 1. It won't build under python2.4. I have fixes for this that I haven't
> >uploaded (and that need some more testing and tidying up).
>
> You may still ask for help.
This will be easy enough to have ready by the time 2.3 is removed, which
I'm assuming is not happening tomorrow. Wh
Coin,
Ben Burton <[EMAIL PROTECTED]> writes:
> For reference, decompyle still needs python2.3. There are two issues:
>
> 1. It won't build under python2.4. I have fixes for this that I haven't
>uploaded (and that need some more testing and tidying up).
You may still ask for help.
> 2. It
Coin,
As you may have heard, Python packaging is moving fast these days. We
plan the move the current Python version to 2.4 and in the same time are
drafting a new policy and creating new tools to greatly improve the
current situation. All this leads to the need for a newer class, which
will at t
Hi,
> With the upcoming releases of the last packages which
> didn't support 2.4 yet (Plone on the Zope application server) we may
> be able to drop support for 2.3 in sid and etch as well.
For reference, decompyle still needs python2.3. There are two issues:
1. It won't build under python2.4.
Coin,
Raphael Hertzog <[EMAIL PROTECTED]> writes:
> Now it's time to ask all maintainers to update their packages. Someone
> should prepare several list of source packages:
> - python extensions
> - python modules only
> - python apps
Fact is python-support is not yet ready for extensions, and
On Tue, 2006-06-13 at 01:14 +0200, Matthias Klose wrote:
> Joe Wreschnig writes:
> > I have updated the Python policy document based on the discussions on
> > the list. An updated DebianDoc (and HTML and text files) can be found at
> > http://people.debian.org/~piman/python-policy/.
> >
> > It:
>
Hi,
I've prepared this:
http://wiki.debian.org/DebianPython/NewPolicy
Feel free to enhance.
I also converted python-pam as an example (std debhelper package):
http://people.debian.org/~hertzog/python/examples/
I'll gladly put other examples packages at the same place. Just send them
to me.
Now
Joe Wreschnig writes:
> I have updated the Python policy document based on the discussions on
> the list. An updated DebianDoc (and HTML and text files) can be found at
> http://people.debian.org/~piman/python-policy/.
>
> It:
> 0) Removes a lot of cruft/debate from the document itself
> 1) Expl
Zack Weinberg writes:
> Since Python policy is being revamped just now I thought I'd bring up
> a complicated situation that I ran across recently (in packages that
> are currently just for private use, but I might try to get them into
> Debian eventually).
>
> Consider a source package that build
Since Python policy is being revamped just now I thought I'd bring up
a complicated situation that I ran across recently (in packages that
are currently just for private use, but I might try to get them into
Debian eventually).
Consider a source package that builds a shared library, Python
bindin
Raphael Hertzog writes:
> On Mon, 12 Jun 2006, Joe Wreschnig wrote:
> > > > - python (>= 2.3.5-7) (for pyversions script)
> >
> > Okay, I've updated the policy document to use that version in the Build
> > Dependencies section.
>
> Which is only really needed for extensions. Modules don't need mo
On Mon, 12 Jun 2006, Joe Wreschnig wrote:
> > > - python (>= 2.3.5-7) (for pyversions script)
>
> Okay, I've updated the policy document to use that version in the Build
> Dependencies section.
Which is only really needed for extensions. Modules don't need more than
an unversioned dependency on p
On Mon, 2006-06-12 at 12:25 -0700, Steve Langasek wrote:
> On Mon, Jun 12, 2006 at 09:06:43PM +0200, Raphael Hertzog wrote:
> > On Mon, 12 Jun 2006, Raphael Hertzog wrote:
> > > On Mon, 12 Jun 2006, Raphael Hertzog wrote:
> > > > I would love to have this fixed by today's dinstall. That's why I
> >
On Mon, Jun 12, 2006 at 09:06:43PM +0200, Raphael Hertzog wrote:
> On Mon, 12 Jun 2006, Raphael Hertzog wrote:
> > On Mon, 12 Jun 2006, Raphael Hertzog wrote:
> > > I would love to have this fixed by today's dinstall. That's why I
> > > prepared the attached NMU, please just send an OK and I'll upl
On Mon, 12 Jun 2006, Raphael Hertzog wrote:
> On Mon, 12 Jun 2006, Raphael Hertzog wrote:
> > I would love to have this fixed by today's dinstall. That's why I
> > prepared the attached NMU, please just send an OK and I'll upload it (of
> > course, feel free to do it yourself in a maintainer upload
On Mon, 2006-06-12 at 17:08 +0300, Juha-Matti Tapio wrote:
> On Mon, Jun 12, 2006 at 09:20:13AM +0200, Raphael Hertzog wrote:
> > /usr/lib/site-python is on the sys.path of all python versions so we must
> > make sure to provide the best (ie .py with working .pyc) for all python
> > versions.
>
>
On Mon, 12 Jun 2006, Juha-Matti Tapio wrote:
> On Mon, Jun 12, 2006 at 09:20:13AM +0200, Raphael Hertzog wrote:
> > /usr/lib/site-python is on the sys.path of all python versions so we must
> > make sure to provide the best (ie .py with working .pyc) for all python
> > versions.
>
> Why "must"?
On Mon, Jun 12, 2006 at 09:20:13AM +0200, Raphael Hertzog wrote:
> /usr/lib/site-python is on the sys.path of all python versions so we must
> make sure to provide the best (ie .py with working .pyc) for all python
> versions.
Why "must"?
Has this for some reason become a problem just recently o
Coin,
Matthias Klose <[EMAIL PROTECTED]> writes:
>> How about adding example for building compiled extensions? Otherwise
>> there will be used many ways to produce binaries for all supported
>> python versions.
>
> - Packaging examples
>- CDBS (not yet available)
A packaging example can be
Hi
On Mon, 12 Jun 2006 13:18:53 +0200
Raphael Hertzog <[EMAIL PROTECTED]> wrote:
> In the mean time, I can tell you that you will have to Build-Depends on
> "python (>= 2.3.5-6), python-all-dev" and that you should use `pyversions
> -r debian/control` to find out the list of python versions that
Hi
no need to CC me...
On Mon, 12 Jun 2006 12:34:18 +0200
Matthias Klose <[EMAIL PROTECTED]> wrote:
> - Packaging examples
>- CDBS (not yet available)
>- python-central
> (http://python-modules.alioth.debian.org/python-central_howto.txt)
>- python-support (http://wiki.debian.org/De
Coin,
Raphael Hertzog <[EMAIL PROTECTED]> writes:
> Without any answer from you, I might upload it right before dinstall
> (depending on the opinion of other involved people).
This is perfectly reasonnable.
--
Marc Dequènes (Duck)
pgpU3t0AM8OF7.pgp
Description: PGP signature
Hi,
On Mon, 12 Jun 2006, Michal Čihař wrote:
> On Mon, 12 Jun 2006 02:29:51 -0500
> Joe Wreschnig <[EMAIL PROTECTED]> wrote:
>
> > I have updated the Python policy document based on the discussions on
> > the list. An updated DebianDoc (and HTML and text files) can be found at
> > http://people.d
On Mon, 12 Jun 2006, Raphael Hertzog wrote:
> On Mon, 12 Jun 2006, Raphael Hertzog wrote:
> > I would love to have this fixed by today's dinstall. That's why I
> > prepared the attached NMU, please just send an OK and I'll upload it (of
> > course, feel free to do it yourself in a maintainer upload
> How about adding example for building compiled extensions? Otherwise
> there will be used many ways to produce binaries for all supported
> python versions.
- Packaging examples
- CDBS (not yet available)
- python-central
(http://python-modules.alioth.debian.org/python-central_howto.txt)
Hi
On Mon, 12 Jun 2006 02:29:51 -0500
Joe Wreschnig <[EMAIL PROTECTED]> wrote:
> I have updated the Python policy document based on the discussions on
> the list. An updated DebianDoc (and HTML and text files) can be found at
> http://people.debian.org/~piman/python-policy/.
How about adding exa
Piotr Ozarowski writes:
> What about an Egg support? I think it's worth mentioning in policy
>
> I'm talking about:
> * --single-version-externally-managed parameter passed to
> `setup.py install` or DEB_PYTHON_INSTALL_ARGS_ALL (CDBS)
> * Egg's dirname's issue (python's/module's version in dirna
On Mon, 12 Jun 2006, Raphael Hertzog wrote:
> I would love to have this fixed by today's dinstall. That's why I
> prepared the attached NMU, please just send an OK and I'll upload it (of
> course, feel free to do it yourself in a maintainer upload).
>
> Without any answer from you, I might upload
Joe Wreschnig ([EMAIL PROTECTED]):
> I have updated the Python policy document based on the discussions on
> the list. An updated DebianDoc (and HTML and text files) can be found at
> http://people.debian.org/~piman/python-policy/.
great work!
[...]
> It does not:
> 1) Cover CDBS, since I don't
I have updated the Python policy document based on the discussions on
the list. An updated DebianDoc (and HTML and text files) can be found at
http://people.debian.org/~piman/python-policy/.
It:
0) Removes a lot of cruft/debate from the document itself
1) Explains X*-Python-Version
2) Explains
On Mon, 12 Jun 2006, Alexandre Fayolle wrote:
> > Since this directory is in sys.path of all python versions, if we
> > byte-compile those in-place for the current version, then the modules
> > won't work with other python versions.
>
> This just not true. Python is smart enough not to use the .py
34 matches
Mail list logo
