[issue17305] IDNA2008 encoding missing

2013-12-02 Thread Marten Lehmann
Marten Lehmann added the comment: There's nice library called idna on PyPI doing idna2008: https://pypi.python.org/pypi/idna/0.1 I'd however prefer this standard encoding to be part of standard python. -- ___ Python tracker <http://bu

[issue16480] pyvenv 3.3 fails to create symlinks for /local/{bin, lib} to /{bin, lib}

2013-04-05 Thread Marten Lehmann
Marten Lehmann added the comment: Which bug ID? Couldn't find it anywhere in the previous comments. -- ___ Python tracker <http://bugs.python.org/is

[issue16480] pyvenv 3.3 fails to create symlinks for /local/{bin, lib} to /{bin, lib}

2013-04-04 Thread Marten Lehmann
Marten Lehmann added the comment: Could you please tell me, in which exact release or commit this is resolved? I'm using Python 3.3.0 on Ubuntu Precise and I noticed like the others, that e.g. easy_install and pip are installed to venv/local/bin instead of venv/bin and the site-pac

[issue17305] IDNA2008 encoding missing

2013-02-27 Thread Marten Lehmann
Marten Lehmann added the comment: I found an interesting link about this issue: http://www.unicode.org/faq/idn.html I also checked a domain name of a client that ends with 'straße.de': IE, Firefox and Chrome still use IDNA2003, Opera already does IDNA2008. In IDNA2008 a lot of

[issue17305] IDNA2008 encoding missing

2013-02-27 Thread Marten Lehmann
Marten Lehmann added the comment: IDNA2008 should be backwards compatible. I can try to explain it in a practical example: DENIC was the first registry that actually used IDNA2008 - at a time, where not even libidn2 officially included the changes required for it. This was mainly due to the

[issue17305] IDNA2008 encoding missing

2013-02-27 Thread Marten Lehmann
Marten Lehmann added the comment: For the embedded Python examples, please prepend the following lines: from __future__ import unicode_literals name='müller.com' So regarding interoperability: Usually you only use one implementation in your code and hopefully the latest release, b

[issue17305] IDNA2008 encoding missing

2013-02-27 Thread Marten Lehmann
Marten Lehmann added the comment: At least from the GNU people, two separate projects exists for this matter: libidn, the original IDNA translation (http://www.gnu.org/software/libidn/) libidn2, the IDNA2008 translation (http://www.gnu.org/software/libidn/libidn2/manual/libidn2.html) Btw

[issue17305] IDNA2008 encoding missing

2013-02-26 Thread Marten Lehmann
New submission from Marten Lehmann: Since Python 2.3 the idna encoding is available for Internationalized Domain Names. But the current encoding doesn't work according to the latest version of the spec. There is a new IDNA2008 specification (RFCs 5890-5894). Although I'm not very