DPMT and PAPT request

I realize that I've never formally requested addition to DPMT and PAPT. Since I maintain both upstream Python applications and modules, and since I'm on the core Python development team, I would like to request admission to both Debian teams. I'll start off by maintaining the various packages tha

Re: packages that raise string exceptions

[Éric Araujo, 2010-05-28] > Hello > > > Jakub Wilk found the problem and prepared a list of packages affected: > > http://people.debian.org/~jwilk/tmp/string-exceptions.ddlist > > > > anyone volunteers to check them and report bugs? > > Is this specific format used by tools that help with bug re

Re: using experimental as a playground

[Barry Warsaw, 2010-05-28] > On May 28, 2010, at 01:24 PM, Piotr Ożarowski wrote: > > >[Barry Warsaw, 2010-05-28] > >> What I mean is, let's say we have to change something in a helper tool. We > >> want that change to happen at least also in Debian, if not first in Debian, > >> but because of ou

Re: packages that raise string exceptions

On May 28, 2010, at 07:21 PM, Jakub Wilk wrote: >Let's try what says grep on the Lucid's vesrion: > >$ grep -Er "raise\s+[\"']" --include='*.py' bzr-2.1.1/ >bzr-2.1.1/bzrlib/bundle/bundle_data.py:raise 'Value %r has >no colon' % info_item >bzr-2.1.1/bzrlib/tests/test_hooks.py:

Re: packages that raise string exceptions

* Barry Warsaw , 2010-05-28, 13:07: http://people.debian.org/~jwilk/tmp/string-exceptions.ddlist Some of these are surprising (e.g. bzr?! - it has to be Python 2.6 compatible because it comes with Lucid), but they could just be out of date versions. "It works is Ubuntu, so it must be fine" is a

Re: using experimental as a playground

On May 28, 2010, at 01:24 PM, Piotr Ożarowski wrote: >[Barry Warsaw, 2010-05-28] >> What I mean is, let's say we have to change something in a helper tool. We >> want that change to happen at least also in Debian, if not first in Debian, >> but because of our different release cycles, where would

Re: packages that raise string exceptions

On May 28, 2010, at 04:35 PM, Jakub Wilk wrote: >* Barry Warsaw , 2010-05-28, 10:21: >>>Jakub Wilk found the problem and prepared a list of packages affected: >>>http://people.debian.org/~jwilk/tmp/string-exceptions.ddlist >>> >>>anyone volunteers to check them and report bugs? >>> >>>(string exce

Re: packages that raise string exceptions

* Barry Warsaw , 2010-05-28, 10:21: Jakub Wilk found the problem and prepared a list of packages affected: http://people.debian.org/~jwilk/tmp/string-exceptions.ddlist anyone volunteers to check them and report bugs? (string exceptions are not allowed in Python >= 2.6) Some of these are surpr

Re: packages that raise string exceptions

On May 28, 2010, at 01:33 PM, Piotr Ożarowski wrote: >Jakub Wilk found the problem and prepared a list of packages affected: >http://people.debian.org/~jwilk/tmp/string-exceptions.ddlist > >anyone volunteers to check them and report bugs? > >(string exceptions are not allowed in Python >= 2.6) So

Re: packages that raise string exceptions

* Piotr Ożarowski , 2010-05-28, 13:33: Which tests can fail on newer Python versions? I though newer Pythons are backward compatible, except Py3k. They are *mostly* compatible, but they cannot be fully 100% backward compatible. Modules and features go through a well defined deprecation cycle,

Re: packages that raise string exceptions

Hello > Jakub Wilk found the problem and prepared a list of packages affected: > http://people.debian.org/~jwilk/tmp/string-exceptions.ddlist > > anyone volunteers to check them and report bugs? Is this specific format used by tools that help with bug reporting? Regards -- To UNSUBSCRIBE, em

packages that raise string exceptions

[Barry Warsaw, 2010-05-28] > On May 18, 2010, at 11:42 PM, anatoly techtonik wrote: > >Which tests can fail on newer Python versions? I though newer Pythons > >are backward compatible, except Py3k. > > They are *mostly* compatible, but they cannot be fully 100% backward > compatible. Modules and

using experimental as a playground

[Barry Warsaw, 2010-05-28] > What I mean is, let's say we have to change something in a helper tool. We > want that change to happen at least also in Debian, if not first in Debian, > but because of our different release cycles, where would we put it? Ubuntu > already sync's with Debian, but does

Re: PEP 384 (was Re: Bits from dh_python2 author ;-)

[Barry Warsaw, 2010-05-28] > On May 16, 2010, at 02:21 PM, Piotr Ożarowski wrote: > > >What's missing to have full PEP3147 support? > >* PEP 384 implementation (will allow us to share (most?) .so files) > > I have a concern about this. > > While I understand the motivation, I'm not sure implemen

Re: Python versions for Ubuntu 10.10 (Maverick Meerkat)

[Barry Warsaw, 2010-05-28] > On May 23, 2010, at 03:58 PM, Piotr Ożarowski wrote: > >[Barry Warsaw, 2010-05-22] > >[¹] f.e. changes in API, absolute imports in 2.7 would be one of those, > >right now I don't see such changes in 2.7, but I didn't play much > >with it yet > > Contrary to wha