[issue1702] Word "alias" used in confusing way to compare open() and file()

Changes by Richard Cohen: -- nosy: +vmlinuz __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue1702] Word "alias" used in confusing way to compare open() and file()

New submission from Devin Jeanpierre: I was slightly misled by the wording of part of the docs (http://docs.python.org/lib/bltin-file-objects.html): "file() is new in Python 2.2. The older built-in open() is an alias for file()." I actually thought it meant that open was an alias of file, so

[issue1745108] 2.5.1 curses panel segfault in new_panel on aix 5.3

Paul Smedley added the comment: I see similar problems here on OS/2 with Python 2.5.1 and Ncurses 5.6. Problem is causes as win->win is uninitialised when passed to new_panel. Initialising win->win to a value makes the new_panel call work. Not sure why this works on other platforms but fails o

[issue1350] IDLE - CallTips enhancement - show full doc-string in new window

Kurt B. Kaiser added the comment: I deleted the extra files. You aren't making this easy! I was expecting a relatively small update to the original patch. Did you backport my 3.0 revision of CallTips.py or did you come up with your own version which uses inspect.py? Right now, the patch inc

[issue1701] svn checkout does not work

Martin v. Löwis added the comment: Fixed. -- nosy: +loewis resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ ___ Py

[issue1701] svn checkout does not work

New submission from hjmjohnson: === ping svn.python.org PING svn.python.org (82.94.237.220): 56 data bytes 64 bytes from 82.94.237.220: icmp_seq=0 ttl=49 time=107.208 ms svn co http://svn.python.org/projects/python/trunk python-svn svn: PROPFIND request failed on '/projects/pyt

[issue1698] urlparse and usernames containing @

Senthil added the comment: > > Olivier Croquette added the comment: > > And about the decoding, sorry, it's clear from your snippets that > urlparse doesn't do it: > >>> print q.username > user%40xyz > > Maybe it should do it, I am not sure. What do you think? It would save > work for the modu

[issue1698] urlparse and usernames containing @

Senthil added the comment: > Olivier Croquette added the comment: > > > The problem right now is that urlparse parses silently an URL which is > not compliant, but does the wrong thing with it (since usernames can > contain @, and hostname can not, it's a more logical thing to parse from > the

[issue1205] urllib fail to read URL contents, urllib2 crash Python

Senthil added the comment: > > Senthil added the comment: > > Irrespective of the patch, this issue is reproducable with the code in the > trunk for Python 2.6. Should we close this then? > __ Sorry, I meant to say "NOT Reproducable". __

[issue1205] urllib fail to read URL contents, urllib2 crash Python

Senthil added the comment: Irrespective of the patch, this issue is reproducable with the code in the trunk for Python 2.6. Should we close this then? n 2.6a0 (trunk:59600M, Dec 25 2007, 13:54:34) [GCC 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)] on linux2 Type "help", "copyright", "credits" or "licens

[issue1698] urlparse and usernames containing @

Olivier Croquette added the comment: And about the decoding, sorry, it's clear from your snippets that urlparse doesn't do it: >>> print q.username user%40xyz Maybe it should do it, I am not sure. What do you think? It would save work for the module user. __ Trac

[issue1698] urlparse and usernames containing @

Olivier Croquette added the comment: See also the related bug on duplicity: http://savannah.nongnu.org/bugs/?21475 __ Tracker <[EMAIL PROTECTED]> __ ___

[issue1698] urlparse and usernames containing @

Olivier Croquette added the comment: Hi! Thanks for the reply! The problem right now is that urlparse parses silently an URL which is not compliant, but does the wrong thing with it (since usernames can contain @, and hostname can not, it's a more logical thing to parse from the right using rsp

[issue1698] urlparse and usernames containing @

Senthil added the comment: Hi ocroquette, Even though I have seen ftp sites requesting email addresses as user names, I would rather put this issue for discussion as this not per any RFC. urlparse is based upon RFC1808 and it points to RFC1738 for the URL Syntax. RFC1738 specifically says (line