[issue12852] test_posix.test_fdlistdir() segfault on OpenBSD
Charles-François Natali neolo...@free.fr added the comment: I think that the problem is that fdopendir() is not defined. If a function is not defined, C uses int as the result type. An int is not enough to store a 64-bit pointer. See in gdb output: dirp is 0x0afb0e80 whereas other pointers look like 0x20973fc30. You missed the highest hexa digit (0x2). Yeah, I noticed that. I didn't make the connection with the possibility of missing prototype though. Nice catch. I tried AC_DEFINE(_POSIX_C_SOURCE, 200809L, Define to activate features from IEEE Stds 1003.1-2008) but it doesn't work. You mean that the patch you attached doesn't work, correct? I know it's a stupid question, but you're sure you didn't forget to run autoconf/autoheader? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12852 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12852] test_posix.test_fdlistdir() segfault on OpenBSD
STINNER Victor victor.stin...@haypocalc.com added the comment: I tried AC_DEFINE(_POSIX_C_SOURCE, 200809L, Define to activate features from IEEE Stds 1003.1-2008) but it doesn't work. You mean that the patch you attached doesn't work, correct? I ran autoconf, re-ran configure and it doesn't work. You can test without touching configure.in: edit pyconfig.h directly. On Linux, all features flags are defined/undefined in /usr/include/features.h. Depending on _POSIX_C_SOURCE, _XOPEN_SOURCE, _BSD_SOURCE, ..., you get a different POSIX level. For example: /* If _GNU_SOURCE was defined by the user, turn on all the other features. */ #ifdef _GNU_SOURCE # undef _ISOC99_SOURCE # define _ISOC99_SOURCE 1 # undef _POSIX_SOURCE # define _POSIX_SOURCE 1 # undef _POSIX_C_SOURCE # define _POSIX_C_SOURCE200809L # undef _XOPEN_SOURCE # define _XOPEN_SOURCE 700 # ... #endif I suppose that there is a conflict between Python's _POSIX_C_SOURCE and other defines related to the POSIX level. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12852 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12855] linebreak sequences should be better documented
STINNER Victor victor.stin...@haypocalc.com added the comment: Would it be better to put this note in a different place? You may just say that StreamReader.readline() uses unicode.splitlines(), and so point to unicode.splitlines() doc (use :meth:`unicode.splitlines` syntax). unicode.splitlines() is now well documented: line boundaries are not listed, even in Python 3 documentation. Unicode line boundaries used by Python 2.7 and 3.3: U+000A: Line feed U+000B: Line tabulation U+000C: Form feed U+000D: Carriage return U+001C: File separator U+001D: Group separator U+001E: Record separator U+0085: control U+2028: Line separator U+2029: Paragraph separator It looks like \x0b and \x0c (vertical tab and form feed) were first considered line breaks in Python 2.7 Correct: U+000B and U+000C were added to Python 2.7 and 3.2. It might be worth putting a changed in 2.7 note somewhere in the docs We add the following syntax exactly for this: .. versionchanged:: 2.6 Also unset environment variables when calling :meth:`os.environ.clear` and :meth:`os.environ.pop`. If you downloaded Python source code, go into Doc/ directory and run make html to compile the doc to HTML. http://docs.python.org/devguide/setup.html http://docs.python.org/devguide/docquality.html -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12855 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12855] linebreak sequences should be better documented
Changes by STINNER Victor victor.stin...@haypocalc.com: -- components: +Unicode versions: +Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12855 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7171] Add inet_ntop and inet_pton support for Windows
Changes by honglei jiang jhong...@gmail.com: -- nosy: +honglei.jiang ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7171 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10278] add time.wallclock() method
STINNER Victor victor.stin...@haypocalc.com added the comment: I think that we should process in two steps: * Expose low level C functions * Write a high level reusing the best low level function depending on the OS Low level functions: * Expose clock_gettime() into the time module, with CLOCK_MONOTONIC and CLOCK_MONOTONIC_RAW constants, if available. The wrapper should be thin, so the result would be a tuple (sec, nsec) (to avoid issues with floating point numbers) * Windows: GetTickCount, GetTickCount64 and QueryPerformaceCounter are monotonic. GetTickCount wraps after 50 days, so GetTickCount64 should be preferred. GetTickCount(64) returns a number of milliseconds. It looks like QueryPerformaceCounter has a better resolution than GetTickCount(64). I don't know when QueryPerformaceCounter does wrap? QueryPerformaceCounter is already exposed as time.clock(). High level: * Use clock_gettime(CLOCK_MONOTONIC_RAW) on Linux=2.6.28 * Use clock_gettime(CLOCK_MONOTONIC) on UNIX * Use time.clock() (QueryPerformaceCounter) on Windows? * If none of these functions is available, don't define the function I propose time.monotonic() because I saw this name in different projects. Pseudo-code for the time module: monotonic = None if hasattr(time, 'clock_gettime'): if hasattr(time, 'CLOCK_MONOTONIC_RAW'): def monotonic(): return time.clock_gettime(CLOCK_MONOTONIC_RAW) else: # i don't think that we should expose clock_gettime # if CLOCK_MONOTONIC is not available (or the function is useless) def monotonic(): return time.clock_gettime(CLOCK_MONOTONIC) elif os.name == 'nt': def monotonic(): return time.clock() if monotonic is not None: monotonic.__doc__ = 'monotonic time' else: del monotonic -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10278 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10278] add time.wallclock() method
STINNER Victor victor.stin...@haypocalc.com added the comment: Note: it would be very pratical if time.monotonic() has always the same unit on all platforms. clock_gettime() uses seconds (and nanoseconds), time.clock() uses also seconds. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10278 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12857] Expose called function on frame object
Changes by Daniel Urban urban.dani...@gmail.com: -- nosy: +durban ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12857 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12850] [PATCH] stm.atomic
Changes by Daniel Urban urban.dani...@gmail.com: -- nosy: +durban ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12850 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12852] test_posix.test_fdlistdir() segfault on OpenBSD
Remi Pointel pyt...@xiri.fr added the comment: Hi, this is the result of gcc -E on Modules/posixmodule.o, asked by haypo. Thanks for your help, Cheers, Remi. -- Added file: http://bugs.python.org/file23072/gcc-E-Modules_posixmodule_output ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12852 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12850] [PATCH] stm.atomic
Nick Coghlan ncogh...@gmail.com added the comment: Nothing specific, just a reflexive C++ induced dislike for linker-accessible globals in general. However, while I slightly prefer the function driven API, I wouldn't actively oppose direct linker access if someone else wanted to check it in :) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12850 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10278] add time.wallclock() method
Kristján Valur Jónsson krist...@ccpgames.com added the comment: The problem with QueryPerformanceCounter is that it drifts. It has high resolution, but can drift far out of sync with GetTickCount64. The best solutions on windows combine the two, but that's tricky to impolement. QPC will wrap, but only after a long time. its 64 bits, and with a frequency of 1GHz, that takes some 600 years. Of course, with 10GHz we're down to 60 years, but by that time, we will have python 2.8 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10278 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11682] PEP 380 reference implementation for 3.3
Nick Coghlan ncogh...@gmail.com added the comment: The pep380 branch in my bitbucket repo has been updated with the refactored tests that Ryan Kelly put together at the PyconAU sprints (as well as being brought up to speed with 3.x tip). The update depends on the new dis.get_opinfo() API added by issue #11816 (which is currently with Raymond for review). The AST validator still needs to be updated to take into account the new syntax and the patch attribution needs to be updated to account for Ryan's contribution, but this is getting fairly close to being ready. -- nosy: +rhettinger ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11682 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12850] [PATCH] stm.atomic
Armin Rigo ar...@users.sourceforge.net added the comment: Ok, I followed Nick's suggestion, and I finally found out how to write the code in order to avoid all (or most?) deadlocks without any change in the rest of CPython. It requires a way to be sure that some callback function is invoked _at the next cross-bytecode point_, and not (or not much) later, which I also include here. Here is the updated patch. -- Added file: http://bugs.python.org/file23073/stm2.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12850 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10946] bdist doesn’t pass --skip-build on to subcommands
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 326a7e44bb66 by Éric Araujo in branch '3.2': Make bdist_* commands respect --skip-build passed to bdist (#10946) http://hg.python.org/cpython/rev/326a7e44bb66 New changeset 2f69b4f3df2e by Éric Araujo in branch 'default': Merge fix for #10946 from 3.2 http://hg.python.org/cpython/rev/2f69b4f3df2e New changeset afb12c6b79ba by Éric Araujo in branch 'default': Make bdist_* commands respect --skip-build passed to bdist (#10946). http://hg.python.org/cpython/rev/afb12c6b79ba -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10946 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10946] bdist doesn’t pass --skip-build on to subcommands
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 4ff92eb1a915 by Éric Araujo in branch '2.7': Make bdist_* commands respect --skip-build passed to bdist (#10946) http://hg.python.org/cpython/rev/4ff92eb1a915 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10946 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9041] raised exception is misleading
Meador Inge mead...@gmail.com added the comment: That is a good question. While it is true that errors other than 'PyExc_OverflowError', will be mapped onto a 'TypeError' I don't think that is a bad thing. Any errors that come out of 'PyFloat_AsDouble' should be handled on a case-by-case basis and not blindly passed back out the call chain. Otherwise, we may end up passing back errors (which are who knows what) that make sense for a caller of 'PyFloat_AsDouble', but not for callers of 'g_set'. Also, the interface would become variable, meaning that whenever 'PyFloat_AsDouble' introduces new exceptions, then this code would too, which would lead to a somewhat unpredictable interface for callers of 'g_set'. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9041 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12858] crypt.mksalt: use ssl.RAND_pseudo_bytes() if available
New submission from STINNER Victor victor.stin...@haypocalc.com: A salt doesn't need to be strong random bits, but I'm not sure that Mersenne Twister is a best candidate to generate salt. It would be nice to use ssl.RAND_pseudo_bytes() if available. Problem: implement random.choice() from a generator generating bytes = see issue #12754. -- components: Extension Modules messages: 143215 nosy: haypo priority: normal severity: normal status: open title: crypt.mksalt: use ssl.RAND_pseudo_bytes() if available versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12858 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12858] crypt.mksalt: use ssl.RAND_pseudo_bytes() if available
Changes by Éric Araujo mer...@netwok.org: -- nosy: +jafo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12858 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12754] Add alternative random number generators
STINNER Victor victor.stin...@haypocalc.com added the comment: Before trying to find the best (CS)PRNG, can't we start with ssl.RAND_bytes() and ssl.RAND_pseudo_bytes()? I would be nice to use ssl.RAND_pseudo_bytes() to generate crypt.mksalt(): see issue #12858 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12754 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12855] linebreak sequences should be better documented
Matthew Boehm boehm.matt...@gmail.com added the comment: I can fix the patch to list all the unicode line boundaries. The three places I've considered putting it are: 1. On the howto/unicode.html 2. Somewhere in the stdtypes.html#typesseq description (maybe with other notes at the bottom) 3. As a note to the stdtypes.html#str.splitlines method description (where it is in the previous patch.) I can move it to any of these places if you think it's a better fit. I'll fix the list so that it's complete, add a note about \x0b and \x0c being added in 2.7/3.2, and possibly reference it from StreamReader.readline. After confirming that my documentation matches the style guide, I'll make the docs, test the output, and upload a patch. I can do this for 2.7, 3.2 and 3.3 separately. Let me know if that sounds good and if you have any further thoughts. I should be able to upload new patches in 10 hours (after work today). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12855 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10946] bdist doesn’t pass --skip-build on to subcommands
Éric Araujo mer...@netwok.org added the comment: I simplified my patch and pushed it. I had to discover again that I needed to inject customized command objects into dist.command_obj, like you found out a few months ago when we had a private email discussion :) Using set_undefined_options in install_* is definitely not safe, because it fails if parent [command] has not set skip_build. We can be sure (by looking at the code) that bdist always sets skip_build to something (False by default), so it’s not unsafe. Also skip_build has to be set to None in install_* (set_... needs that to work) which obviously breaks it. Yes, skip_build on the subcommands needed to change from None to False, but I don’t see how it is a breakage; it’s just an harmless change needed for this bug fix, so I did it. :) Thanks to everyone involved in this bug. -- resolution: - fixed stage: commit review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10946 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12759] (?P=) input for Tools/scripts/redemo.py raises unnhandled exception
Éric Araujo mer...@netwok.org added the comment: Great! Feel free to ask any questions here or through the core-mentorship mailing list. Remember to read the devguide and work from a Mercurial clone of Python 3.2. Thanks! -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12759 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12855] linebreak sequences should be better documented
STINNER Victor victor.stin...@haypocalc.com added the comment: 1. On the howto/unicode.html 2. Somewhere in the stdtypes.html#typesseq description (maybe with other notes at the bottom) 3. As a note to the stdtypes.html#str.splitlines method description (where it is in the previous patch.) (3) is the best place. For Python 2, you should add a new unicode.splitlines entry, whereas the str.splitlines should be updated in Python 3. I can do this for 2.7, 3.2 and 3.3 separately. You don't have to do it for 3.3: 2.7 and 3.2 are enough (I will do the change in 3.3 using Mercurial). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12855 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2945] bdist_rpm does not list dist files (should effect upload)
Éric Araujo mer...@netwok.org added the comment: Even thought bdist_rpm is gone from distutils2, this is a bug that can be fixed in distutils. Adding the easy keyword to let potential contributors find this bug; hint: look at how bdist_dumb registers distributions with dist.dist_files. -- keywords: +easy stage: - needs patch versions: +Python 3.3 -Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2945 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12853] global name 'r' is not defined in upload.py
Éric Araujo mer...@netwok.org added the comment: Does it work if you replace r with result? -- versions: -Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12853 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9041] raised exception is misleading
Changes by Éric Araujo mer...@netwok.org: -- nosy: -eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9041 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1215] documentation doesn't say that you can't handle C segfaults from python
Changes by Éric Araujo mer...@netwok.org: -- nosy: +eric.araujo, haypo versions: +Python 3.3 -Python 2.6, Python 2.7, Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1215 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12829] pyexpat segmentation fault caused by multiple calls to Parse()
Terry J. Reedy tjre...@udel.edu added the comment: My understanding is that what you did: import xml.parsers.expat is now the proper way to use expat. After some searching, it seems the sentence about direct use of pyexpat being deprecated refers to http://sourceforge.net/tracker/?func=detailaid=2745230group_id=26590atid=387667 The location and name of the PyExpat module have moved in Python v2.6.1 from xml.dom.ext.reader.PyExpat to xml.parsers.expat This is puzzling becasue xmo.parsers.expat dates back to 2.0 while I see no doc for xml.dom.ext... . The deprecation notice should be deleted from the 3.x docs. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12829 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12829] pyexpat segmentation fault caused by multiple calls to Parse()
Terry J. Reedy tjre...@udel.edu added the comment: This seems to be a Mac-only issue. Barry, does this seem to be a security issue to you, or should we delete 2.6 from the versions? -- assignee: - ronaldoussoren components: +Macintosh nosy: +barry, ned.deily, ronaldoussoren ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12829 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12555] PEP 3151 implementation
Changes by Antoine Pitrou pit...@free.fr: Added file: http://bugs.python.org/file23074/8a0e40f4f004.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12555 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12555] PEP 3151 implementation
Antoine Pitrou pit...@free.fr added the comment: Here is a new patch implementing the latest PEP changes. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12555 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12859] readline implementation doesn't release the GIL
New submission from Albert Zeyer alb...@googlemail.com: Modules/readline.c 's `call_readline` doesn't release the GIL while reading. -- messages: 143226 nosy: Albert.Zeyer priority: normal severity: normal status: open title: readline implementation doesn't release the GIL versions: Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12859 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12860] http client attempts to send a readable object twice
New submission from Lang Martin lang.mar...@gmail.com: on line 765 of client/http.py, the client loops over the read method, sending it's content to the web server. It appears as though the send method should return at this point; instead it falls through and attempts to send the data object through first self.sock.sendall, falling back to the iterable interface. The result is that a readable data object must support a null __iter__ method, or if it supports both a working read and __iter__, the data will be sent to the server twice. Change the break on line 768 to a return, and the expected behavior happens. -- messages: 143227 nosy: langmartin priority: normal severity: normal status: open title: http client attempts to send a readable object twice type: behavior versions: Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12860 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12859] readline implementation doesn't release the GIL
Albert Zeyer alb...@googlemail.com added the comment: Whoops, sorry, invalid. It doesn't need to. It is handled in PyOS_Readline. -- resolution: - invalid status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12859 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12861] PyOS_Readline uses single lock
New submission from Albert Zeyer alb...@googlemail.com: In Parser/myreadline.c PyOS_Readline uses a single lock (`_PyOS_ReadlineLock`). I guess it is so that we don't have messed up stdin reads. Or are there other technical reasons? However, it should work to call this function from multiple threads with different/independent `sys_stdin` / `sys_stdout`. -- messages: 143229 nosy: Albert.Zeyer priority: normal severity: normal status: open title: PyOS_Readline uses single lock versions: Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12861 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12862] ConfigParser does not implement comments need to be preceded by a whitespace character correctly
New submission from Daniel Fortunov pythonbugtrac...@danielfortunov.com:
ConfigParser does not implement comments need to be preceded by a whitespace
character correctly and in most cases will treat a value beginning with a
comment character as a comment, even though it is not preceded by a whitespace
character.
The ConfigParser documentation states:
Comments may appear on their own in an otherwise empty line, or may be entered
in lines holding values or section names. In the latter case, they need to be
preceded by a whitespace character to be recognized as a comment.
This suggests that in the following configuration file, the value of 'password'
would be read as ';23bUx1'.
[test_config]
password=;23bUx1
username=bar
In fact, there appears to be a bug in the following code within
RawConfigParser._read():
if vi in ('=', ':') and ';' in optval:
# ';' is a comment delimiter only if it follows
# a spacing character
pos = optval.find(';')
if pos != -1 and optval[pos-1].isspace():
optval = optval[:pos]
optval = optval.strip()
For the example file above, vi==';' and optval==';23bUx1\r'. pos therefore
takes the value 0, and the second part of the compound if statement which
checks if the preceding character is a space ends up looking at optval[-1] --
the last character in optval -- which is \r, since it has not yet been stripped.
I think this can be resolved by changing the line:
if pos != -1 and optval[pos-1].isspace():
to:
if pos 0 and optval[pos-1].isspace():
Thus, the if preceded by a space case is only considered if the comment
character appears *after* the first character in the value. (And if it appears
as the very *first* character, then by definition it cannot be preceded by a
space!)
A rather fragile workaround (which works only if there is only one single value
affected by this bug) would be to ensure that the affected value is defined on
the last line of your config file, the file does not end with a carriage
return. In this case, the optval[-1] would return a non-whitespace character
and prevent the value being considered a comment.
The above analysis pertains to Python 2.7.2, and I see that the implementation
has been re-written in python 3 so this bug doesn't seem to exist there.
--
components: Library (Lib)
messages: 143230
nosy: DanielFortunov
priority: normal
severity: normal
status: open
title: ConfigParser does not implement comments need to be preceded by a
whitespace character correctly
type: behavior
versions: Python 2.7
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12862
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12844] Support more than 255 arguments
Changes by Brett Cannon br...@python.org: -- nosy: +brett.cannon ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12844 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12861] PyOS_Readline uses single lock
Albert Zeyer alb...@googlemail.com added the comment: Ok, it seems that the Modules/readline.c implementation is also not really threadsafe... (Whereby, I think it should be.) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12861 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1462440] socket and threading: udp multicast setsockopt fails
Changes by Charles-François Natali neolo...@free.fr: -- resolution: - invalid stage: needs patch - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1462440 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12863] py32 Lib xml.minidom usage feedback overrides
New submission from GPU Group gpugr...@gmail.com:
Py32 Lib xml.dom.minidom usage feedback overrides
I like the minidom. I use it -and over-ride the Element.writexml() and
_write_data() methods for a few of my Blender.org B259 personal export scripts
to formats:
.x3d - a www.web3d.org public format, an xml-like version of vitual reality
.vrml, except it wants single quotes with double quotes inside:
'EXAMINE ANY'. It's an attribute heavy format.
.kml - an earth.google.com format, element heavy. By default minidom puts extra
lines backslash n so the following comes out on 3 lines:
description
1909 era from 1891 to 1930
/description
and I want something more compact on one line:
description1909 era from 1891 to 1930/description
In both cases I over-ride the minidom:
save_original_writexml = xml.dom.minidom.Element.writexml
xml.dom.minidom.Element.writexml = writexml_pluto
... do my exporting ...
# other registered scripts share the minidom, so restore it
xml.dom.minidom.Element.writexml = save_original_writexml
I'm happy with this, as long as I remember to update my minidom overrides with
new py versions. I mention it in case I'm using it wrong or in case you like
what I'm doing and want to adopt or spread the word.
more...
kml over-ride for compact element-heaviness:
def _write_data_orig(writer, data):
Writes datachars to writer.
if data:
data = data.replace(, amp;).replace(, lt;). \
replace(\, quot;).replace(, gt;)
writer.write(data)
def writexml_plutokml(self, writer, indent=, addindent=, newl=):
# indent = current indentation
# addindent = indentation to add to higher levels
# newl = newline string
writer.write(indent+ + self.tagName)
attrs = self._get_attributes()
a_names = sorted(attrs.keys())
for a_name in a_names:
writer.write( %s=\ % a_name)
_write_data_orig(writer, attrs[a_name].value)
writer.write(\)
if self.childNodes:
#pluto- writer.write(%s%(newl))
writer.write() # pluto+
tx = False # pluto+
k=0 # pluto+
for node in self.childNodes:
k=k+1 # p+
if node.nodeType == Node.TEXT_NODE: # p+
node.writexml(writer,,,) # p+
tx = True # p+
else:# p+
if k == 1: writer.write(newl) # p+
node.writexml(writer, indent + addindent, addindent, newl)
if tx: # p+
writer.write(%s/%s%s % (,self.tagName,newl)) # p+
else: # p+
writer.write(%s/%s%s % (indent, self.tagName, newl))
else:
writer.write(/%s%(newl))
x3d over-ride for apos (versus quote) attribute delimeters:
def _write_data_pluto(writer, data):
Writes datachars to writer.
if data:
data = data.replace(, amp;).replace(, lt;). \
replace(', apos;).replace(, gt;) # pluto:
apos instead of quot
writer.write(data)
def writexml_pluto(self, writer, indent=, addindent=, newl=):
# indent = current indentation
# addindent = indentation to add to higher levels
# newl = newline string
writer.write(indent+ + self.tagName)
attrs = self._get_attributes()
a_names = sorted(attrs.keys())
for a_name in a_names:
writer.write( %s=' % a_name) # pluto, orig: writer.write(
%s=\ % a_name)
_write_data_pluto(writer, attrs[a_name].value)
writer.write(') # pluto, orig: writer.write(\)
if self.childNodes:
writer.write(%s % (newl))
for node in self.childNodes:
node.writexml(writer, indent+addindent, addindent, newl)
writer.write(%s/%s%s % (indent, self.tagName, newl))
else:
writer.write(/%s%(newl))
--
components: XML
messages: 143232
nosy: GPU.Group
priority: normal
severity: normal
status: open
title: py32 Lib xml.minidom usage feedback overrides
type: behavior
versions: Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12863
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9651] ctypes crash when writing zerolength string buffer to file
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 4aa00f465b4f by Amaury Forgeot d'Arc in branch '2.7': Issue #9651: Fix a crash when ctypes.create_string_buffer(0) was passed to http://hg.python.org/cpython/rev/4aa00f465b4f -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9651 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9651] ctypes crash when writing zerolength string buffer to file
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 5df1609fbd8f by Amaury Forgeot d'Arc in branch '3.2': Issue #9651: Fix a crash when ctypes.create_string_buffer(0) was passed to http://hg.python.org/cpython/rev/5df1609fbd8f New changeset d8c73a7d65f8 by Amaury Forgeot d'Arc in branch 'default': Merge from 3.2: http://hg.python.org/cpython/rev/d8c73a7d65f8 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9651 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11241] ctypes: subclassing an already subclassed ArrayType generates AttributeError
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 5e23532f694d by Amaury Forgeot d'Arc in branch '3.2': Issue #11241: subclasses of ctypes.Array can now be subclassed. http://hg.python.org/cpython/rev/5e23532f694d -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11241 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9651] ctypes crash when writing zerolength string buffer to file
Changes by Amaury Forgeot d'Arc amaur...@gmail.com: -- resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9651 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1215] documentation doesn't say that you can't handle C segfaults from python
STINNER Victor victor.stin...@haypocalc.com added the comment: def handler(signal, stackframe): print OUCH stdout.flush() _exit(1) What do you want to do on a SIGSEGV? On a real fault, you cannot rely on Python internal state, you cannot use any Python object. To handle a real SIGSEGV fault, you have to implement a signal handler using only *signal safe* functions in C. See faulthandler_fatal_error() function: https://github.com/haypo/faulthandler/blob/master/faulthandler.c#L257 The documentation for this can now point to the faulthandler module (in Python 3). For your information, faulthandler is available for Python older than 3.3 as a third party module: http://pypi.python.org/pypi/faulthandler segfault is the following C module: For tests, you can use ctypes.string_at(0) to read a word from NULL. -- faulthandler installs a signal handler for SIGSEGV, SIGFPE, SIGABRT, SIGBUS and SIGILL signals: http://docs.python.org/dev/library/faulthandler.html -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1215 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12864] 2to3 creates illegal code on import a.b inside a package
New submission from simohe sim...@besonet.ch: When the current module is in a package and imports submodules, the following lines are converted to illegal code. -import sub.subsub +from . import sub.subsub -import sub, sub.subsub, sub2 +from . import sub, sub.subsub, sub2 A valid alternative: -import sub.subsub +from .sub import subsub as _dummy -import sub, sub.subsub, sub2 +from . import sub, sub2\nfrom .sub import subsub as _dummy -- components: 2to3 (2.x to 3.0 conversion tool) messages: 143237 nosy: simohe priority: normal severity: normal status: open title: 2to3 creates illegal code on import a.b inside a package versions: Python 2.6, Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12864 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11241] ctypes: subclassing an already subclassed ArrayType generates AttributeError
Changes by Amaury Forgeot d'Arc amaur...@gmail.com: -- resolution: accepted - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11241 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12865] import SimpleHTTPServer
New submission from Andrey Men menan...@gmail.com: In russian windows seven SP1, x32, installed from 2.7.1/2.7.2 MSI installer: import SimpleHTTPServer Traceback (most recent call last): File pyshell#0, line 1, in module import SimpleHTTPServer File C:\Python\lib\SimpleHTTPServer.py, line 27, in module class SimpleHTTPRequestHandler(BaseHTTPServer.BaseHTTPRequestHandler): File C:\Python\lib\SimpleHTTPServer.py, line 204, in SimpleHTTPRequestHandler mimetypes.init() # try to read system mime.types File C:\Python\lib\mimetypes.py, line 355, in init db.read_windows_registry() File C:\Python\lib\mimetypes.py, line 259, in read_windows_registry for ctype in enum_types(mimedb): File C:\Python\lib\mimetypes.py, line 249, in enum_types ctype = ctype.encode(default_encoding) # omit in 3.x! UnicodeDecodeError: 'ascii' codec can't decode byte 0xe0 in position 0: ordinal not in range(128) -- messages: 143238 nosy: Andrey.Men priority: normal severity: normal status: open title: import SimpleHTTPServer type: resource usage versions: Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12865 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12866] Want to submit our Audioop.c patch for 24bit audio
New submission from Peder Jørgensen peder.jorgen...@gmail.com: Hi, I'm working with audio in python 2.7 and I needed Audioop to work with 24bit files, it currently only supports 8 16 and 32 bit sound files. (24bit files are very common in the audio world) My brother knows c quite well, so he managed to patch it up to support 24bit files for me, he's a bit too shy to try and get it into the standard python package him self, so I thought i'd give it a go for him :) I think the updated audioop.c would be a great add-on to python, it's 100% backwards compatible, and should work fine with python 3. I searched for hours and hours to see if someone had fixed it before, but found nothing. Not sure if this is the right place for this kind of thing, but was the best place I could find on python.org Also! The file i uploaded is not ready for release, my brother will probably want to go over it a few times and do more testing. -- files: audioop24.c messages: 143239 nosy: Peder.Jørgensen priority: normal severity: normal status: open title: Want to submit our Audioop.c patch for 24bit audio type: behavior versions: Python 2.7 Added file: http://bugs.python.org/file23075/audioop24.c ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12866 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12865] import SimpleHTTPServer
Amaury Forgeot d'Arc amaur...@gmail.com added the comment: This is a duplicate of issue9291. -- nosy: +amaury.forgeotdarc resolution: - duplicate status: open - closed superseder: - mimetypes initialization fails on Windows because of non-Latin characters in registry ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12865 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12829] pyexpat segmentation fault caused by multiple calls to Parse()
Ned Deily n...@acm.org added the comment: This is the same issue as highlighted by Issue6676. The root cause is attempting to reuse a parser instance and that is known to not work with the version of expat included with Python. Whether the test program crashes with a memory access violation or just uses uninitialized memory depends on the version of malloc in use and what protections the linker and os use. Even on Mac OS X, the test program does not segfault on earlier versions of OS X (like 10.5). And on 10.6 and 10.7 if you build python with pymalloc it usually does not segfault. But that doesn't mean it is working properly. At a minimum, the single use restriction should be documented; if anyone is interested, they could look into adding any more recent fixes to expat and plugging remaining reuse holes. -- resolution: - duplicate status: open - closed superseder: - expat parser throws Memory Error when parsing multiple files ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12829 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6676] expat parser throws Memory Error when parsing multiple files
Ned Deily n...@acm.org added the comment: I agree that, at a minimum, the documentation should be updated to include a warning about not reusing a parser instance. Whether it's worth trying to plug all the holes in the expat library is another issue (see, for instance, issue12829). David, would you be willing to propose a wording for a documentation change? -- nosy: +ned.deily versions: +Python 3.2, Python 3.3 -Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6676 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6676] expat parser throws Memory Error when parsing multiple files
Ned Deily n...@acm.org added the comment: Also, note issue1208730 proposes a feature to expose a binding for XML_ParserReset and has the start of a patch. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6676 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1215] documentation doesn't say that you can't handle C segfaults from python
Martin Pool m...@sourcefrog.net added the comment: On 31 August 2011 07:56, STINNER Victor rep...@bugs.python.org wrote: STINNER Victor victor.stin...@haypocalc.com added the comment: def handler(signal, stackframe): print OUCH stdout.flush() _exit(1) What do you want to do on a SIGSEGV? On a real fault, you cannot rely on Python internal state, you cannot use any Python object. To handle a real SIGSEGV fault, you have to implement a signal handler using only *signal safe* functions in C. Well, strictly speaking, it is very hard or impossible to write C code that's guaranteed to be safe after an unexpected segv too; who knows what might have caused it. The odds are probably better that it will work in in C than in Python. At any rate I think it's agreed that the original code is not supported and it's just the docs that need to change. So what do you think of http://bugs.python.org/file22989/20110822-1525-signal-doc.diff ? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1215 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12855] linebreak sequences should be better documented
Matthew Boehm boehm.matt...@gmail.com added the comment: I've attached a patch for 2.7 and will attach one for 3.2 in a minute. I built the docs for both 2.7 and 3.2 and verified that there were no warnings and that the resulting web pages looked okay. Things to consider: * Placement of unicode.splitlines() method: I placed it next to str.splitlines. I didn't want to place it with the unicode methods further down because docs say The following methods are present only on unicode objects * The docs for codecs.readlines() already mentions Line-endings are implemented using the codec’s decoder method and are included in the list entries if keepends is true. * Feel free to make any wording/style suggestions. -- Added file: http://bugs.python.org/file23076/linebreakdoc.v2.py27.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12855 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12855] linebreak sequences should be better documented
Changes by Matthew Boehm boehm.matt...@gmail.com: Added file: http://bugs.python.org/file23077/linebreakdoc.v2.py32.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12855 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12409] Moving Documenting Python to Devguide
Changes by Adam Woodbeck adam.woodb...@gmail.com: -- nosy: +adam.woodbeck ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12409 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11176] give more meaningful argument names in argparse documentation
Changes by Adam Woodbeck adam.woodb...@gmail.com: -- nosy: +adam.woodbeck ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11176 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11241] ctypes: subclassing an already subclassed ArrayType generates AttributeError
Meador Inge mead...@gmail.com added the comment: Thanks a lot for committing this for me Amaury. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11241 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12867] linecache.getline() Returning Error
New submission from Jordan Meyer jordanmeyer1...@gmail.com:
In trying to use the linecache.getline() function to extra data from a
plain-text database format that I'm building. Every time I make a call to it
(even from the interpreter directly) I get an error like the one below. I
believe the problem lies in the linecache module itself.
Traceback (most recent call last):
File
/Users/jordanmeyer/Documents/Python/eFlashcard/alpha/0.1a2/eFlashcard_0.1a2.py,
line 59, in module
eFlashcard_main()
File
/Users/jordanmeyer/Documents/Python/eFlashcard/alpha/0.1a2/eFlashcard_0.1a2.py,
line 17, in eFlashcard_main
eFlashcard_build()
File
/Users/jordanmeyer/Documents/Python/eFlashcard/alpha/0.1a2/eFlashcard_0.1a2.py,
line 31, in eFlashcard_build
while str(linecache.getline(lib_file, lib_index, module_globals=None)) !=
'':
File
/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/linecache.py,
line 15, in getline
lines = getlines(filename, module_globals)
File
/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/linecache.py,
line 41, in getlines
return updatecache(filename, module_globals)
File
/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/linecache.py,
line 76, in updatecache
if not filename or (filename.startswith('') and filename.endswith('')):
AttributeError: '_io.TextIOWrapper' object has no attribute 'startswith'
--
components: Library (Lib)
messages: 143247
nosy: Jordan.Meyer
priority: normal
severity: normal
status: open
title: linecache.getline() Returning Error
type: crash
versions: Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12867
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12857] Expose called function on frame object
Eric Snow ericsnowcurren...@gmail.com added the comment: Thanks for the review, Nick. I'll be uploading a new patch in a couple hours with your recommended fixes. Regarding the comments on python-ideas, would it be better to use a weakref proxy around the function, to help with the reference cycles? That's what I was doing with my closure-based solution. I didn't do it here just to see what would happen and I didn't see any problems in my very limited testing (basically just 'make test'). I don't mind using weakrefs and, if it matters, I could pre-allocate the weakref proxy in PyFunction_New to save a little overhead at each call. For the moment I left in the code to limit f_func to only functions. I'll respond to that on python-ideas. Finally, how does this patch relate to the ABI? I'm not too familiar with it (read through PEP 384) and want to make sure I'm okay here. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12857 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12857] Expose called function on frame object
Eric Snow ericsnowcurren...@gmail.com added the comment: On second thought, I probably won't be able to get an updated patch tonight. I need to mull over the PyEval_EvalFunction implementation and the interaction with fast_function. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12857 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
