[issue8746] os.chflags() and os.lchflags() are not built when they should be be

Garrett Cooper added the comment: *NOUNLINK was not implemented by OSX, so there's actually a bug with the compile tests if you take that into consideration. And again, only FreeBSD defines *NOUNLINK. The other BSDs, not so much. As far as the reason why I implemented the flags, the documenta

[issue9810] bzip2 build sometimes fails (VS8.0)

Hirokazu Yamamoto added the comment: Probably this patch works. P.S. These lines in PCBuild/vs9to8.py seem to be not needed. I could build python even without it, (I only tried py3k) # Bah. VS8.0 does not expand macros in file names. # Replace them here. lines = lines.replace('$(sqlite3D

[issue9810] bzip2 build sometimes fails (VS8.0)

Hirokazu Yamamoto added the comment: - create latter option + create the patch by latter option -- ___ Python tracker ___ ___ Python-b

[issue9810] bzip2 build sometimes fails (VS8.0)

Hirokazu Yamamoto added the comment: Thank you for the reply. I agree with you. I'll try to create latter option. -- ___ Python tracker ___ __

[issue9815] test_tarfile sometimes ends with error "Cannot remove dir"

Hirokazu Yamamoto added the comment: Here is the simple test case to demonstrate this issue. -- Added file: http://bugs.python.org/file18897/test_traceback_freed.py ___ Python tracker __

[issue9868] test_locale leaves locale changed

Hirokazu Yamamoto added the comment: This happens because in Lib/test/test_locale.py, TestEnUSCollation#setUp raises exception after BaseLocalizedTest.setUp(self) changed locale. tearDown never be called when setUp failedsetUp failed. It's easy to fix this as is, but I think more general soluti

[issue9868] test_locale leaves locale changed

New submission from Hirokazu Yamamoto : I noticed test_locale leaves locale changed. # test_boo is simple test just to print windows error. E:\python-dev\py3k\Lib\test>py3k -m test.regrtest test_locale test_boo [1/2] test_locale [2/2] test_boo test test_boo failed -- Traceback (most recent call

[issue9867] Interrupted system calls are not retried

Ned Deily added the comment: The test fails exactly the same way using a python 2.6.6 on a current Debian (testing) Linux 2.6.32 so I think it better to remove the OS X from the title. Also the versions field refers to where a potential fix might be applied; that rules out 2.5 and 2.6 since

[issue8077] cgi handling of POSTed files is broken

Changes by R. David Murray : -- nosy: +r.david.murray title: urlparse -> cgi handling of POSTed files is broken ___ Python tracker ___

[issue9867] Interrupted system calls are not retried on OS X

New submission from Armin Ronacher : Currently Python does not check fread and other IO calls for EINTR. This usually is not an issue, but on OS X a continued program will be sent an SIGCONT signal which causes fread to be interrupted. Testcase: mitsuh...@nausicaa:~$ python2.7 Python 2.7 (r2

[issue9863] threading, signals, atexit: different execution with different versions

R. David Murray added the comment: I'm closing this as invalid, but I note that this kind of behavior change is not something we would normally have done in a point release if we had realized the consequences. -- resolution: -> invalid stage: -> committed/rejected status: open -> cl

[issue9858] Python and C implementations of io are out of sync

Benjamin Peterson added the comment: 2010/9/15 Daniel Stutzbach : > > Daniel Stutzbach added the comment: > >> Hmm, none the less other code expects it. > > Does that imply that there's some code that will break on FileIO objects that > are created using a file descriptor instead of a filename

[issue9865] OrderedDict doesn't implement __sizeof__

Changes by Raymond Hettinger : -- keywords: +patch stage: -> patch review type: behavior -> feature request Added file: http://bugs.python.org/file18896/od_size.diff ___ Python tracker _

[issue9858] Python and C implementations of io are out of sync

Daniel Stutzbach added the comment: > Hmm, none the less other code expects it. Does that imply that there's some code that will break on FileIO objects that are created using a file descriptor instead of a filename? If so, where? -- ___ Python tr

[issue9315] The trace module lacks unit tests

Terry J. Reedy added the comment: I agree with finishing this and opening a separate issue with respect to list comp behavior. The latter seems peripheral to the purpose of this issue. -- ___ Python tracker __

[issue9090] Error code 10035 calling socket.recv() on a socket with a timeout (WSAEWOULDBLOCK - A non-blocking socket operation could not be completed immediately)

Antoine Pitrou added the comment: > It appears that there is a known issue with Windows sockets where this > type of problem may occur with non-blocking sockets. It is described in > the msdn documentation for WSAAsyncSelect() > (http://msdn.microsoft.com/en-us/library/ms741540%28VS.85%29.aspx

[issue9090] Error code 10035 calling socket.recv() on a socket with a timeout (WSAEWOULDBLOCK - A non-blocking socket operation could not be completed immediately)

Changes by Antoine Pitrou : -- nosy: +exarkun, giampaolo.rodola versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.6 ___ Python tracker ___ __

[issue9090] Error code 10035 calling socket.recv() on a socket with a timeout (WSAEWOULDBLOCK - A non-blocking socket operation could not be completed immediately)

Ben Smith added the comment: I also see this issue on occasion on windows XP SP 3, using python 2.6.5 to fetch large files via http. The error is infrequent, but it is happening in my situation without a VM. -- nosy: +Ben.Smith ___ Python tracker

[issue9863] threading, signals, atexit: different execution with different versions

Corey Bertram added the comment: On second thought, i'll just move forward with this new expected behavior. I understand the design decision and why it was made here in regards to waiting for threads to shutdown before atexit kicks in. My intended use for atexit just no longer works in this p

[issue9863] threading, signals, atexit: different execution with different versions

Corey Bertram added the comment: let me preface this: I'm no expert on how this should be done ect... The goal here was to specifically not set daemon on the test_loop thread. In an actual app test_loop would perhaps need to shutdown cleanly (save state or what have you). That said, your prev

[issue9863] threading, signals, atexit: different execution with different versions

Ned Deily added the comment: A better fix for the program is to mark the test_loop thread as a daemon thread. As the threading module documentation says, by default threads started from the main thread are non-daemon threads and the "entire Python program exits when no alive non-daemon threa

[issue6884] Impossible to include file in sdist that starts with 'build' on Win32

Changes by Éric Araujo : -- keywords: +patch -needs review resolution: -> accepted stage: needs patch -> patch review status: open -> pending ___ Python tracker ___ _

[issue6884] Impossible to include file in sdist that starts with 'build' on Win32

Éric Araujo added the comment: My feeling was that there was a logic bug in filelist (something explicitly added should not be filtered out by a default exclude pattern), so I’m glad to learn it’s just a regex bug. I’ll add a test for the add/filter logic just in case. Thanks a lot for the

[issue9860] Building python outside of source directory fails

Alexander Belopolsky added the comment: On Wed, Sep 15, 2010 at 5:45 PM, Roumen Petrov wrote: .. > Please could you remove object files from source tree then try again. > It looks like you missed my penultimate comment. > This is invalid issue. At the very least, Building Python [1] section c

[issue9865] OrderedDict doesn't implement __sizeof__

Raymond Hettinger added the comment: I have a hard time caring about this. The main value of sys.getsizeof() is to enable developers to determine the internal sizes of basic objects on a given build. IIRC, there was no intention for this to become a requirement for pure python classes.

[issue9866] Inconsistencies in tracing list comprehensions

Alexander Belopolsky added the comment: On Wed, Sep 15, 2010 at 5:33 PM, Antoine Pitrou wrote: .. > As I said in #9315, I think this kind of thing (bytecode traces) is an > implementation detail; the changes > in results shouldn't be regarded as breaking compatibility. In r74132, an attempt w

[issue9860] Building python outside of source directory fails

Roumen Petrov added the comment: Please could you remove object files from source tree then try again. This is invalid issue. -- nosy: +rpetrov ___ Python tracker ___ __

[issue9863] threading, signals, atexit: different execution with different versions

Ned Deily added the comment: I can verify that the test case terminates with 2.6.2 and 2.5.1 but does not for 2.6.6, 2.7, and 3.2. This is indeed almost certainly due to Issue1722344. r75749 moved wait_for_thread_shutdown into Py_Finalize just before the atexit functions are called. The pre

[issue8077] urlparse

Changes by Nick Coghlan : -- title: cgi handling of POSTed files is broken -> urlparse ___ Python tracker ___ ___ Python-bugs-list mail

[issue9865] OrderedDict doesn't implement __sizeof__

Antoine Pitrou added the comment: > > How do you want to "handle this in general"? > > Possibly by adding up __sizeof__'s of base and __dict__ in a generated > function? With a special handling of slots ... I agree that in the general case this would be better, but for OrderedDict it would st

[issue9865] OrderedDict doesn't implement __sizeof__

Alexander Belopolsky added the comment: > How do you want to "handle this in general"? Possibly by adding up __sizeof__'s of base and __dict__ in a generated function? With a special handling of slots ... May prove to be too complicated to be worth the effort. -- __

[issue9866] Inconsistencies in tracing list comprehensions

Antoine Pitrou added the comment: As I said in #9315, I think this kind of thing (bytecode traces) is an implementation detail; the changes in results shouldn't be regarded as breaking compatibility. The only problem I could see would be if a whole line of code would be "forgotten".

[issue9865] OrderedDict doesn't implement __sizeof__

Antoine Pitrou added the comment: How do you want to "handle this in general"? -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue9865] OrderedDict doesn't implement __sizeof__

Alexander Belopolsky added the comment: I wonder if type metaclass can be taught to handle this in general for subclasses implemented in python. -- nosy: +belopolsky ___ Python tracker

[issue1633863] AIX: configure ignores $CC

R. David Murray added the comment: Sébastien, you could email Martin (tracker id loewis) about adding your buildbot to our unstable fleet (or even to stable if it is stable; that is, the tests normally pass and don't randomly fail). As long as you are around to help fix bugs it would be grea

[issue9866] Inconsistencies in tracing list comprehensions

New submission from Alexander Belopolsky : Attached test script, tracetest.py, prints disassembly followed by a trace of the following function: 1 def f(): 2 return [i 3 for i 4 in range(2)] With default configuration, the output is 2 0 LOAD_CONS

[issue9360] nntplib cleanup

Changes by Antoine Pitrou : Added file: http://bugs.python.org/file18894/nntplib_cleanup4.patch ___ Python tracker ___ ___ Python-bugs-list mai

[issue9865] OrderedDict doesn't implement __sizeof__

New submission from Antoine Pitrou : Ordered dicts pretend to have the memory consumption as dicts: >>> import sys, collections >>> sys.getsizeof({}) 280 >>> sys.getsizeof(collections.OrderedDict()) 280 -- components: Library (Lib) messages: 116481 nosy: pitrou, rhettinger priority: low

[issue9863] threading, signals, atexit: different execution with different versions

R. David Murray added the comment: I can confirm this, and that it works on python2.5 (I don't have a 2.6.2 around to test). It also has the looping behavior on 2.7 and 3.2. Given the timing, I wonder if this is the result of the fix to issue 1722344. (Note, I removed 2.6 because it doesn't

[issue678264] test_resource fails when file size is limited

R. David Murray added the comment: As a point of information, on my gentoo linux system without largefile support in the kernel, any value 4294967295 or above results in getrlimit reporting -1. Any smaller value is set and reported as itself. (If a sufficiently large value is passed in to s

[issue9315] The trace module lacks unit tests

Alexander Belopolsky added the comment: Raymond asked on IRC why this work is being back-ported. The answer is that it is being forward-ported rather than back-ported. The trace module had no unittests in either 2.x or 3.x and was very buggy in 3.x. Presumably, 2.x version saw more use and

[issue9854] SocketIO should return None on EWOULDBLOCK

Antoine Pitrou added the comment: > Of course, I should have been more clear. > What I meant is that there's no such thing as explicit and "native" as > setblocking() for plain files. Indeed. It would probably be a nice addition, assuming it is portable enough. > > A BlockingIOError is raised

[issue9756] Crash with custom __getattribute__

Changes by Daniel Urban : -- nosy: +durban ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue9746] All sequence types support .index and .count

Changes by Daniel Urban : -- nosy: +durban ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue9807] deriving configuration information for different builds with the same prefix

Barry A. Warsaw added the comment: @Martin: yep, I know we still need to install pyconfig.h and Makefile, but we shouldn't need to parse them to get programmatic access to the data they contain. -- ___ Python tracker

[issue4761] create Python wrappers for openat() and others

Changes by Daniel Urban : -- nosy: +durban ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue9864] email.utils.{parsedate, parsedate_tz} should have better return types

Antoine Pitrou added the comment: By the way, while as mentioned in the docs “indexes 6, 7, and 8 of the result tuple are not usable”, perhaps it would be time to fix it? (at least for 6 and 7, aka. wday and yday) -- ___ Python tracker

[issue9864] email.utils.{parsedate, parsedate_tz} should have better return types

Barry A. Warsaw added the comment: +1 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue9861] subprocess module changed exposed attributes

Changes by Giampaolo Rodola' : -- nosy: +giampaolo.rodola ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue9864] email.utils.{parsedate, parsedate_tz} should have better return types

New submission from Antoine Pitrou : They both return raw tuples, which are not very intuitive to interpret: >>> email.utils.parsedate_tz("Wed, 15 Sep 2010 09:53:50 -0700 (PDT)") (2010, 9, 15, 9, 53, 50, 0, 1, -1, -25200) It would be much better if they returned some kind of namedtuple, which w

[issue9863] threading, signals, atexit: different execution with different versions

New submission from Corey Bertram : my code works on python 2.6.2 and fails to work on python 2.6.5. What's going on here? import atexit, sys, signal, time, threading terminate = False threads = [] def test_loop(): while True: if terminate: print('stopping thread')

[issue9863] threading, signals, atexit: different execution with different versions

Changes by Corey Bertram : -- nosy: cbertram priority: normal severity: normal status: open title: threading, signals, atexit: different execution with different versions type: behavior versions: Python 2.6 ___ Python tracker

[issue9854] SocketIO should return None on EWOULDBLOCK

Giampaolo Rodola' added the comment: > Non-blocking files exist Of course, I should have been more clear. What I meant is that there's no such thing as explicit and "native" as setblocking() for plain files. > Returning None is what raw I/O objects are supposed to do when they > fail reading

[issue9759] GzipFile object should raise ValueError on .read() after .close()

Jeffrey Finkelstein added the comment: Here's the updated patch, which checks whether the file is closed on each call to read(), write(), and flush(), along with a test. -- Added file: http://bugs.python.org/file18893/issue9759.patch ___ Python trac

[issue9315] The trace module lacks unit tests

Alexander Belopolsky added the comment: I am attaching another test file, y.py, which shows that the cause of discrepancy is outside of the trace module. The traced function is the same as in x.py only with 5 iterations instead of 10 for brevity, but instead of using trace module, I am regist

[issue9858] Python and C implementations of io are out of sync

Benjamin Peterson added the comment: 2010/9/15 Daniel Stutzbach : > > Daniel Stutzbach added the comment: > > Roundup does not play well with Gmail when Gmail is in Rich Format mode ;-) > > That example should have read: > f = io.FileIO(1) f.name > 1 Hmm, none the less other code exp

[issue9315] The trace module lacks unit tests

Changes by Alexander Belopolsky : Added file: http://bugs.python.org/file18891/x.py ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue9862] test_subprocess hangs on AIX

New submission from Sébastien Sablé : On AIX, the test test_communicate_pipe_buf in test_subprocess will hang forever (in py3k and py27): test_communicate_pipe_buf (__main__.ProcessTestCase) ... File "Lib/test/test_subprocess.py", line 386, in test_communicate_pipe_buf (stdout, stderr)

[issue9315] The trace module lacks unit tests

Alexander Belopolsky added the comment: > Is it really *interesting* to trace separate parts of list > comprehensions like this? It may or may not be useful for tracing code in the wild, but it helps to isolate the causes of count mismatches. I am attaching a file, x.py, that shows differing

[issue1633863] AIX: configure ignores $CC

Sébastien Sablé added the comment: Antoine, I tested your commit with cc_r and it compiles fine (I have buildbot running now, just need to find a way to make the results publicly browsable). I still think xlc_r would be a better choice as a default: at the moment ctypes will not compile on AI

[issue9315] The trace module lacks unit tests

Changes by Alexander Belopolsky : Removed file: http://bugs.python.org/file1/unnamed ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue9858] Python and C implementations of io are out of sync

Daniel Stutzbach added the comment: Roundup does not play well with Gmail when Gmail is in Rich Format mode ;-) That example should have read: >>> f = io.FileIO(1) >>> f.name 1 -- ___ Python tracker _

[issue9858] Python and C implementations of io are out of sync

Changes by Daniel Stutzbach : Removed file: http://bugs.python.org/file18890/unnamed ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue9858] Python and C implementations of io are out of sync

Daniel Stutzbach added the comment: On Wed, Sep 15, 2010 at 10:51 AM, Benjamin Peterson wrote: > I'm not sure if this pickling stuff matters as long as they both pickle. > I'm not sure either. Do other Python implementations try to maintain a compatible pickle format with CPython? If so, I t

[issue9858] Python and C implementations of io are out of sync

Benjamin Peterson added the comment: 2010/9/15 Daniel Stutzbach : > > Daniel Stutzbach added the comment: > >> These attributes exist; they're just not properties. > > Yes, I see. They're added to the instance in the constructor, so they don't > exist as attributes of the class. Also in that

[issue6884] Impossible to include file in sdist that starts with 'build' on Win32

Chris Withers added the comment: Okay, so here's the patch: Change line 352 on distutils/filelist.py from: pattern_re = "^" + os.path.join(prefix_re, ".*" + pattern_re) To: pattern_re = "^"+prefix_re+re.escape(os.sep)+".*"+pattern_re os.path.join is is not always the saviour ;-) --

[issue9858] Python and C implementations of io are out of sync

Daniel Stutzbach added the comment: > These attributes exist; they're just not properties. Yes, I see. They're added to the instance in the constructor, so they don't exist as attributes of the class. Also in that category: BlockingIOError python is missing: ['characters_written'] That lea

[issue9860] Building python outside of source directory fails

Alexander Belopolsky added the comment: > (what is VPATH?) VPATH is a search path that make uses to find targets and prerequisites. configure sets it to its own location when invoked from a directory other than cwd. -- ___ Python tracker

[issue9860] Building python outside of source directory fails

Alexander Belopolsky added the comment: It turns out that make only gets confused when target files (Parser/pgenmain.o etc.) exist in the source directory. Thus an obvious workaround is to build all versions in alternative directories or delete object files from source tree before alternativ

[issue6884] Impossible to include file in sdist that starts with 'build' on Win32

Chris Withers added the comment: So, the workaround I gave doesn't work, because this stupid regex still knocks out all the egg-info. The only solution is to use that accidentally employed by http://svn.plone.org/svn/collective/buildout/buildout.dumppickedversions/trunk/ and put any files sta

[issue9860] Building python outside of source directory fails

Antoine Pitrou added the comment: It works here (Linux). Did you try make distclean first? Also, try to remove the various files created by configure. (what is VPATH?) -- nosy: +pitrou ___ Python tracker

[issue9858] Python and C implementations of io are out of sync

Benjamin Peterson added the comment: 2010/9/15 Daniel Stutzbach : > > Daniel Stutzbach added the comment: > > Attached is a script to find all of the mismatches between the C and Python > implementations.  There are several.  Below is the output: > > BufferedRandom python is missing: ['raw'] >

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.3" but "10.5" during configure

Stonewall Ballard added the comment: I just ran into this with Python 2.7, installed using port. I'm using python to process a text file in an Xcode 3.2 Script build step, and it's throwing the error because my Xcode target has a base sdk of 10.5. -- nosy: +stoneyb __

[issue9859] Add tests to verify API match of modules with 2 implementations

Daniel Stutzbach added the comment: Yes, exactly. :-) (see also Issue9731, which has a similar flavor) -- ___ Python tracker ___ ___

[issue9859] Add tests to verify API match of modules with 2 implementations

R. David Murray added the comment: Shouldn't the test suite catch such discrepancies by testing all of the API? So your script catching something would be the equivalent of "oops, we forgot a test" (or "oops, this name shouldn't be public"). Which is not a bad thing to have as part of the t

[issue9860] Building python outside of source directory fails

Alexander Belopolsky added the comment: I think the problem is with the following explicit rules in Makefile: Parser/tokenizer_pgen.o:$(srcdir)/Parser/tokenizer.c Parser/pgenmain.o: $(srcdir)/Include/parsetok.h It looks like these rules are not VPATH friendly. Per Antoine's sug

[issue9861] subprocess module changed exposed attributes

New submission from paul clinch : Some attributes, e.g. STARTF_USESHOWWINDOW have moved to _subrocess.STARTF_USESHOWWINDOW. This breaks old code. -- components: Library (Lib) messages: 116450 nosy: pclinch priority: normal severity: normal status: open title: subprocess module changed e

[issue678264] test_resource fails when file size is limited

R. David Murray added the comment: The test does not fail if FSIZE is not max on linux/py3k, but max is still represented as -1 on linux. So the reported bug is no longer valid, but Martin's concern has not been addressed. -- nosy: +r.david.murray ___

[issue9860] Building python outside of source directory fails

New submission from Alexander Belopolsky : When testing config options, it is often useful to build python in a directory different from the root of the source tree. This is supported by autoconf based builds as follows: you cd to the desired directory run configure with an explicit path. For

[issue9857] SkipTest in tearDown is reported an as an error

Changes by Raghuram Devarakonda : -- nosy: +draghuram ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue9851] multiprocessing socket timeout will break client

Jesse Noller added the comment: Calling it stupid doesn't incentivize me to help you, or fix it. -- ___ Python tracker ___ ___ Python-

[issue9858] Python and C implementations of io are out of sync

Daniel Stutzbach added the comment: FWIW, I just opened Issue9859: Add tests to verify API match of modules with 2 implementations. -- ___ Python tracker ___ ___

[issue9859] Add tests to verify API match of modules with 2 implementations

New submission from Daniel Stutzbach : Recently it came to light that the classes in C and Python implementations of the io module have slightly different attributes (issue9858). I propose the addition of a helper function in Lib/test/support.py to verify that the classes in two different imp

[issue9858] Python and C implementations of io are out of sync

Daniel Stutzbach added the comment: Attached is a script to find all of the mismatches between the C and Python implementations. There are several. Below is the output: RawIOBase C is missing: ['readinto', 'write'] StringIO C is missing: ['name'] StringIO python is missing: ['__getstate__',

[issue9858] RawIOBase doesn't define readinto

Antoine Pitrou added the comment: > +1 for a failing one. (Does the base implementation not raise?) The base implementation doesn't exist :) > Is it even possible to implement a real one without buffering? FileIO does. It's the same as read(), except that you read into an existing buffer rat

[issue9858] RawIOBase doesn't define readinto

Benjamin Peterson added the comment: +1 for a failing one. (Does the base implementation not raise?) Is it even possible to implement a real one without buffering? -- ___ Python tracker ___

[issue9857] SkipTest in tearDown is reported an as an error

Michael Foord added the comment: Interesting use case. If the test has not yet failed this is fine. The problem is that if an exception has *already* been raised then it will already have been added to the result - so by then skipping is meaningless (or contradictory - the test can fail *and

[issue9858] RawIOBase doesn't define readinto

Changes by Antoine Pitrou : -- nosy: +benjamin.peterson, stutzbach ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue9858] RawIOBase doesn't define readinto

New submission from Antoine Pitrou : RawIOBase is defined as having the readinto() method but it doesn't. It should at least have a failing one (raising io.UnsupportedOperation like the BufferedIOBase.{read,readinto} methods do). This is, of course, mainly for auto-documenting purposes (with h

[issue9315] The trace module lacks unit tests

Changes by Antoine Pitrou : -- Removed message: http://bugs.python.org/msg116438 ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue9315] The trace module lacks unit tests

Eli Bendersky added the comment: Is it really *interesting* to trace separate parts of list comprehensions like this? What would one want to do that? The only idea I have in mind of perhaps for comprehensions containing 'if's, to know how many times the comprehension was actually executed. In a

[issue9315] The trace module lacks unit tests

teresap989 added the comment: I was about to commit issue9315.3.patch, which is a lightly modified version of issue9315.2.patch, but it turned out that test_trace cannot be run by regrtest.py: $ ./python.exe Lib/test/regrtest.py test_trace test_trace test test_trace failed -- multiple errors

[issue9759] GzipFile object should raise ValueError on .read() after .close()

Antoine Pitrou added the comment: You should make sure that all operations (except close() itself) raise ValueError. Currently: >>> f = gzip.open("test.gz", "rb") >>> f.close() >>> f.read() b'' >>> f.seek(0) 0 Also, you don't have to post a patch for 2.7. We'll do the porting ourselves. Thank

[issue9315] The trace module lacks unit tests

Antoine Pitrou added the comment: > It looks like 3.1 with computed gotos produces the yet another different > tracing of list comprehensions: > > > 2: l = [i for >10: i in > 1: range(10)] Well, this kind of thing is going to depend on the exact bytecode, the way the ev