[issue12867] linecache.getline() Returning Error
Ned Deily n...@acm.org added the comment: The linecache module functions take a filename string as an argument, not a file object. Try: linecache.getlines(/path/to/filename, lineno) http://docs.python.org/py3k/library/linecache.html -- nosy: +ned.deily resolution: - works for me stage: - committed/rejected status: open - closed type: crash - behavior ___ 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
[issue12868] test_faulthandler.test_stack_overflow() failed on OpenBSD
New submission from Remi Pointel pyt...@xiri.fr: Hello, the test_stack_overflow failed on OpenBSD. Don't hesitate if you need more information. Details: $ ./python Lib/test/test_faulthandler.py test_disable (__main__.FaultHandlerTests) ... ok test_dump_traceback (__main__.FaultHandlerTests) ... ok test_dump_traceback_file (__main__.FaultHandlerTests) ... ok test_dump_traceback_threads (__main__.FaultHandlerTests) ... ok test_dump_traceback_threads_file (__main__.FaultHandlerTests) ... ok test_dump_tracebacks_later (__main__.FaultHandlerTests) ... ok test_dump_tracebacks_later_cancel (__main__.FaultHandlerTests) ... ok test_dump_tracebacks_later_file (__main__.FaultHandlerTests) ... ok test_dump_tracebacks_later_repeat (__main__.FaultHandlerTests) ... ok test_dump_tracebacks_later_twice (__main__.FaultHandlerTests) ... ok test_enable_file (__main__.FaultHandlerTests) ... ok test_enable_single_thread (__main__.FaultHandlerTests) ... ok test_fatal_error (__main__.FaultHandlerTests) ... ok test_gil_released (__main__.FaultHandlerTests) ... ok test_is_enabled (__main__.FaultHandlerTests) ... ok test_read_null (__main__.FaultHandlerTests) ... ok test_register (__main__.FaultHandlerTests) ... ok test_register_chain (__main__.FaultHandlerTests) ... ok test_register_file (__main__.FaultHandlerTests) ... ok test_register_threads (__main__.FaultHandlerTests) ... ok test_sigabrt (__main__.FaultHandlerTests) ... ok test_sigbus (__main__.FaultHandlerTests) ... ok test_sigfpe (__main__.FaultHandlerTests) ... ok test_sigill (__main__.FaultHandlerTests) ... ok test_sigsegv (__main__.FaultHandlerTests) ... ok test_stack_overflow (__main__.FaultHandlerTests) ... FAIL test_unregister (__main__.FaultHandlerTests) ... ok == FAIL: test_stack_overflow (__main__.FaultHandlerTests) -- Traceback (most recent call last): File Lib/test/test_faulthandler.py, line 187, in test_stack_overflow other_regex='unable to raise a stack overflow') File Lib/test/test_faulthandler.py, line 105, in check_fatal_error self.assertRegex(output, regex) AssertionError: Regex didn't match: '^Fatal Python error: (?:Segmentation fault|Bus error)\n\nCurrent\\ thread\\ XXX:\n File string, line 3 in module$|unable to raise a stack overflow' not found in '' -- Ran 27 tests in 16.938s FAILED (failures=1) Traceback (most recent call last): File Lib/test/test_faulthandler.py, line 551, in module test_main() File Lib/test/test_faulthandler.py, line 548, in test_main support.run_unittest(FaultHandlerTests) File /home/remi/dev/cpython_test/Lib/test/support.py, line 1328, in run_unittest _run_suite(suite) File /home/remi/dev/cpython_test/Lib/test/support.py, line 1303, in _run_suite raise TestFailed(err) test.support.TestFailed: Traceback (most recent call last): File Lib/test/test_faulthandler.py, line 187, in test_stack_overflow other_regex='unable to raise a stack overflow') File Lib/test/test_faulthandler.py, line 105, in check_fatal_error self.assertRegex(output, regex) AssertionError: Regex didn't match: '^Fatal Python error: (?:Segmentation fault|Bus error)\n\nCurrent\\ thread\\ XXX:\n File string, line 3 in module$|unable to raise a stack overflow' not found in '' Thanks a lot, Remi. -- messages: 143251 nosy: rpointel priority: normal severity: normal status: open title: test_faulthandler.test_stack_overflow() failed on OpenBSD versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12868] test_faulthandler.test_stack_overflow() failed on OpenBSD
Remi Pointel pyt...@xiri.fr added the comment: Info: I read issue 12469 but I prefered to create new issue. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12868 ___ ___ 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 Andrew Svetlov andrew.svet...@gmail.com: -- nosy: +asvetlov ___ 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
[issue1215] documentation doesn't say that you can't handle C segfaults from python
STINNER Victor victor.stin...@haypocalc.com added the comment: Le mercredi 31 août 2011 02:52:01, vous avez écrit : 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 It is possible if you only use signal safe functions. I think that no Python function is signal safe :-) -- ___ 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
[issue12765] test_packaging failure under Snow Leopard
Éric Araujo mer...@netwok.org added the comment: Still failing. -- resolution: fixed - stage: commit review - needs patch status: pending - open ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12765 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9998] ctypes find_library should search LD_LIBRARY_PATH on linux
Vinay Sajip vinay_sa...@yahoo.co.uk added the comment: There is a problem in this area of the code, not especially with the patch but with how gcc works (or doesn't). To illustrate: --- Version info --- vinay@eta-hardy:/tmp$ uname -a Linux eta-hardy 2.6.24-29-generic #1 SMP Wed Aug 10 16:34:32 UTC 2011 i686 GNU/Linux vinay@eta-hardy:/tmp$ gcc --version gcc (GCC) 4.2.4 (Ubuntu 4.2.4-1ubuntu4) Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. --- Create an empty file: --- vinay@eta-hardy:/tmp$ touch dummy.c --- Compile a shared library from it: --- vinay@eta-hardy:/tmp$ gcc -shared -o libdummy.so dummy.c --- Invoke gcc with patched command line: --- vinay@eta-hardy:/tmp$ gcc -L /tmp -Wl,t -o /dev/null -ldummy /usr/bin/ld: t: No such file: No such file or directory collect2: ld returned 1 exit status --- It's not patch related, here's what happens with the unpatched line --- vinay@eta-hardy:/tmp$ gcc -Wl,t -o /dev/null -ldummy /usr/bin/ld: t: No such file: No such file or directory collect2: ld returned 1 exit status --- Calling ld directly works as expected. With no search path: --- vinay@eta-hardy:/tmp$ ld -t -o /dev/null -ldummy ld: mode elf_i386 ld: cannot find -ldummy --- With the search path supplied: --- vinay@eta-hardy:/tmp$ ld -t -L /tmp -o /dev/null -ldummy ld: mode elf_i386 -ldummy (/tmp/libdummy.so) ld: warning: cannot find entry symbol _start; not setting start address vinay@eta-hardy:/tmp$ So, ISTM that the find_library code needs changing to use ld, else it will not work on all platforms. -- nosy: +vinay.sajip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9998 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12869] PyOS_StdioReadline is printing the prompt on stderr
New submission from Albert Zeyer alb...@googlemail.com: PyOS_StdioReadline from Parser/myreadline.c is printing the prompt on stderr. I think it should print it on the given parameter sys_stdout. Other readline implementations (like from the readline module) also behave this way. Even if it really is supposed to write on stderr, it should use the `sys.stderr` and not the system stderr. -- messages: 143256 nosy: Albert.Zeyer priority: normal severity: normal status: open title: PyOS_StdioReadline is printing the prompt on stderr versions: Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12869 ___ ___ 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: Even more problematic: The readline lib itself is absolutely not designed in a way to be used from multi threads at once. -- ___ 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
[issue11435] Links to source code should now point to hg repo
Éric Araujo mer...@netwok.org added the comment: After getting Georg’s greenlight on python-dev, I have adapted the source reST role for 2.7 and updated all links. -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11435 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10086] test_sysconfig failure when prefix matches /site
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 1e01543c3d0a by Éric Araujo in branch '3.2': Fix test_sysconfig when run from a Python installed under /site (#10086). http://hg.python.org/cpython/rev/1e01543c3d0a New changeset 0968acf0e6db by Éric Araujo in branch 'default': Merge fix for #10086 from 3.2 http://hg.python.org/cpython/rev/0968acf0e6db -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10086 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12765] test_packaging failure under Snow Leopard
Bill Janssen bill.jans...@gmail.com added the comment: I'm on vacation right now and can't get to it... Bill On Thu, Aug 18, 2011 at 12:22 PM, Antoine Pitrou rep...@bugs.python.org wrote: Antoine Pitrou pit...@free.fr added the comment: Bill is the owner of that buildbot. -- nosy: +janssen ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12765 ___ -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12765 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12785] list_distinfo_file is wrong
Éric Araujo mer...@netwok.org added the comment: I've tested the attached patch against 3.3 on Windows XP, and it seems to fix the test_database failures. Thanks. I've uploaded the exact diff of what I tested with. Your diff matches the one I get after updating my clone, we’re good. I tested both with and without the change you suggested in msg142773 - the tests pass in both cases. I have to have another look at the code to make sure this makes sense and take the right approach. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12785 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10086] test_sysconfig failure when prefix matches /site
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 4dcbae65df3f by Éric Araujo in branch '2.7': Fix test_sysconfig when run from a Python installed under /site (#10086). http://hg.python.org/cpython/rev/4dcbae65df3f -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10086 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10086] test_sysconfig failure when prefix matches /site
Éric Araujo mer...@netwok.org added the comment: I think I can commit this fix for a minor issue in a test without worrying about regressions. I manually tested and it’s fixed. Done! Thanks again. -- assignee: tarek - eric.araujo resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10086 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12386] packaging fails in install_distinfo when writing RESOURCES
Éric Araujo mer...@netwok.org added the comment: I only meant that when writing data resources, one might reasonably use 'wb', but when writing scripts, which are text, 'w' is more appropriate. I don’t see why. All text is bytes, so we can do all I/O in bytes when writing resources and avoid special-casing. BTW, IIRC I have fixed it in the pythonv branch. https://bitbucket.org/vinay.sajip/pythonv A link to a specific changeset or file would be great. [trevor] i see the same behavior - the error occurs leaving an empty RESOURCES file Do you see that when running a test, a command or some other code? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12386 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12386] packaging fails in install_distinfo when writing RESOURCES
trevor tre...@well.com added the comment: [eric.araujo] Do you see that when running a test, a command or some other code? when attempting to install a self-created package. tools from 3.3a ~72060:1696e2789d91 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12386 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12868] test_faulthandler.test_stack_overflow() failed on OpenBSD
Charles-François Natali neolo...@free.fr added the comment: OpenBSD's threads are userland threads, and sigaltstack() doesn't work when the program is built with -pthread: http://marc.info/?l=openbsd-bugsm=114323355014696w=2 Note that POSIX warns about this: http://www.opengroup.org/onlinepubs/95399/functions/sigaltstack.html Use of this function by library threads that are not bound to kernel-scheduled entities results in undefined behavior. I think we should skip this test on OpenBSD when Python is compiled with threads support. Out of curiosity, could you try this: $ ./python -c import faulthandler; faulthandler.enable(); faulthandler._stack_overflow(); echo $? And if you're motivated, you could try it again after having built python with './configure --without-threads'. -- components: +Tests nosy: +haypo, neologix stage: - needs patch type: - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12870] Regex object should have introspection methods
New submission from Matt Chaput m...@whoosh.ca: Several times in the recent past I've wished for the following methods on the regular expression object. These would allow me to speed up search and parsing code, by limiting the number of regex matches I need to try. literal_prefix(): Returns any literal string at the start of the pattern (before any special parts). E.g., for the pattern ab(c|d)ef the method would return ab. For the pattern abc|def the method would return . When matching a regex against keys in a btree, this would let me limit the search to just the range of keys with the prefix. first_chars(): Returns a string/list/set/whatever of the possible first characters that could appear at the start of a matching string. E.g. for the pattern ab(c|d)ef the method would return a. For the pattern [a-d]ef the method would return abcd. When parsing a string with regexes, this would let me only have to test the regexes that could match at the current character. As long as you're making a new regex package, I thought I'd put in a request for these :) -- components: Regular Expressions messages: 143266 nosy: mattchaput priority: normal severity: normal status: open title: Regex object should have introspection methods type: feature request versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12870 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12870] Regex object should have introspection methods
Ezio Melotti ezio.melo...@gmail.com added the comment: These additions sounds more useful as an external tool than regex functions/methods. There are already a few tools able to explain what a regex matches. The use cases you proposed are too specific to deserve new methods, and using them programmatically sounds like premature optimization IMHO. -- nosy: +ezio.melotti, mrabarnett ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12870 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12868] test_faulthandler.test_stack_overflow() failed on OpenBSD
Remi Pointel pyt...@xiri.fr added the comment: Hi, results: Out of curiosity, could you try this: $ ./python -c import faulthandler; faulthandler.enable(); faulthandler._stack_overflow(); echo $? $ ./python -c import faulthandler; faulthandler.enable(); faulthandler._stack_overflow(); echo $? zsh: illegal hardware instruction (core dumped) ./python -c 132 And if you're motivated, you could try it again after having built python with './configure --without-threads'. It does not build completely, I have a problem if I add --without-threads: $ make [...] ./Modules/posixmodule.c:4582: undefined reference to `sched_get_priority_min' libpython3.3m.a(posixmodule.o)(.text+0x430b): In function `posix_sched_get_priority_max': ./Modules/posixmodule.c:4565: undefined reference to `sched_get_priority_max' collect2: ld returned 1 exit status *** Error code 1 It seems that it needs -pthread even if I precise --without-threads. Must I open a new ticket for this problem? Thanks for your help, Remi. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12871] Disable sched_get_priority_min/max if Python is compiled without threads
New submission from STINNER Victor victor.stin...@haypocalc.com: If Pyton is configured without thread support (--without-threads), the compilation fails on OpenBSD : $ make [...] ./Modules/posixmodule.c:4582: undefined reference to `sched_get_priority_min' libpython3.3m.a(posixmodule.o)(.text+0x430b): In function `posix_sched_get_priority_max': ./Modules/posixmodule.c:4565: undefined reference to `sched_get_priority_max' collect2: ld returned 1 exit status *** Error code 1 I didn't try on Linux, but I suppose that the issue is not specific to OpenBSD. -- components: Extension Modules messages: 143270 nosy: haypo, rpointel priority: normal severity: normal status: open title: Disable sched_get_priority_min/max if Python is compiled without threads versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12871 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12868] test_faulthandler.test_stack_overflow() failed on OpenBSD
STINNER Victor victor.stin...@haypocalc.com added the comment: I have a problem if I add --without-threads Yeah, it's a recent regression: I opened the issue #12871. I don't think that it's specific to OpenBSD. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12868] test_faulthandler.test_stack_overflow() failed on OpenBSD
Remi Pointel pyt...@xiri.fr added the comment: Yeah, it's a recent regression: I opened the issue #12871. I don't think that it's specific to OpenBSD. Thanks. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12636] IDLE ignores -*- coding -*- with -r option
ledave123 ledave...@yahoo.fr added the comment: Here is the patch: diff -r e8da570d29a8 Lib/idlelib/PyShell.py --- a/Lib/idlelib/PyShell.pyWed Jul 27 21:28:23 2011 +0200 +++ b/Lib/idlelib/PyShell.pyWed Aug 31 20:16:38 2011 +0200 @@ -582,7 +582,9 @@ def execfile(self, filename, source=None): Execute an existing file if source is None: -source = open(filename, r).read() +import tokenize +with tokenize.open(filename) as filein: +source = filein.read() try: code = compile(source, filename, exec) except (OverflowError, SyntaxError): Sorry for taking such a long time, I was on holidays. -- resolution: - works for me ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6721] Locks in python standard library should be sanitized on fork
Nir Aides n...@winpdb.org added the comment: For the record, turns out there was a bit of misunderstanding. I used the term deprecate above to mean warn users (through documentation) that they should not use (a feature) and not in its Python-dev sense of remove (a feature) after a period of warning. I do not think the possibility to mix threading and multiprocessing together should be somehow forcibly disabled. Anyway, since my view does not seem to resonate with core developers I I'll give it a rest for now. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6721 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12793] allow filters in os.walk
Jacek Pliszka jacek.plis...@gmail.com added the comment:
Looks like the proper way to do it is described in the manual:
http://docs.python.org/dev/library/os.html#os.walk
for root, dirs, files in os.walk('python/Lib/email'):
if 'CVS' in dirs:
dirs.remove('CVS') # don't visit CVS directories
.
I checked that it is covered by unit tests in /test_os.py so it is safe to use
and bug can blo closed as invalid.
--
resolution: - invalid
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12793
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12868] test_faulthandler.test_stack_overflow() failed on OpenBSD
Changes by Charles-François Natali neolo...@free.fr: -- keywords: +patch Added file: http://bugs.python.org/file23078/openbsd_sigaltstack.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12871] Disable sched_get_priority_min/max if Python is compiled without threads
Nadeem Vawda nadeem.va...@gmail.com added the comment: I haven't been able to reproduce this on Linux (2.6.38; Ubuntu 11.04). Some searching around seems to suggest that OpenBSD doesn't provide those functions (or didn't until recently). Modules/posixmodule.c and configure.in seem to assume that these functions are available if sched.h exists. Adding an explicit check for them should solve the problem. -- nosy: +nadeem.vawda ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12871 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12871] Disable sched_get_priority_min/max if Python is compiled without threads
Charles-François Natali neolo...@free.fr added the comment:
There's no reason to disable sched_get_priority_(min|max) when Python is built
without threads: those libraries control the scheduling policy, and should be
available even without pthread.
However, it's really likely that pthread has its own implementation (especially
since OpenBSD's threads are implemented in user-space), and it seems that
OpenBSD sched_get_priority() is only defined for threads:
http://www.openbsd.org/cgi-bin/man.cgi?query=sched_get_priority_maxapropos=0sektion=0manpath=OpenBSD+Currentarch=i386format=html
This implementation does not support process scheduling.
For example, the following snippet builds correctly on Linux:
#include sched.h
int main(int argc, char *argv[])
{
int (*fp)(int) = sched_get_priority_max;
return 0;
}
So this should be skipped only on OpenBSD, or we should add some checks to the
configure script.
--
nosy: +neologix
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12871
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12793] allow filters in os.walk
Changes by Raymond Hettinger raymond.hettin...@gmail.com: -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12793 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12868] test_faulthandler.test_stack_overflow() failed on OpenBSD
Charles-François Natali neolo...@free.fr added the comment: It does not build completely, I have a problem if I add --without-threads: Until this gets fixed, if you want to do a quick test, you could just remove the calls to sched_get_priority_(min|max): diff -r 0968acf0e6db Modules/posixmodule.c --- a/Modules/posixmodule.c Wed Aug 31 16:52:12 2011 +0200 +++ b/Modules/posixmodule.c Wed Aug 31 22:51:13 2011 +0200 @@ -4562,7 +4562,6 @@ if (!PyArg_ParseTuple(args, i:sched_get_priority_max, policy)) return NULL; -max = sched_get_priority_max(policy); if (max 0) return posix_error(); return PyLong_FromLong(max); @@ -4579,7 +4578,6 @@ if (!PyArg_ParseTuple(args, i:sched_get_priority_min, policy)) return NULL; -min = sched_get_priority_min(policy); if (min 0) return posix_error(); return PyLong_FromLong(min); That should allow you to rebuild with 'without-threads'. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6721] Locks in python standard library should be sanitized on fork
Charles-François Natali neolo...@free.fr added the comment: Anyway, since my view does not seem to resonate with core developers I I'll give it a rest for now. Well, the problem is that many views have been expressed in this thread, which doesn't help getting a clear picture of what's needed to make progress on this issue. AFAIC, I think the following seems reasonable: 1) add an atfork module which provides a generic and pthread_atfork-like mechanism to setup handlers that must be called after fork (right now several modules use their own ad-hoc mechanism) 2) for multiprocessing, call exec() after fork() (issue #8713) 3) for buffered file objects locks, use the approach similar to the patch I posted (reinit locks in the child process right after fork()) Does that sound reasonable? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6721 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12472] Build failure on IRIX
Charles-François Natali neolo...@free.fr added the comment: I'm closing, since IRIX header files seem terminally broken, and we can't do much about it. Furthermore, I'm 99% sure IRIX isn't officially supported anymore. -- resolution: - wont fix stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12472 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12872] --with-tsc crashes on ppc64
New submission from Dave Malcolm dmalc...@redhat.com:
On 64-bit PPC builds configured --with-tsc, Python segfaults within the first
function call in the bytecode interpreter.
Upon investigation this is due to this code in Python/ceval.c:
32 typedef unsigned long long uint64;
33
34 /* PowerPC support.
35 __ppc__ appears to be the preprocessor definition to detect on OS
X, whereas
36 __powerpc__ appears to be the correct one for Linux with GCC
37 */
38 #if defined(__ppc__) || defined (__powerpc__)
39
40 #define READ_TIMESTAMP(var) ppc_getcounter(var)
41
42 static void
43 ppc_getcounter(uint64 *v)
44 {
45 register unsigned long tbu, tb, tbu2;
46
47loop:
48 asm volatile (mftbu %0 : =r (tbu) );
49 asm volatile (mftb %0 : =r (tb) );
50 asm volatile (mftbu %0 : =r (tbu2));
51 if (__builtin_expect(tbu != tbu2, 0)) goto loop;
52
53 /* The slightly peculiar way of writing the next lines is
54 compiled better by GCC than any other way I tried. */
55 ((long*)(v))[0] = tbu;
56 /*((long*)(v))[1] = tb; */ /* this is the bug */
57 }
58
59 #elif defined(__i386__)
(gdb) p sizeof(long)
$44 = 8
(gdb) p sizeof(uint64)
$45 = 8
Looks like lines 55 and 56 are erroneously assuming that a long is 4 bytes on
this arch: line 56 above is trashing the next value beyond the timer value,
which is on the machine's stack, corrupting local variables within
PyEval_EvalFrameEx.
The code has been this way since ppc_getcounter was added, in:
http://hg.python.org/cpython/rev/f455bbe7ea7e
I may have broken this in:
http://hg.python.org/cpython/rev/419ca089d365/
which was for:
http://bugs.python.org/issue10655
by (perhaps) generalizing support from ppc to (ppc and ppc64) (not sure about
this).
I'm attaching a patch which splits the ppc tsc support into 32-bit and 64-bit
parts, and which also removes an aliasing violation on 32-bit ppc.
(I'm tracking this downstream in Fedora's bug tracker as
https://bugzilla.redhat.com/show_bug.cgi?id=698726 )
--
components: Interpreter Core
files: python-2.7.2-tsc-on-ppc.patch
keywords: patch
messages: 143281
nosy: dmalcolm
priority: normal
severity: normal
stage: patch review
status: open
title: --with-tsc crashes on ppc64
type: crash
versions: Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4
Added file: http://bugs.python.org/file23079/python-2.7.2-tsc-on-ppc.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12872
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12386] packaging fails in install_distinfo when writing RESOURCES
Vinay Sajip vinay_sa...@yahoo.co.uk added the comment: I don’t see why. All text is bytes, so we can do all I/O in bytes when writing resources and avoid special-casing. I was only commenting on how the bug might have come about. A link to a specific changeset or file would be great. https://bitbucket.org/vinay.sajip/pythonv/changeset/3e3a07a94f69#chg-Lib/packaging/command/install_distinfo.py -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12386 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12873] 2to3 incorrectly handles multi-line imports from __future__
New submission from Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com: $ cat test1.py from __future__ import (absolute_import, division, print_function, unicode_literals) print(1, 2) $ cat test2.py from __future__ import (absolute_import, division, print_function, unicode_literals) print(1, 2) $ python2.7 -c 'import test1' 1 2 $ python2.7 -c 'import test2' 1 2 $ 2to3 test1.py test2.py RefactoringTool: Skipping implicit fixer: buffer RefactoringTool: Skipping implicit fixer: idioms RefactoringTool: Skipping implicit fixer: set_literal RefactoringTool: Skipping implicit fixer: ws_comma RefactoringTool: Refactored test1.py --- test1.py(original) +++ test1.py(refactored) @@ -1,4 +1,4 @@ from __future__ import (absolute_import, division, print_function, unicode_literals) -print(1, 2) +print((1, 2)) RefactoringTool: Files that need to be modified: RefactoringTool: test1.py -- components: 2to3 (2.x to 3.0 conversion tool) messages: 143283 nosy: Arfrever, benjamin.peterson priority: normal severity: normal status: open title: 2to3 incorrectly handles multi-line imports from __future__ versions: Python 2.7, Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12873 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12874] Rearrange descriptions of builtin types
New submission from Nick Coghlan ncogh...@gmail.com: Section 4 of the Standard Library reference currently includes the two following sections (amongst others): 4.6. Sequence Types — str, bytes, bytearray, list, tuple, range 4.9. memoryview type This is crazy - memoryview, a fairly niche type, gets its own second tier section on the main table of contents, while str, one of the most important types in Python, is tucked away under the generic Sequence Type heading? I propose that these sections be rearranged as: 4.6 Sequence Types - list, tuple, range 4.7 Text Types - str 4.8 Binary Data Types - bytes, bytearray, memoryview The Set Types and Mapping Types sections would slide down to sections 4.9 and 4.10 to make room for the two new sections. -- assignee: docs@python components: Documentation messages: 143284 nosy: docs@python, ncoghlan priority: normal severity: normal status: open title: Rearrange descriptions of builtin types versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12874 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12874] Rearrange descriptions of builtin types in the Library reference
Changes by Nick Coghlan ncogh...@gmail.com: -- title: Rearrange descriptions of builtin types - Rearrange descriptions of builtin types in the Library reference ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12874 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12874] Rearrange descriptions of builtin types in the Library reference
Changes by Nick Coghlan ncogh...@gmail.com: -- stage: - needs patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12874 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12874] Rearrange descriptions of builtin types in the Library reference
Nick Coghlan ncogh...@gmail.com added the comment: Better titles for the proposed new sections: 4.7 Text Data - str 4.8 Binary Data - bytes, bytearray, memoryview -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12874 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12874] Rearrange descriptions of builtin types in the Library reference
Guido van Rossum gu...@python.org added the comment: I agree on the subdivision, but I think they should still be grouped together somehow, since these all really *do* share some interfaces: __getitem__ (with slicing), __iter__, __len__, at least; arguably __contains__; probably some others (see collections/abc.py). -- nosy: +gvanrossum ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12874 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12874] Rearrange descriptions of builtin types in the Library reference
Nick Coghlan ncogh...@gmail.com added the comment: Putting the new sections on tier 2 makes a big difference in discoverability, since that's the lowest level the main ToC page shows. Perhaps just including the phrase Sequence Type in the new section titles would provide enough logical grouping? Something like: 4.6 Sequence Types - list, tuple, range 4.7 Text Sequence Type - str 4.8 Binary Data Sequence Types - bytes, bytearray, memoryview -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12874 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12874] Rearrange descriptions of builtin types in the Library reference
Guido van Rossum gu...@python.org added the comment: That sounds fine. Or list most of them at tier 2: 4.6 Sequence Types - list, tuple, range, str, bytes and friends 4.6.1 Sequence containers - list, tuple, range 4.6.2 Text Sequence Type - str 4.6.3 Binary Data Sequence Types - bytes, bytearray, memoryview Although including range() here feels a bit odd? (It's a much more specialized type -- actually the same can be said for memoryview.) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12874 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12472] Build failure on IRIX
kais58 kai...@sucs.org added the comment: Apologies for not getting back to you sooner, I discovered some more pressing issues with the machine regarding gcc, I'll try and fix/hack it together as I have found some possible fixes for the headers. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12472 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12874] Rearrange descriptions of builtin types in the Library reference
Nick Coghlan ncogh...@gmail.com added the comment: 'Sequence Types - list, tuple, str, bytes, etc' *might* work, but I think part of the problem is that str's brevity is actually a downside in this case. I know I missed it when I was scanning the ToC earlier (I wanted to check if the internal Unicode repr for narrow builds was documented at all - it doesn't appear to be). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12874 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12874] Rearrange descriptions of builtin types in the Library reference
Guido van Rossum gu...@python.org added the comment: How about list, tuple, text and binary strings ? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12874 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12874] Rearrange descriptions of builtin types in the Library reference
Ezio Melotti ezio.melo...@gmail.com added the comment: I believe this is a duplicate of #4966. -- nosy: +ezio.melotti resolution: - duplicate stage: needs patch - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12874 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4966] Improving Lib Doc Sequence Types Section
Nick Coghlan ncogh...@gmail.com added the comment: Bringing a suggestion over from #12874, I think it may be worth splitting the current Sequence Types section into 3 pieces that all appear in the top level table of contents for the library reference: 4.6 Sequence Types - list, tuple, range 4.7 Text Sequence Type - str 4.8 Binary Data Sequence Types - bytes, bytearray, memoryview -- nosy: +ncoghlan ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4966 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12720] Expose linux extended filesystem attributes
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 4eb0b1819bda by Benjamin Peterson in branch 'default': expose linux extended file system attributes (closes #12720) http://hg.python.org/cpython/rev/4eb0b1819bda -- nosy: +python-dev resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12720 ___ ___ 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
David H. Gutteridge dhgutteri...@sympatico.ca added the comment: Ned: My proposed wording is: Note that only one document can be parsed by a given instance; it is not possible to reuse an instance to parse multiple files. To provide more detail, one could also add something like: The isfinal argument of the Parse() method is intended to allow the parsing of a single file in fragments, not the submission of multiple files. -- ___ 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
[issue6560] socket sendmsg(), recvmsg() methods
Changes by Brett Cannon br...@python.org: -- nosy: +brett.cannon resolution: fixed - stage: committed/rejected - needs patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6560 ___ ___ 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()
David H. Gutteridge dhgutteri...@sympatico.ca added the comment: Okay. I'd seen the earlier issue, but had submitted this separately because I wasn't sure if it was a security-related bug, whereas the older issue didn't mention anything of the sort. (In retrospect, I could've just added to it...) -- ___ 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
[issue12494] subprocess: check_output() doesn't close pipes on error
Ross Lagerwall rosslagerw...@gmail.com added the comment: The second patch looks good. Tests? I think it would be better to kill the process than to let it carry on. But, it *probably* shouldn't be applied to 2.7 3.2 given that it is a behaviour change. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12494 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6069] casting error from ctypes array to structure
Meador Inge mead...@gmail.com added the comment:
Hmmm ... Assuming a native VC++ compiler on an x86 machine running Windows,
then it doesn't make sense to validate these test cases in such an environment.
All the tests are all big-endian.
'ctypes' can't be expected to behave the same as the native compiler that
compiled the Python interpreter for structures of non-native endianities
produced by 'ctypes'. That doesn't make sense. The best we can do is document
how 'ctypes' does handle non-native endianites on various platforms.
FWIW, I did try the first set of tests (http://bugs.python.org/msg88145) with
GCC for a 32-bit MIPS ELF target using the following test case:
#include stdio.h
struct T {
unsigned int x : 31;
unsigned int y : 32;
};
struct S {
unsigned long long x : 31;
unsigned long long y : 32;
};
int main (int argc, char **argv)
{
unsigned char buf[8] = {0x55, 0x55, 0x55, 0x55, 0x55, 0x55, 0x55, 0x55};
struct T *t = (struct T*)buf;
struct S *s = (struct S*)buf;
printf (%X, %X\n, t-x, t-y);
printf (%X, %X\n, s-x, s-y);
}
The test output:
Data0 is 0x2AAA, Data1 is 0x for uint
Data0 is 0x2AAA, Data1 is 0x for ulonglong
is correct with respect to that environment.
The difference in the first case (uint) and the second case (ulonglong) is that
the first is placed into two 4-byte unsigned integer units where as the second
is placed into one 8-byte unsigned long long unit.
I am slightly confused how issue12528 is going to address this, when there
seems to be no bug; only what seems to be a test case problem. I think we
should close this issue out.
Another issue should be opened to enhance the documentation, though. We should
document exactly how 'ctypes' does the structure layout for different
endianities on different platforms. Something similar to how VC++ documents
this ( http://msdn.microsoft.com/en-us/library/ewwyfdbe(v=vs.71).aspx ).
--
assignee: theller -
nosy: +meadori -theller
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6069
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12837] Patch for issue #12810 removed a valid check on socket ancillary data
Brett Cannon br...@python.org added the comment: This is now generating a compiler warning under OS X because the older POSIX standard is followed where socklen_t can be unsigned. Attached is a patch to cast msg_controllen to a size big enough to hold either signed 2**31-1 or unsigned 2**32-1 (i.e., long long) to silence the compiler warning. I would check the patch in myself but test_socket is failing under OS X right now so I can't verify I didn't do something extremely stupid with the cast somehow. -- nosy: +brett.cannon resolution: fixed - stage: committed/rejected - commit review status: closed - open Added file: http://bugs.python.org/file23080/socket_compiler_warning.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12837 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12875] backport re.compile flags default value documentation
New submission from Eli Bendersky eli...@gmail.com: In the 2.7 docs, re.compile has this signature: re.compile(pattern[, flags]) From here it isn't clear what the default value of 'flags' is, to be able to write code like this: re.compile(pattern, re.I if options['ignore_case'] else WHAT??) Of course, looking at the source shows immediately that the default flag value is 0 (which is kind-of implied by the flags being a bit-OR of flags, but not mentioned explicitly). I saw that in the latest 3K docs, it is documented properly: re.compile(pattern, flags=0) Naturally this applies to other methods of 're' that take 'flags'. I hope I'm not missing something and this really is just a documentation issue. If no objections arise, I will commit a fix to the docs of 're' in 2.7 -- assignee: docs@python components: Documentation messages: 143300 nosy: docs@python, eli.bendersky, ezio.melotti, pitrou priority: normal severity: normal status: open title: backport re.compile flags default value documentation versions: Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12875 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12875] backport re.compile flags default value documentation
Ezio Melotti ezio.melo...@gmail.com added the comment: I don't think you are missing anything, but using ints instead of flags is discouraged (see #11957). OTOH there's no re.NOFLAGS flag that can be used instead. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12875 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12868] test_faulthandler.test_stack_overflow() failed on OpenBSD
Remi Pointel pyt...@xiri.fr added the comment: Hi, without-threads, it segfault: $ ./python -c import faulthandler; faulthandler.enable(); faulthandler._stack_overflow(); echo $? Fatal Python error: Segmentation fault Current thread 0x: File string, line 1 in module zsh: segmentation fault (core dumped) ./python -c 139 Thanks, Remi. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12868] test_faulthandler.test_stack_overflow() failed on OpenBSD
Remi Pointel pyt...@xiri.fr added the comment: However, if I run test_faulthandler.py, it seems to be ok: $ ./python Lib/test/test_faulthandler.py test_disable (__main__.FaultHandlerTests) ... ok test_dump_traceback (__main__.FaultHandlerTests) ... ok test_dump_traceback_file (__main__.FaultHandlerTests) ... ok test_dump_traceback_threads (__main__.FaultHandlerTests) ... skipped 'need threads' test_dump_traceback_threads_file (__main__.FaultHandlerTests) ... skipped 'need threads' test_dump_tracebacks_later (__main__.FaultHandlerTests) ... skipped 'need faulthandler.dump_tracebacks_later()' test_dump_tracebacks_later_cancel (__main__.FaultHandlerTests) ... skipped 'need faulthandler.dump_tracebacks_later()' test_dump_tracebacks_later_file (__main__.FaultHandlerTests) ... skipped 'need faulthandler.dump_tracebacks_later()' test_dump_tracebacks_later_repeat (__main__.FaultHandlerTests) ... skipped 'need faulthandler.dump_tracebacks_later()' test_dump_tracebacks_later_twice (__main__.FaultHandlerTests) ... skipped 'need faulthandler.dump_tracebacks_later()' test_enable_file (__main__.FaultHandlerTests) ... ok test_enable_single_thread (__main__.FaultHandlerTests) ... ok test_fatal_error (__main__.FaultHandlerTests) ... ok test_gil_released (__main__.FaultHandlerTests) ... ok test_is_enabled (__main__.FaultHandlerTests) ... ok test_read_null (__main__.FaultHandlerTests) ... ok test_register (__main__.FaultHandlerTests) ... ok test_register_chain (__main__.FaultHandlerTests) ... ok test_register_file (__main__.FaultHandlerTests) ... ok test_register_threads (__main__.FaultHandlerTests) ... ok test_sigabrt (__main__.FaultHandlerTests) ... ok test_sigbus (__main__.FaultHandlerTests) ... ok test_sigfpe (__main__.FaultHandlerTests) ... ok test_sigill (__main__.FaultHandlerTests) ... ok test_sigsegv (__main__.FaultHandlerTests) ... ok test_stack_overflow (__main__.FaultHandlerTests) ... ok test_unregister (__main__.FaultHandlerTests) ... ok -- Ran 27 tests in 1.281s OK (skipped=7) Remi. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12875] backport re.compile flags default value documentation
Ezio Melotti ezio.melo...@gmail.com added the comment: Two more things: 1) Python 2 doc used to use the func(arg[, optional1[, optional2]]) notation, and with Python 3 we switched to func(arg, optional1=default1, optional2=default2). The latter is also used in Python 2 now, and the [] are still there in Python 3 in some places; 2) If you are going to fix it, you can probably backport the fix from py3k with hg diff Doc/library/re.rst -c 106ee4eb5970; -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12875 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
