Re: [Python-modules-team] Ftputil

2010-09-21 Thread Sandro Tosi
Hello Chris, please leave all the recipients :) On Wed, Sep 22, 2010 at 00:46, Chris wrote: > On Sat, 18 Sep 2010 19:24:47 +0200 > Sandro Tosi wrote: > >> Hello Chris, >> >> On Sat, Sep 18, 2010 at 19:05, Chris wrote: >> > Hi >> > >> > I have put up ftputil. Could a kind soul look it over and p

RFS: python-django-threadedcomments

2010-09-21 Thread Bernhard Reiter
Hello mentors, I am looking for a sponsor for my package "python-django-threadedcomments". Package name: python-django-threadedcomments Version : 0.5.2 Upstream Author : Eric Florenzano URL : http://github.com/ericflo/django-threadedcomments License : BSD Program

Re: Python packaging, dependencies, upstream facilities

2010-09-21 Thread Clint Byrum
On Sep 21, 2010, at 3:26 AM, Piotr Ożarowski wrote: > [Simon McVittie, 2010-09-21] >> On Tue, 21 Sep 2010 at 10:30:33 +0200, Piotr Ożarowski wrote: >>> I see only one sane way to fix the problem - changing Python interpreter >>> to recognize API from filenames, like foo.1.py foo.2.py foo.2.3.py >

RFS: python-django-voting

2010-09-21 Thread Bernhard Reiter
Hello mentors, I am looking for a sponsor for my package "python-django-voting". Package name: python-django-voting Version : 0+svn73 Upstream Author : Jonathan Buchanan URL : http://code.google.com/p/django-voting License : MIT Programming Lang: Python Descripti

Re: Python packaging, dependencies, upstream facilities

2010-09-21 Thread Piotr Ożarowski
[Barry Warsaw, 2010-09-21] > On Sep 21, 2010, at 10:30 AM, Piotr Ożarowski wrote: > >I see only one sane way to fix the problem - changing Python > >interpreter to recognize API from filenames, like foo.1.py foo.2.py > >foo.2.3.py (with `import foo <= 2` as valid syntax) and let upstream > >authors

Re: Python packaging, dependencies, upstream facilities

2010-09-21 Thread Barry Warsaw
On Sep 21, 2010, at 10:30 AM, Piotr Ożarowski wrote: >[Robert Collins, 2010-09-20] >> Path to a solution: use an API marker analgous to the ABI markers C >> libraries have. Incompatible changes to a package bump the package >> *name*. e.g. >> python-zope.publication2.3 to python-zope.publication2.

Re: Fw: Python packaging, dependencies, upstream facilities

2010-09-21 Thread Piotr Ożarowski
[Simon McVittie, 2010-09-21] > On Tue, 21 Sep 2010 at 10:30:33 +0200, Piotr Ożarowski wrote: > > I see only one sane way to fix the problem - changing Python interpreter > > to recognize API from filenames, like foo.1.py foo.2.py foo.2.3.py > > (with `import foo <= 2` as valid syntax) and let upstr

Re: Fw: Python packaging, dependencies, upstream facilities

2010-09-21 Thread Simon McVittie
On Tue, 21 Sep 2010 at 10:30:33 +0200, Piotr Ożarowski wrote: > I'm not sure we should try to solve this. IMHO we should try to convince > upstreams that breaking API/ABI so often is a bad thing instead. ... and that when they do, they need to rename the module with a version number, just like C u

Re: Fw: Python packaging, dependencies, upstream facilities

2010-09-21 Thread Piotr Ożarowski
[Piotr Ożarowski, 2010-09-21] > [Robert Collins, 2010-09-20] > > Path to a solution: use an API marker analgous to the ABI markers C > > libraries have. Incompatible changes to a package bump the package > > *name*. e.g. > > python-zope.publication2.3 to python-zope.publication2.4 > > Compatible ch

Re: Fw: Python packaging, dependencies, upstream facilities

2010-09-21 Thread Piotr Ożarowski
[Robert Collins, 2010-09-20] > Path to a solution: use an API marker analgous to the ABI markers C > libraries have. Incompatible changes to a package bump the package > *name*. e.g. > python-zope.publication2.3 to python-zope.publication2.4 > Compatible changes don't: > python-zope.publication2.3-