-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 18:38 , Sidnei da Silva wrote:
> On Tue, Apr 7, 2009 at 1:28 PM, Jens Vagelpohl
> wrote:
>> Personally, I haven't had the need to search for a service that
>> offers
>> something like SF, incl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 7, 2009, at 19:03 , Michael Ströder wrote:
> Jens Vagelpohl wrote:
>> One candidate you could look at, if you have a minute, is Launchpad.
>> They have all kinds of nice services, but there's one big drawback:
>> The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 7, 2009, at 15:43 , Michael Ströder wrote:
> Jens Vagelpohl wrote:
>>
>> On Apr 7, 2009, at 13:48 , Michael Ströder wrote:
>>
>>> Does that look correct to you?
>>> http://pypi.python.org/pypi/python-lda
-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
>
-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 SourceForg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 6, 2009, at 16:21 , Michael Ströder wrote:
> Jens Vagelpohl wrote:
>> For the customers' needs it's perfectly fine to just go with an older
>> version of python- ldap.
>
> As long as there aren't any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
P.S.: To avoid any confusion, I'm not arguing for official support for
old versions. Just an easy way (like PyPI) to get hold of them.
SourceForge is, in my very personal opinion, garbage. You never know
which mirror holds what. You never know if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 6, 2009, at 14:55 , Michael Ströder wrote:
> Jens Vagelpohl wrote:
>>
>> On Apr 6, 2009, at 14:10 , Michael Ströder wrote:
>>
>>>> It's not always wise to go with the latest.
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 6, 2009, at 14:10 , Michael Ströder wrote:
>> It's not always wise to go with the latest.
>
> At the moment it is (within the 2.3 series).
Unfortunately that's not true. I've ben in many situations where I
really needed older versions (lik
On Jun 16, 2008, at 17:07 , Michael Ströder wrote:
> Torsten Kurbad wrote:
>> Jens Vagelpohl wrote:
>>> IMHO it's really not a big deal to tell people they must use older
>>> python-ldap releases if they insist on running Python versions that
>>> are no
On Jun 16, 2008, at 15:48 , Michael Ströder wrote:
> HI!
>
> I'd like to hear from the Python community whether support for Python
> version prior to 2.3 is still needed in python-ldap. Please tell me
> which Python version you're using and why it'd be important for you to
> have python-ldap upda
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
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 you
On Mar 30, 2008, at 17:03 , Michael Ströder wrote:
> HI!
>
> Waldemar Osuch contributed the converted new-style docs for python-
> ldap
> based on the latest latex-based docs. You can view/browse the PDF and
> HTML builds here:
>
> http://python-ldap.sourceforge.net/new-style-doc/
>
> The PDF ind
15 matches
Mail list logo
