-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 14, 2009, at 13:24 , Matias Surdi wrote:
Hi!
I'm wondering if there is any example or documentation on how to add
or modify ldap objects whose values contains non-ascii characters,
such as accents, and so on. As far as I understand,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 7, 2009, at 13:48 , Michael Ströder wrote:
Jens Vagelpohl wrote:
While we're on the topic of packaging, I have one more request:
Please upload the software (the tarball) to PyPI instead of using the
Sourceforge URL as download URL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
While we're on the topic of packaging, I have one more request:
Please upload the software (the tarball) to PyPI instead of using the
Sourceforge URL as download URL. While setuptools itself can (at least
most of the time) interact with
On Jun 11, 2008, at 02:36 , Michael Ströder wrote:
Sigh! One more place to go when doing a release...
If I were you I'd put releases on PyPI only and just point people
there. Using setuptools this is a one line command from within your
checkout, you don't even need to create the tarball
On Jun 11, 2008, at 09:25 , Michael Ströder wrote:
Jens Vagelpohl wrote:
Personally, I can't stand that SF setup.
Are you talking about python-ldap? I generally hide old releases.
There
are pros and cons for that.
python-ldap and general. SF is a pile of steaming you know what. It's
