RFC/RFS: python-enchant -- spellchecking library for Python

2006-04-12 Thread Piotr Ozarowski
I'm looking for a sponsor for python-enchant (ITP #299783).
Package is lintian/linda clean and builds in pbuilder.

* Package name: python-enchant
  Version : 1.1.5
  Upstream Author : Ryan Kelly [EMAIL PROTECTED]
* URL : http://pyenchant.sourceforge.net/
* License : LGPL with a special exception to link to non-free
spell checker backend (e.g. Microsoft Office
spell checker)
  Description : spellchecking library for Python
 
PyEnchant consists of Python binding to Enchant spellchecking
library and some wrapper classes. It includes all the functionality
of Enchant in Pythonic object-oriented interface, and also provides
some higher-level functionality than is available in the C API.


I have also updated my gaupol package, so now it recommends
python2.4-enchant

Both packages can be downloaded from: http://debian.pox.one.pl/

BTW: I have permission to take over from Seo Sanghyeon
-- 
-=[ Piotr Ozarowski ]=-
-=[ http://www.ozarowski.pl ]=-


pgpAlGbfoH9Hq.pgp
Description: PGP signature


Re: Python 2.1/2.2 removal; Python 2.4 as default

2006-04-12 Thread Raphael Hertzog
On Wed, 12 Apr 2006, Matthias Klose wrote:
 ok, I did run out of time last weekend, however python2.5,
 python2.3-doc, python2.4-doc are in NEW. According your logic about
 vacation times, the change of the default version probably should not
 be done before Easter.

Easter is 4 days or a full week for some: nothing problematic. Please go
ahead with the python 2.4 change ASAP.

 Unfortunately FTP masters did reject the Zope2.x upload, which uses
 python2.4. Any reasons for that? Zope2.7 already was scheduled for
 removal.

I'm not ftpmaster so I can't comment, but usually they give a reason in
the rejection notice... what did it say ?

Cheers,
-- 
Raphaël Hertzog

Premier livre français sur Debian GNU/Linux :
http://www.ouaza.com/livre/admin-debian/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



python-mysqldb in the Maintaince team

2006-04-12 Thread Jonas Meurer
hello,

i like the idea of a python modules packaging team, thus i'dd like to
add python-mysqldb to the svn repository and co-maintain it within the
team.

please add me (mejo) to the alioth project.

...
 jonas


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Please add me to Python Modules Team

2006-04-12 Thread Ganesan Rajagopal

Hi,

I currently maintain clientcookie, fixedpoint and ctypes python packages. I
am not subscribed to debian-python list but I am already subscribed to the
corresponding newsgroup in gmane.

Ganesan

-- 
Ganesan Rajagopal (rganesan at debian.org) | GPG Key: 1024D/5D8C12EA
Web: http://employees.org/~rganesan| http://rganesan.blogspot.com



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Please add me to Python Modules Team

2006-04-12 Thread Raphael Hertzog
Hi,

On Wed, 12 Apr 2006, Ganesan Rajagopal wrote:
 I currently maintain clientcookie, fixedpoint and ctypes python packages. I
 am not subscribed to debian-python list but I am already subscribed to the
 corresponding newsgroup in gmane.

User rganesan has been added to the project. You will have commit rights
tomorrow.

Cheers,
-- 
Raphaël Hertzog

Premier livre français sur Debian GNU/Linux :
http://www.ouaza.com/livre/admin-debian/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: python-mysqldb in the Maintaince team

2006-04-12 Thread Raphael Hertzog
Hi,

On Wed, 12 Apr 2006, Jonas Meurer wrote:
 i like the idea of a python modules packaging team, thus i'dd like to
 add python-mysqldb to the svn repository and co-maintain it within the
 team.
 
 please add me (mejo) to the alioth project.

Done. You will have commit rights tomorrow.
Welcome to the group!

Cheers,
-- 
Raphaël Hertzog

Premier livre français sur Debian GNU/Linux :
http://www.ouaza.com/livre/admin-debian/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Modules Team

2006-04-12 Thread Norbert Tretkowski
Hi,

I'm maintaining ipython, and I'd like the idea of a Python Modules
Team. Please add me (nobse) to the project on alioth.

Norbert


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Modules Team

2006-04-12 Thread Raphael Hertzog
Hi,

On Wed, 12 Apr 2006, Norbert Tretkowski wrote:
 I'm maintaining ipython, and I'd like the idea of a Python Modules
 Team. Please add me (nobse) to the project on alioth.

Done. You will have commit rights tomorrow.
Welcome to the group!

Cheers,
-- 
Raphaël Hertzog

Premier livre français sur Debian GNU/Linux :
http://www.ouaza.com/livre/admin-debian/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: New python maintenance team

2006-04-12 Thread Bob Tanner
Raphael Hertzog wrote:

 But I would really like turbogears maintained within python-modules
 since it's mainly good glue between several general-purpose Python
 modules.
 
 (But it's up to you in the end.)

Let's merge the projects.

There is only 3 of us and I think it would be best to be part of a large
project.


-- 
Bob Tanner [EMAIL PROTECTED]  | Phone : (952)943-8700
http://www.real-time.com, Minnesota, Linux | Fax   : (952)943-8500
Key fingerprint = AB15 0BDF BCDE 4369 5B42  1973 7CF1 A709 2CC1 B288


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: how to make python package binNMU-safe [Bug#361940: python-mysqldb: can't be binNMUed due to arch: all - arch: any dep]

2006-04-12 Thread Raphael Hertzog
Hi,

We discussed that on IRC, I'll just post a quick summary:

On Wed, 12 Apr 2006, Jonas Meurer wrote:
 i got the following bugreport, and i'm not sure about the best way to fix
 it. the problem is obvious: python-mysqldb depends on python2.3-mysqldb
 (= 1.2.1c3-6), but after a binNMU of python2.3-mysqldb it is version
 1.2.1c3-6+b1.
 
 so three solutions spring into my mind:
 - relax the dependency to python2.3-mysqldb (= 1.2.1c3-6)

Or simply depend on python2.3-mysqldb (without any version specified). The
main point of the dependency is to install python2.4-mysql automatically
when python2.4 will become the default version. The goal is not to ensure
that the latest version of the corresponding package is installed since an
upgrade will upgrade both at the same time anyway.

 - drop pythonX.Y-mysqldb packages, provide one python-mysqldb package
   for all python versions. i'm not sure whether this is possible at all.

Not sure... and the python policy is kind of not finished. But it seems
to make sense for me for some very small modules.

http://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-all_versions

The policy says it's not yet supported and describes this the follwing
way:

 You have a version independent Python module. Create a single package
 python-foo that has a dependency

  Depends: python

 It should install modules somewhere inside
 /usr/lib/python/site-packages/ and use #!/usr/bin/python for
 programs. The postinst script should create symlinks in all
 /usr/lib/pythonX.Y/site-packages/ directories that point to its
 /usr/lib/python/site-packages/ files and compile them. 

Cheers,
-- 
Raphaël Hertzog

Premier livre français sur Debian GNU/Linux :
http://www.ouaza.com/livre/admin-debian/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: New python maintenance team

2006-04-12 Thread Raphael Hertzog
On Wed, 12 Apr 2006, Bob Tanner wrote:
  But I would really like turbogears maintained within python-modules
  since it's mainly good glue between several general-purpose Python
  modules.
  
  (But it's up to you in the end.)
 
 Let's merge the projects.
 
 There is only 3 of us and I think it would be best to be part of a large
 project.

Indeed. I added the 3 members of pkg-turbogears in the python-modules
alioth project. Let's go for it!

(Please request the removal of pkg-turbogears on alioth once you don't
need it any more)

Cheers,
-- 
Raphaël Hertzog

Premier livre français sur Debian GNU/Linux :
http://www.ouaza.com/livre/admin-debian/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: how to make python package binNMU-safe [Bug#361940: python-mysqldb: can't be binNMUed due to arch: all - arch: any dep]

2006-04-12 Thread Sanghyeon Seo
Jonas Meurer wrote:
 - drop pythonX.Y-mysqldb packages, provide one python-mysqldb package
   for all python versions. i'm not sure whether this is possible at all.

Raphael Hertzog wrote:
 Not sure... and the python policy is kind of not finished. But it seems
 to make sense for me for some very small modules.

 http://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-all_versions

 The policy says it's not yet supported and describes this the follwing
 way:

  You have a version independent Python module. Create a single package
  python-foo that has a dependency

   Depends: python

  It should install modules somewhere inside
  /usr/lib/python/site-packages/ and use #!/usr/bin/python for
  programs. The postinst script should create symlinks in all
  /usr/lib/pythonX.Y/site-packages/ directories that point to its
  /usr/lib/python/site-packages/ files and compile them.

You can do this with python-support today. See python-cherrypy package
for an example.

Depends: python (= 2.3), python ( 2.5)
Declare the minimum supported Python version.

Package installs to /usr/share/python-support/$PACKAGENAME.
postinst calls update-python-modules, which will bytecompile Python
sources to /var/lib/python-support/$PYTHONVERSION for each Python
versions installed. Instead of symlinking, python-support.pth, path
configuration files are placed by python-support package, which extends
Python's module search path.

Path configuration file is documented here:
http://docs.python.org/lib/module-site.html

Seo Sanghyeon



Re: how to make python package binNMU-safe [Bug#361940: python-mysqldb: can't be binNMUed due to arch: all - arch: any dep]

2006-04-12 Thread Raphael Hertzog
On Thu, 13 Apr 2006, Sanghyeon Seo wrote:
   It should install modules somewhere inside
   /usr/lib/python/site-packages/ and use #!/usr/bin/python for
   programs. The postinst script should create symlinks in all
   /usr/lib/pythonX.Y/site-packages/ directories that point to its
   /usr/lib/python/site-packages/ files and compile them.
 
 You can do this with python-support today. See python-cherrypy package
 for an example.

Interesting, but I think this will not work out of the box for packages
that should provide Python eggs. 

I just checked python-cherrypy and I noticed that it only provides
/usr/share/python-support/cherrypy/CherryPy-2.1.1-py2.3.egg-info
(there's no egg for python 2.4 version). It should provide both.

Any idea on how to nicely fix that ?

Cheers,
-- 
Raphaël Hertzog

Premier livre français sur Debian GNU/Linux :
http://www.ouaza.com/livre/admin-debian/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Python 2.1/2.2 removal; Python 2.4 as default

2006-04-12 Thread Jeroen van Wolffelaar
On Wed, Apr 12, 2006 at 04:33:35PM +0200, Matthias Klose wrote:
 Jeroen van Wolffelaar writes:
  On Wed, Apr 12, 2006 at 12:41:13AM +0200, Jeroen van Wolffelaar wrote:
   So, because there were no objections to the python 2.1/2.2 removal,
   I'll be proceeding with that.
  
  Done now, I'd like to announce this, together with some warning about
  default python version changes, if they're going to happen soon (best to
  not to have multiple separate announcements if they can be joined).
  It'll be a bit (about 24h) before a dropped python2.1  python2.2 will
  reach the mirrors, and impact should be reasonably limited, so otoh, it
  isn't totally required.
  
  So, any opinion on the -defaults change, esp. from Matthias of course,
  is very welcomed.
 
 ok, I did run out of time last weekend, however python2.5,
 python2.3-doc, python2.4-doc are in NEW.

Cool

 According your logic about vacation times, the change of the default
 version probably should not be done before Easter.

I don't know, while some people (including, at least, myself) will be
unavailable during Easter to do any Debian work, others might rather
have lots of time because of it being a holiday and no daytime job being
in the way. Having this change done before easter will leverage both
groups of people.

But I don't care about the exact timing, but I do think we should really
do this sooner rather than later, to get things going. Therefore, I'd
like to urge you to simply do the move, and have anyone interested help
out fixing up all the packages that get broken by it and need an update.

 Unfortunately FTP masters did reject the Zope2.x upload, which uses
 python2.4. Any reasons for that? Zope2.7 already was scheduled for
 removal.

Can you please be more specific? And/or reply to the REJECT mail, as it
states at the bottom of every reject? That way, all the info is at hand
for us ftp-people to look into it. I can't find any NEW reject for
zope2.anything during the whole of 2006. At least listing the exact
filename of the .changes is already very useful to find the upload
you're talking about.

--Jeroen

-- 
Jeroen van Wolffelaar
[EMAIL PROTECTED] (also for Jabber  MSN; ICQ: 33944357)
http://Jeroen.A-Eskwadraat.nl


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Python 2.1/2.2 removal; Python 2.4 as default

2006-04-12 Thread Matthias Klose
Jeroen van Wolffelaar writes:
  Unfortunately FTP masters did reject the Zope2.x upload, which uses
  python2.4. Any reasons for that? Zope2.7 already was scheduled for
  removal.
 
 Can you please be more specific? And/or reply to the REJECT mail, as it
 states at the bottom of every reject? That way, all the info is at hand
 for us ftp-people to look into it. I can't find any NEW reject for
 zope2.anything during the whole of 2006. At least listing the exact
 filename of the .changes is already very useful to find the upload
 you're talking about.

CC'ing Fabio, AFAIK that was a zope2.9 upload. Maybe it would be
better, if FTP masters send the reject mail to the Maintainer address,
not the uploader address?

  Matthias


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Python 2.1/2.2 removal; Python 2.4 as default

2006-04-12 Thread Jeroen van Wolffelaar
On Wed, Apr 12, 2006 at 10:32:28PM +0200, Matthias Klose wrote:
 Jeroen van Wolffelaar writes:
   Unfortunately FTP masters did reject the Zope2.x upload, which uses
   python2.4. Any reasons for that? Zope2.7 already was scheduled for
   removal.
  
  Can you please be more specific? And/or reply to the REJECT mail, as it
  states at the bottom of every reject? That way, all the info is at hand
  for us ftp-people to look into it. I can't find any NEW reject for
  zope2.anything during the whole of 2006. At least listing the exact
  filename of the .changes is already very useful to find the upload
  you're talking about.
 
 CC'ing Fabio, AFAIK that was a zope2.9 upload. Maybe it would be
 better, if FTP masters send the reject mail to the Maintainer address,
 not the uploader address?

zope2.9 is simply still sitting in NEW, and is not rejected. I see there
was a clarification requested over the weekend about the big number of
zope versions in the archive (2.9 would be the 4th), and Fabio replied.
This was two days ago, nothing happened since as far as I can see, so
I'd advice to just wait a bit. Fwiw, I don't see a zope2.7 removal
request yet, but maybe I'm looking wrongly?

About who to inform, typically there isn't a maintainer yet for packages
in NEW, so it's a bit tricky. The actual maintainer is only available
after a package is installed, because it's not in the .changes. In most
cases it doesn't matter (uploader  maintainer same person), so while I
agree better notification might be worthwhile, it's also not terribly
high on my list of things to look into.

--Jeroen

-- 
Jeroen van Wolffelaar
[EMAIL PROTECTED] (also for Jabber  MSN; ICQ: 33944357)
http://Jeroen.A-Eskwadraat.nl


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: New python maintenance team

2006-04-12 Thread Bob Tanner
Raphael Hertzog wrote:

 (Please request the removal of pkg-turbogears on alioth once you don't
 need it any more)
 

Waiting on confirmation and then I'll submit the remove request.
-- 
Bob Tanner [EMAIL PROTECTED]  | Phone : (952)943-8700
http://www.real-time.com, Minnesota, Linux | Fax   : (952)943-8500
Key fingerprint = AB15 0BDF BCDE 4369 5B42  1973 7CF1 A709 2CC1 B288


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: New python maintenance team

2006-04-12 Thread Gustavo Franco
On 4/12/06, Bob Tanner [EMAIL PROTECTED] wrote:
 Raphael Hertzog wrote:

  (Please request the removal of pkg-turbogears on alioth once you don't
  need it any more)
 

 Waiting on confirmation and then I'll submit the remove request.

Please, move cherrypy from pkg-turbogears svn repository first. :-)

Thanks,
-- stratus



Joining the python modules team

2006-04-12 Thread Jan Lübbe
Hi!

I'm currently in the NM-Process and maintain the packages python-pysnmp2
and pida. I'd like to join the python-modules team to help with
comaintaining the packages.

My alioth login is jluebbe-guest.

-- 
Jan Lübbe [EMAIL PROTECTED]http://sicherheitsschwankung.de
 gpg-key  1024D/D8480F2E 2002-03-20
 fingerprint  1B25 F91F 9E7B 5D4F 1282  02D6 8A83 8BE4 D848 0F2E



Joining the Python modules team

2006-04-12 Thread Torsten Marek
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

I'd like to join, too. Please add my account (shlomme).
I bring in ElementTree, cElementTree and ElementTidy (currently in the NEW 
queue).

best,

Torsten
- --
Torsten Marek [EMAIL PROTECTED]
ID: A244C858 -- FP: 1902 0002 5DFC 856B F146  894C 7CC5 451E A244 C858
Keyserver: subkeys.pgp.net

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEPX5rfMVFHqJEyFgRAtyPAJ0fFQmak8n5DGQPjQA7TGJmbvLMsQCfT2HJ
Hsa5NEyPf/q7pcQHu3/mzGY=
=f8ac
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Joining the Python modules team

2006-04-12 Thread Gustavo Franco
On 4/12/06, Torsten Marek [EMAIL PROTECTED] wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Hi,

 I'd like to join, too. Please add my account (shlomme).
 I bring in ElementTree, cElementTree and ElementTidy (currently in the NEW 
 queue).


Hi Torsten,

Welcome to the python-modules! I've added you on the group at alioth.
Any doubt or suggestion, ask us here.

Thanks,
-- stratus



Re: Joining the python modules team

2006-04-12 Thread Gustavo Franco
On 4/12/06, Jan Lübbe [EMAIL PROTECTED] wrote:
 Hi!

 I'm currently in the NM-Process and maintain the packages python-pysnmp2
 and pida. I'd like to join the python-modules team to help with
 comaintaining the packages.

 My alioth login is jluebbe-guest.


Hi Jan,

Welcome to the python-modules! You've svn commit access, so you're
free to upload the packages you're maintaining to our repository. Read
our policy, and if you've doubts or suggestions post it here or
contact us at irc.oftc.net - #debian-python.

Thanks,
-- stratus