I'd like to suggest a last minute amendment to the Python Policy, that
would help further transitions a lot. I'd suggest that packages uses a
XS-Python-Standards-Version, that would'nt be mandatory for the current
policy but *strongly* advised (a followup on every mass bug could help
here) to u
Le jeu 15 juin 2006 00:00, Peter Samuelson a écrit :
> unblock 373387 by 373628
> thanks
>
> (This block was a false positive. While we use cdbs a little, we
> don't actually use it for anything python-related.)
>
> First, it's not clear to me what advantages anyone would get from
> "fixing" the s
Pierre Habouzit ([EMAIL PROTECTED]):
> I'd like to suggest a last minute amendment to the Python Policy, that
> would help further transitions a lot. I'd suggest that packages uses a
> XS-Python-Standards-Version, that would'nt be mandatory for the current
> policy but *strongly* advised (a foll
Le jeu 15 juin 2006 10:50, Piotr Ozarowski a écrit :
> Pierre Habouzit ([EMAIL PROTECTED]):
> > I'd like to suggest a last minute amendment to the Python Policy,
> > that would help further transitions a lot. I'd suggest that
> > packages uses a XS-Python-Standards-Version, that would'nt be
> > man
Hi all,
Can someone upload the urwid package from the python-modules svn? It
updates to a new upstream and completes the changes needed for the new
python policy.
New upstream tarball is here:
http://excess.org/urwid/urwid-0.9.4.tar.gz
Changelog:
urwid (0.9.4-1) unstable; urgency=low
* New
Pierre Habouzit ([EMAIL PROTECTED]):
> Le jeu 15 juin 2006 10:50, Piotr Ozarowski a écrit :
> > I think a better idea is to use Standards-Version as we did before
> > (version 3.8.0 should be released)
>
> well the thing is there is no way to track all the packages that *have*
> to follow the pyt
Le jeu 15 juin 2006 13:36, Piotr Ozarowski a écrit :
> Pierre Habouzit ([EMAIL PROTECTED]):
> > well the thing is there is no way to track all the packages that
> > *have* to follow the python subpolicy, and that makes the work of
> > tracking them for transition harder.
> >
> > I think/thought it
Pierre Habouzit ([EMAIL PROTECTED]):
> we are not talking about the same target. My goal is to be able to spot
> every package that has to conform to the python subpolicy by just
> listing those fields. Obviously the Standards-Version is bumped also,
> but it's not distinctive of python and not
Currently both tools install into a directory
/
leading to situations like
package foo: /python-foo/same_file.py
package bar: /python-bar/same_file.py
Currently python-support does overwrite these (#373753),
python-central had a bug as well not byte-compiling these.
The intention for pyth
On Thu, 2006-06-15 at 13:44 +0200, Pierre Habouzit wrote:
> Le jeu 15 juin 2006 13:36, Piotr Ozarowski a écrit :
> > Pierre Habouzit ([EMAIL PROTECTED]):
>
> > > well the thing is there is no way to track all the packages that
> > > *have* to follow the python subpolicy, and that makes the work of
On Thu, 2006-06-15 at 09:15 +0200, Pierre Habouzit wrote:
> Le jeu 15 juin 2006 00:00, Peter Samuelson a écrit :
> > unblock 373387 by 373628
> > thanks
> >
> > (This block was a false positive. While we use cdbs a little, we
> > don't actually use it for anything python-related.)
> >
> > First, i
Brown paper bug ... as a workaround, install python2.4, so that both
python2.3 and python2.4 are installed, or install 0.4.17 from
http://people.debian.org/~doko/tmp/python-central_0.4.17_all.deb
or from http://incoming.debian.org/ when it's available there.
Matthias
--
To UNSUBSCRIBE, email
12 matches
Mail list logo
