[issue10080] Py_Initialize crashes when stdout has been redirected with freopen

Amaury Forgeot d'Arc added the comment: It looks very similar to issue6501. Can you check if setting the environment variable PYTHONIOENCODING=cp1252 solves the problem? -- nosy: +amaury.forgeotdarc ___ Python tracker

[issue6417] multiprocessing Process examples: print and getppid

Changes by Georg Brandl : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue6417] multiprocessing Process examples: print and getppid

Sandro Tosi added the comment: Thanks Michael for checking it, this bug can be closed then, since all the points mentioned were already fixed. -- ___ Python tracker ___

[issue10080] Py_Initialize crashes when stdout has been redirected with freopen

New submission from Mitchell Stokes : I have Python embedded in a C/C++ program, and I'm trying to redirect stdout to a text file. Since I'm trying to get rid of the console, I want C and Python stdout going to the text file (so, not sys.stdout = open('log.txt', 'w')). To this end, I used freo

[issue10079] idlelib for Python 3 with Guilherme Polo GSoC enhancements

New submission from Bruce Sherwood : It is proposed to incorporate the work of Guilherme Polo in the 2009 Google Summer of Code into idlelib. Polo's enhancements have been extensively tested for a year through being included with VPython. Here is a description from NEWS.txt: In December 2008 Da

[issue7944] Use the 'with' statement in conjunction with 'open' throughout test modules

Brian Curtin added the comment: Fixed test_mailbox in r85401. Fixed test_marshal in r85402. Fixed test_bz2 in r85403. -- ___ Python tracker ___ __

[issue10071] Should not release GIL while running RegEnumValue

Daniel Stutzbach added the comment: Hirokazu, could you run Python in a debugger and figure out exactly which line crashes and what the error is? I'm curious. If we make this change, the same change should be applied to RegEnumKey, etc., since the RegEnumKey docs contain similar language. -

[issue7944] Use the 'with' statement in conjunction with 'open' throughout test modules

Brian Curtin added the comment: Fixed test_gzip in r85400. -- resolution: -> accepted ___ Python tracker ___ ___ Python-bugs-list mai

[issue6417] multiprocessing Process examples: print and getppid

Michael Newman added the comment: The example is working correctly for: Python 3.2a3 (r32a3:85355, Oct 10 2010, 17:11:45) [MSC v.1500 32 bit (Intel)] on win32 # First test: C:\mike>c:\Python32\python.exe s2.py main line module name: __main__ parent process: 2360 process id: 1584 function f mod

[issue10068] global objects created in some module are not destroyed when last reference to that module is released

Benjamin Peterson added the comment: r85398 -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-li

[issue10068] global objects created in some module are not destroyed when last reference to that module is released

STINNER Victor added the comment: test_runpy fails also on Python 3.2. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue10068] global objects created in some module are not destroyed when last reference to that module is released

STINNER Victor added the comment: r85393 introduced a regression in test_runpy of Python 2.7. -- nosy: +haypo resolution: fixed -> status: closed -> open ___ Python tracker ___

[issue10071] Should not release GIL while running RegEnumValue

Brian Curtin added the comment: Some of your submission appears to have gotten lost (I saw it via email). Below is the patch you proposed. I haven't experienced this crash on my machines, but the solution seems fine to me. # I sometimes experienced crash of test_changing_value(test_winreg) #

[issue10039] python é.py fails with UnicodeEncodeErr or if PYTHONFSENCODING is used

STINNER Victor added the comment: > Is it always correct to decode a filename with the locale encoding > on Unix? Do you know something better than the locale encoding? I don't. > Can’t each filesystem have its own encoding? Yes, but how do you get the encoding of each filesystem? I think tha

[issue8863] Segfault handler: display Python backtrace on segfault

STINNER Victor added the comment: Patch version 4: - Add segfault.c to pythoncore.vcproj - Remove #error "nope" (I used it for debug purpose) - Don't include on Windows This version works on Windows. -- Added file: http://bugs.python.org/file19210/segfault_handler-4.patch

[issue1503] test_xmlrpc is still flakey

Ralf Schmitt added the comment: The tests now pass, but the underlying issue hasn't been fixed! -- ___ Python tracker ___ ___ Python-b

[issue8863] Segfault handler: display Python backtrace on segfault

STINNER Victor added the comment: > It should be tested at least on a wide build and ... Done: it works correctly for non-BMP characters in narrow and wide builds. Eg. in wide build with U+10 character in the path: - $ ./python bla.py Fatal Python error: segmentation f

[issue10041] socket.makefile(mode = 'r').readline() silently removes carriage return

kai zhu added the comment: done ;p added separate unicode read, write, and readwrite test cases (which all pass) keep in mind my issue is specific to truncation of carriage return (imo a priority for py3k migration). i think this can b resolved by python 3.2 more general unicode issues shou

[issue8863] Segfault handler: display Python backtrace on segfault

Changes by STINNER Victor : Removed file: http://bugs.python.org/file17717/segfault_handler-2.patch ___ Python tracker ___ ___ Python-bugs-list

[issue8863] Segfault handler: display Python backtrace on segfault

Changes by STINNER Victor : Removed file: http://bugs.python.org/file17507/segfault_handler.patch ___ Python tracker ___ ___ Python-bugs-list m

[issue8863] Segfault handler: display Python backtrace on segfault

Changes by STINNER Victor : -- nosy: +dmalcolm ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue8863] Segfault handler: display Python backtrace on segfault

STINNER Victor added the comment: Updated example: -- $ ./python Lib/test/crashers/recursive_call.py Fatal Python error: segmentation fault Traceback (most recent call first): File "Lib/test/crashers/recursive_call.py", line 12 in File "Lib/test/

[issue8863] Segfault handler: display Python backtrace on segfault

STINNER Victor added the comment: New version of the patch: - use more standard function names (_Py_initsegfault => _Py_InitSegfault) - use "#ifdef HAVE_SIGACTION" to support system without sigaction(): fallback to signal() - usage of the alternative stack is now optional (#ifdef HAVE_SIGALT

[issue10078] Documentation: 'Postive' should be 'Positive'

Benjamin Peterson added the comment: Done for all branches that are maintained. -- resolution: remind -> fixed ___ Python tracker ___ ___

[issue10078] Documentation: 'Postive' should be 'Positive'

Changes by Retro : -- resolution: fixed -> remind ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue10078] Documentation: 'Postive' should be 'Positive'

Changes by Retro : -- status: closed -> open ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue10078] Documentation: 'Postive' should be 'Positive'

Retro added the comment: Please commit this fix to the trunk, as well as to the Python 2.5, Python 2.6, and Python 2.7 branches. Thank you. -- ___ Python tracker ___ __

[issue10074] dictobject.c: crash in Py_XDECREF

Changes by Benjamin Peterson : -- resolution: -> invalid status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue10078] Documentation: 'Postive' should be 'Positive'

Benjamin Peterson added the comment: r85395. -- nosy: +benjamin.peterson resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue10078] Documentation: 'Postive' should be 'Positive'

New submission from Retro : There's a typo in the docs. Please follow http://docs.python.org/py3k/library/string.html#format-specification-mini-language and find the below text, and fix the word 'Postive' to 'Positive', indicated between >>> and <<<: 'g' General format. For a given preci

[issue10068] global objects created in some module are not destroyed when last reference to that module is released

Benjamin Peterson added the comment: r85392. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-l

[issue7140] imp.new_module does not function correctly if the module is returned from a function and used directly

Benjamin Peterson added the comment: Rebroken in r85392. See #10068. -- resolution: fixed -> status: closed -> open ___ Python tracker ___ __

[issue6612] 'import site' fails when called from an unlinked directory

STINNER Victor added the comment: Fixed in 3.2 (r85386+r85387+r85389), 2.7 (r85390), 3.1 (r85391). Thanks labrat for your patch. I added you to Misc/ACKS. -- resolution: -> fixed status: open -> closed ___ Python tracker

[issue10077] Python 3.1: site error is not logged

New submission from STINNER Victor : If the site module fails, the error is not logged because of a bug in initsite(). The problem is that PyFile_WriteString() does nothing if an error occurred. - Edit Lib/site.py to add "raise Exception('xxx')" at the beginning of main() - Run ./python - (

[issue10069] 2to3 crash in fix_urllib.py

Benjamin Peterson added the comment: r85388. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-l

[issue10074] dictobject.c: crash in Py_XDECREF

Changes by Sridhar Ratnakumar : -- nosy: +toddw ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue10074] dictobject.c: crash in Py_XDECREF

Sridhar Ratnakumar added the comment: On 2010-10-12, at 11:49 AM, Ned Deily wrote: > And what is libpyxpcom.dylib? Likely PyXPCOM https://developer.mozilla.org/en/PyXPCOM > As Ronald says, this is almost certainly a 3rd-party extension module problem. Ok, I've made a note for Todd (current

[issue10068] global objects created in some module are not destroyed when last reference to that module is released

Antoine Pitrou added the comment: > Therefore, I propose we remove the Py_REFCNT == 1 guard in > module_dealloc, and simply leave as an open bug that modules will clear > their dictionaries on deallocation. Yes, I think it's the best solution. People can easily copy the dict if they want to k

[issue10068] global objects created in some module are not destroyed when last reference to that module is released

Benjamin Peterson added the comment: Tricky. I think the only way to do this properly is to call _PyModule_Clear when the dict is destroyed. However, there's no good way to flag a dictionary as a "module" dict. Therefore, I propose we remove the Py_REFCNT == 1 guard in module_dealloc, and sim

[issue7523] add SOCK_NONBLOCK and SOCK_CLOEXEC to socket module

Antoine Pitrou added the comment: You can check accept4() presence by adding it to the AC_CHECK_FUNCS macro in configure.in around line 2553, and add the corresponding HAVE_ACCEPT4 lines in pyconfig.h.in. Then run "autoconf" and you will have access to a HAVE_ACCEPT4 constant when accept4() e

[issue3873] Unpickling is really slow

Antoine Pitrou added the comment: Patch committed in r85384. -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___

[issue7523] add SOCK_NONBLOCK and SOCK_CLOEXEC to socket module

Vetoshkin Nikita added the comment: Thanks! I can see the problem now, but I think checking should be done like this: >>> fcntl.fcntl(c, fcntl.F_GETFD) & fcntl.FD_CLOEXEC 0 >>> fcntl.fcntl(s, fcntl.F_GETFD) & fcntl.FD_CLOEXEC 1 and with accept4() call I've got flag set: >>> fcntl.fcntl(c, fcntl

[issue10076] Regex objects became uncopyable in 2.5

Michael Shields added the comment: Here's the patch. I updated the test case and release notes also. I'm a Google employee, so this patch is covered by whatever usual copyright arrangement we have with the PSF. -- keywords: +patch Added file: http://bugs.python.org/file19205/copy-pat

[issue10076] Regex objects became uncopyable in 2.5

New submission from Michael Shields : For many years now, the sre module has provided __copy__ and __deepcopy__ modules that raise an exception ("cannot copy this pattern object") by default, with an #ifdef to enable their implementations. Until Python 2.5, these were simply unused. Since th

[issue10070] 2to3 wishes for already-2to3'ed files

Martin v. Löwis added the comment: >> I don't think this can work. You may have to write code like >> >> if sys.version_info >= (3,): >> try: >> some_code() >> except Exception, e: >> pass >> >> (i.e. not use the "as" syntax), because it otherwise won't parse on >> Python 2. Hence, o

[issue10073] calendar.isleap() not checking parameter type

Philip Jenvey added the comment: Another option is to wrap the operations in a try/except. When a TypeError is raised have it throw a new TypeError with an improved error message and the original chained to it -- nosy: +pjenvey ___ Python tracker

[issue10041] socket.makefile(mode = 'r').readline() silently removes carriage return

Antoine Pitrou added the comment: The proposed test case doesn't test a lot, IMHO. It would be better if it sent binary from one end and received unicode on the other end, or vice-versa (with explicit encoding and errors, preferably). -- ___ Python

[issue10075] Get session cache stats from SSLContext

Changes by Antoine Pitrou : -- status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue10075] Get session cache stats from SSLContext

Antoine Pitrou added the comment: I've renamed the method to session_stats() and commited the patch in r85383. -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> pending ___ Python tracker

[issue10073] calendar.isleap() not checking parameter type

shadikka added the comment: To clarify my original point, I'm for making an explicit error message for that, definitely not for any silent failure or automatic string conversion. -- ___ Python tracker ___

[issue7523] add SOCK_NONBLOCK and SOCK_CLOEXEC to socket module

Antoine Pitrou added the comment: The accept() issue is the following: the socket created by accept() (in Lib/socket.py) will formally inherit its parent's `type` attribute (including any SOCK_NONBLOCK and SOCK_CLOEXEC flags). However, the underlying Linux socket is created by the accept() sy

[issue10072] ftplib documentation is unclear

Rafe Kettler added the comment: Double spaced after the sentence ending periods. -- Added file: http://bugs.python.org/file19204/ftplib-patch.txt ___ Python tracker ___

[issue10072] ftplib documentation is unclear

Changes by Rafe Kettler : Removed file: http://bugs.python.org/file19203/ftplib-patch.txt ___ Python tracker ___ ___ Python-bugs-list mailing

[issue10073] calendar.isleap() not checking parameter type

Éric Araujo added the comment: I’d be in favor of type checking here, but I know I’m in the minority. I’m very much not in favor of making code less readable (“& 3”). -- ___ Python tracker __

[issue10072] ftplib documentation is unclear

Éric Araujo added the comment: Looks good to me. Before committing, spaces after full stops should be doubled. -- nosy: +eric.araujo ___ Python tracker ___

[issue10072] ftplib documentation is unclear

Changes by Rafe Kettler : Added file: http://bugs.python.org/file19203/ftplib-patch.txt ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue10072] ftplib documentation is unclear

Changes by Rafe Kettler : Removed file: http://bugs.python.org/file19201/ftplib-patch.rst ___ Python tracker ___ ___ Python-bugs-list mailing

[issue10072] ftplib documentation is unclear

Changes by Rafe Kettler : -- keywords: +patch Added file: http://bugs.python.org/file19202/ftplib-patch.diff ___ Python tracker ___ __

[issue10072] ftplib documentation is unclear

Rafe Kettler added the comment: I've drafted up a patch. For those of you who don't want to read the diff, it changes all references to FTP reply codes with short explanations of what they do. Also, in the docs for retrlines() and nlst() the commands LIST, NLST, and MLSD are explained. Attac

[issue10073] calendar.isleap() not checking parameter type

Alexander Belopolsky added the comment: I would also like to note the following curiosity: >>> calendar.isleap("%d") False I still don't think there is anything worth fixing here, but we can consider replacing year % 4 == 0 predicate with year & 3 == 0 which will change the error raised by i

[issue7523] add SOCK_NONBLOCK and SOCK_CLOEXEC to socket module

Vetoshkin Nikita added the comment: Made an attempt to port lekma's patch to py3k-trunk. No (logical) changes needed. Don't know about accept4() issue. As I saw in Qt sources, they ifdef'ed CLOEXEC by default on file descriptors. Don't think it's acceptable :) in this particular case. So, @A

[issue10074] dictobject.c: crash in Py_XDECREF

Ned Deily added the comment: And what is libpyxpcom.dylib? As Ronald says, this is almost certainly a 3rd-party extension module problem. -- nosy: +ned.deily ___ Python tracker __

[issue10075] Get session cache stats from SSLContext

New submission from Antoine Pitrou : This patch adds a method to query the session cache statistics from an SSL context. See http://www.openssl.org/docs/ssl/SSL_CTX_set_session_cache_mode.html# for more info. -- components: Library (Lib) files: sslstats.patch keywords: patch messages:

[issue10070] 2to3 wishes for already-2to3'ed files

Hallvard B Furuseth added the comment: [I got failed issue tracker submission, trying again...] >> How about this phrasing: “Make 2to3 fixers not touch code in a >> block starting with ’if sys.version >= '3'’“ >> (and hexversion, version_info, you get the idea)? Right, almost... it doesn't nee

[issue10049] Add a "no-op" (null) context manager to contextlib

Raymond Hettinger added the comment: Are you sure that this is useful enough to warrant inclusion in the standard lib? I don't know of anyone else who has used the same idiom. It seems crufty to me -- something that adds weight (mental burden and maintenance effort) without adding much valu

[issue10067] itertools' docs put izip_longest in the "terminating on the shortest input sequence" section

Changes by Raymond Hettinger : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue10067] itertools' docs put izip_longest in the "terminating on the shortest input sequence" section

Raymond Hettinger added the comment: I saw that when I put in in. It doesn't fit the overall category but it does belong in the same general grouping and the notes make the semantics clear, so there is no harm in it and I like the current presentation better than the alternatives. -- r

[issue10074] dictobject.c: crash in Py_XDECREF

Ronald Oussoren added the comment: It is not impossible that this is a bug in python, but IMHO pretty unlikely, it is way more likely to be a bug in a 3th-party extension. BTW. This issue is very likely to languish unless you add a way to reproduce the issue (and preferably without Komodo).

[issue9003] urllib.request and http.client should allow certificate checking

Changes by Antoine Pitrou : Removed file: http://bugs.python.org/file19189/unnamed ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue10049] Add a "no-op" (null) context manager to contextlib

R. David Murray added the comment: Because hardcoding a particular condition into a context manager is less flexible? (I'm +0 on this thing myself, by the way.) -- ___ Python tracker

[issue10074] dictobject.c: crash in Py_XDECREF

New submission from Sridhar Ratnakumar : I noticed that Python 2.6.6 crashes on OSX 10.6 when using Komodo. The below traceback indicates a crash in line 911 - "Py_XDECREF(ep->me_value);" in tags/r266/Objects/dictobject.c Thread 0: Dispatch queue: com.apple.main-thread 0 org.activestate.Act

[issue10049] Add a "no-op" (null) context manager to contextlib

Giampaolo Rodola' added the comment: I'm with Antoine. Why not just do this in the context function itself? I think it's more explicit and easier than reading the doc to figure out what nullcontext is supposed to do: from contextlib import contextmanager CONDITION = False @contextmanager de

[issue10063] file:// scheme will stop accessing via ftp protocol

R. David Murray added the comment: I think the error message should be changed from 'allowed' to 'supported', though. -- ___ Python tracker ___

[issue10063] file:// scheme will stop accessing via ftp protocol

Éric Araujo added the comment: With this explanation, I agree with Senthil’s plan too. -- ___ Python tracker ___ ___ Python-bugs-list

[issue10039] python é.py fails with UnicodeEncodeErr or if PYTHONFSENCODING is used

Éric Araujo added the comment: > if you are saying, "the user asked for it, it *should* fail", then > that is indeed one of the arguments put forward in issue 9992 where > this was discussed. You could put it that way, thanks for phrasing my thoughts :) > But I think the emerging consensus is t

[issue10039] python é.py fails with UnicodeEncodeErr or if PYTHONFSENCODING is used

R. David Murray added the comment: Éric, if you are saying, "the user asked for it, it *should* fail", then that is indeed one of the arguments put forward in issue 9992 where this was discussed. But I think the emerging consensus is that it is better to just avoid the problem by always usin

[issue10070] 2to3 wishes for already-2to3'ed files

Martin v. Löwis added the comment: > How about this phrasing: “Make 2to3 fixers not touch code in a block > starting with ’if sys.version >= '3'’“ (and hexversion, version_info, > you get the idea)? I don't think this can work. You may have to write code like if sys.version_info >= (3,): try

[issue10063] file:// scheme will stop accessing via ftp protocol

R. David Murray added the comment: Éric: WellI suppose that depends on how you look at it. The RFC says that 'file:' does not specify a network protocol, and so "it's utility in network protocols between hosts is limited". So, technically an implementation that decides to handle 'file://

[issue10063] file:// scheme will stop accessing via ftp protocol

Antoine Pitrou added the comment: (by disable I meant disallow, sorry) -- ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue10063] file:// scheme will stop accessing via ftp protocol

Antoine Pitrou added the comment: I'd say disable hostnames in file:// URIs altogether. There's no practical reason for forcing a hostname in there, and trying to check that it matches the local host's FQDN sounds like a distraction. -- nosy: +pitrou _

[issue10067] itertools' docs put izip_longest in the "terminating on the shortest input sequence" section

Changes by Éric Araujo : -- nosy: +rhettinger versions: -Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscr

[issue10066] xmlrpclib does not handle some non-printable characters properly

Martin v. Löwis added the comment: The patch is incorrect. Even though this may let get these characters "through", the other end will have no clue that \x is meant as an escape. Please face the ugly truth: XML (and hence XML-RPC) just does not support these characters, see http://www.w3.org/

[issue8106] SSL session management

Antoine Pitrou added the comment: http://www.openssl.org/docs/ssl/SSL_CTX_set_session_cache_mode.html suggests that SSL session caching already occurs by default in server mode: “SSL_SESS_CACHE_SERVER Server sessions are added to the session cache. When a client proposes a session to be

[issue10072] ftplib documentation is unclear

Giampaolo Rodola' added the comment: A patch would be great. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue10042] total_ordering stack overflow

Changes by Éric Araujo : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue10039] python é.py fails with UnicodeEncodeErr or if PYTHONFSENCODING is used

Éric Araujo added the comment: I don’t understand why reading a filename would not respect the envvar stating the filesystem encoding. -- nosy: +eric.araujo ___ Python tracker

[issue10073] calendar.isleap() not checking parameter type

Changes by Éric Araujo : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue10070] 2to3 wishes for already-2to3'ed files

Éric Araujo added the comment: How about this phrasing: “Make 2to3 fixers not touch code in a block starting with ’if sys.version >= '3'’“ (and hexversion, version_info, you get the idea)? -- ___ Python tracker _

[issue10070] 2to3 wishes for already-2to3'ed files

Changes by Éric Araujo : -- nosy: +benjamin.peterson, eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue10069] 2to3 crash in fix_urllib.py

Changes by Éric Araujo : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue10066] xmlrpclib does not handle some non-printable characters properly

Éric Araujo added the comment: Thanks for the report. Unfortunately, 2.6 only gets security fixes, not general bug fixes; can you tell if this applies to 2.7, 3.1 and 3.2? If you have a small script that displays the problem, please attach it. -- nosy: +eric.araujo, loewis

[issue10063] file:// scheme will stop accessing via ftp protocol

Éric Araujo added the comment: Ah, I thought this was not a bug, because of “RFC 1738, says that host, if present should be the FQDN of the machine”. If it’s a bug I’m all for fixing it in all three versions. -- ___ Python tracker

[issue10063] file:// scheme will stop accessing via ftp protocol

R. David Murray added the comment: I doubt it. As Senthil says, file invoking ftp it is a bug. I'm just betting that *someone* is going to complain when it stops working in their particular situation. -- ___ Python tracker

[issue10063] file:// scheme will stop accessing via ftp protocol

Éric Araujo added the comment: file: URIs provoking FTP access seem wrong to me. Are there widely-used tools displaying this behavior? -- nosy: +eric.araujo ___ Python tracker ___

[issue6322] Pdb breakpoints don't work on lines without bytecode

Changes by R. David Murray : -- nosy: +georg.brandl -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue10073] calendar.isleap() not checking parameter type

Alexander Belopolsky added the comment: I agree with David on this one. In addition to the arguments already stated, the string value of an exception is not part of specification. The exception is still TypeError even if the message may be confusing. I also find that once read in the conte

[issue10070] 2to3 wishes for already-2to3'ed files

Hallvard B Furuseth added the comment: Another syntax could be attached to if-else and try-except. Given: if ...: else: or try: except ...: if 2to3 would translate to or vise versa, sans whitespace/comment differences, then it does not do

[issue1708] improvements for linecache

R. David Murray added the comment: I am indeed going to close this. The patch isn't complete, since there's the line ending issue Antoine pointed out, which implies that there are also some missing tests. I doubt that linecache performance is something that affects very many people, but i

[issue10070] 2to3 wishes for already-2to3'ed files

Hallvard B Furuseth added the comment: > Maybe we need to tackle this from a different angle: can you please > specify the feature you are asking for exactly, with any syntax, API, or > command line changes that you consider necessary? First, nothing here is necessary, since it's just a request

[issue10073] calendar.isleap() not checking parameter type

R. David Murray added the comment: In Python we often don't type check, we just let errors happen. It is true that it would make the problem clearer to do a type check and issue a specific error message, but I don't know if it is worth it. (The error would already have been clear if it were

  1   2   >