[issue21116] Failure to create multiprocessing shared arrays larger than 50% of memory size under linux
Médéric Boquien added the comment: I have now signed the contributor's agreement. As for the unit test I was looking at it. However, I was wondering how to write a test that would have triggered the problem. It only shows up for very large arrays and it depends on occupied memory and the configuration of the temp dir. Or should I simply write a test creating for instance a 100 MB array and checking it has the right length? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21116 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21111] PyLong_AsUnsignedLongAndOverflow does not exist
Mark Dickinson added the comment: Sounds reasonable to me. Were there particular uses you needed this for? And do you want to work on a patch? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13824] argparse.FileType opens a file and never closes it
paul j3 added the comment: From http://bugs.python.org/issue14156 argparse.FileType for '-' doesn't work for a mode of 'rb' I learned that 'stdin/out' can be embedded in an 'open' by using the 'fileno()' and 'closefd=False' (so it isn't closed at the end of open). With this, the dummy file context that I implemented in the previous patch, could be replaced with: partial(open, sys.stdin.fileno(), mode=self._mode,..., closefd=False) However, as Steven Bethard wrote in the earlier issue, setting up tests when stdin/out will be redirected is not a trivial problem. So I don't yet have a testable patch. --- And just for the record, the 'osaccess' testing that I wrote earlier, probably should also test that proposed output file string is not already a directory. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13824 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14156] argparse.FileType for '-' doesn't work for a mode of 'rb'
paul j3 added the comment: A related issue http://bugs.python.org/issue13824 argparse.FileType opens a file and never closes it I proposed a FileContext class that returns a `partial(open, filename,...)' context object. The issues of how to deal with stdin/out are similar. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14156 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21120] PyArena type is used in headers from the limited API
New submission from Andrey: Hi all, The PyArena data type is defined in the pyarena.h under the #ifndef Py_LIMITED_API statement, so it's not included in the limited api. But this type is used in Python-ast.h, ast.h and asdl.h headers that included in the limited api, because they don't contain any checks for Py_LIMITED_API. May be all these header files (Python-ast.h, ast.h, asdl.h) should begin with #ifndef Py_LIMITED_API (excluded from the limited api)? Thanks. -- components: Library (Lib) messages: 215300 nosy: aponomarenko priority: normal severity: normal status: open title: PyArena type is used in headers from the limited API type: compile error versions: Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21120 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21118] str.translate is absurdly slow in majority of use cases (takes up to 60x longer than similar functions)
STINNER Victor added the comment: str.translate() currently allocates a buffer of UCS4 characters. translate_writer.patch: - modify _PyUnicode_TranslateCharmap() to use the _PyUnicodeWriter API - drop optimizations for error handlers different than ignore because there is no unit tests for them, and str.translate() uses ignore. It's safer to drop untested optimization. - cleanup also the code: charmaptranslate_output() is now responsible to handle charmaptranslate_lookup() result (to decrement the reference coutner) str.translate() may be a little bit faster when translating ASCII to ASCII for large string, but not so much. bytes.translate() is much faster because it builds a C array of 256 items to fast table lookup, whereas str.translate() requires a Python dict lookup for each character, which is much slower. codecs.charmap_build() (PyUnicode_BuildEncodingMap()) creates a C array (a three-level trie) for fast lookup. It is used with codecs.charmap_encode() for 8-bit encodings. We may reuse it for simple cases, like translating ASCII to ASCII. -- keywords: +patch Added file: http://bugs.python.org/file34691/translate_writer.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21118 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21118] str.translate is absurdly slow in majority of use cases (takes up to 60x longer than similar functions)
Changes by Serhiy Storchaka storch...@gmail.com: -- stage: - patch review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21118 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21085] compile error Python3.3 on Cygwin
dellair jie added the comment: Martin, Here is the values presented on Python 3.4.0, in fact they are the same as 3.3.2, please note the key difference. /* #undef HAVE_SIGTIMEDWAIT */ #define HAVE_SIGWAIT 1 #define HAVE_SIGWAITINFO 1 The SIGTIMEDWAIT is undef while the SIGWAIT is defined. The patch Victor found (https://github.com/Alexpux/MSYS2-packages/blob/master/python3/3.3.2-cygwin-siginfo.patch) to modify sigalmodule.c works on both 3.3.2 and 3.4 (at least the build went through the sign failure.) So shall we close this issue? Petrov, Thanks a loot! The patch you offered about parser works with 3.3.2 and 3.4. There is further issues with the build on Cygwin and I will raise it in a separate issue. Br, Dellair -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21085 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21085] compile error Python3.3 on Cygwin
STINNER Victor added the comment: So shall we close this issue? Nope. Could you please try the test described in msg215249? We might integrate https://github.com/Alexpux/MSYS2-packages/blob/master/python3/3.3.2-cygwin-siginfo.patch but it would be better to fix sigwaitinfo() if it works without si_band. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21085 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21113] Error usage of class.__bases__
Lotus Qin added the comment: get the __doc__ in a wrong way, it works now. -- resolution: - invalid status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21113 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21121] -Werror=declaration-after-statement is added even for extension modules through setup.py
New submission from nils: I got an error while rebuilding a module for 3.4. This was a ISO C90 error but setup.py explicitely adds -std=c99 to the gcc parameters, and indeed it is used. fifo.h:114:5: error: ISO C90 forbids mixed declarations and code [-Werror=declaration-after-statement] uint32_t ofs = fifo-write_count - fifo-write_offset; However, Py 3.4 seems to add -Werror=declaration-after-statement also for extension modules. This should not happe (said also Yhg1s in #python). Attached is a file that shows the setup.py and also the error log. -- components: Build, Distutils, Extension Modules files: pybug.txt messages: 215305 nosy: dstufft, eric.araujo, nilsge priority: normal severity: normal status: open title: -Werror=declaration-after-statement is added even for extension modules through setup.py versions: Python 3.4 Added file: http://bugs.python.org/file34692/pybug.txt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21121 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1298835] Add a vendor-packages directory for system-supplied modules
Robert Kuska added the comment: Ok, I have started a thread at pypa-devs google group. https://groups.google.com/forum/#!topic/pypa-dev/r6qsAmJl9t0 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1298835 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21122] CPython fails to build modules with LLVM LTO on Mac OS
New submission from Jonas Wagner: CPython fails to build with LLVM's link-time optimization (LTO) in Mac OS. Very similar commands work on Linux. I'm currently configuring CPython as follows: on Linux: RANLIB=ar -s --plugin=/path/to/llvm/lib/LLVMgold.so CC=/path/to/llvm/bin/clang CXX=/path/to/llvm/bin/clang++ CFLAGS=-g -flto LDFLAGS=-flto ./configure on Mac OS: CC=/path/to/llvm/bin/clang CXX=/path/to/llvm/bin/clang++ CFLAGS=-g -flto LDFLAGS=-flto ./configure The RANLIB variable should not be needed on Mac, because its toolchain does not need a GOLD plugin. On Linux, the above builds correctly and passes most of the test suite. On Mac, I receive the following error (similar for other extensions): building '_scproxy' extension /usr/bin/clang -Wno-unused-result -Werror=declaration-after-statement -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -g -flto -I../cpython/Include -I. -I/usr/local/include -I../cpython/Include -I../cpython-lto-build -c ../cpython/Modules/_scproxy.c -o build/temp.macosx-10.9-x86_64-3.5/path/to/cpython/Modules/_scproxy.o /usr/bin/clang -bundle -undefined dynamic_lookup -flto build/temp.macosx-10.9-x86_64-3.5/path/to/cpython/Modules/_scproxy.o -L/usr/local/lib -o build/lib.macosx-10.9-x86_64-3.5/_scproxy.so -framework SystemConfiguration -framework CoreFoundation *** WARNING: renaming _scproxy since importing it failed: dlopen(build/lib.macosx-10.9-x86_64-3.5/_scproxy.so, 2): Symbol not found: __Py_NoneStruct Referenced from: build/lib.macosx-10.9-x86_64-3.5/_scproxy.so Expected in: flat namespace in build/lib.macosx-10.9-x86_64-3.5/_scproxy.so -- components: Extension Modules messages: 215307 nosy: Sjlver priority: normal severity: normal status: open title: CPython fails to build modules with LLVM LTO on Mac OS type: compile error versions: Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21122 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21085] compile error Python3.3 on Cygwin
dellair jie added the comment: Victor, Would you please be more specific on test_signal? Br, Dellair -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21085 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21122] CPython fails to build modules with LLVM LTO on Mac OS
Changes by STINNER Victor victor.stin...@gmail.com: -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21122 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21122] CPython fails to build modules with LLVM LTO on Mac OS
Changes by STINNER Victor victor.stin...@gmail.com: -- nosy: +koobs ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21122 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21085] compile error Python3.3 on Cygwin
STINNER Victor added the comment:
Would you please be more specific on test_signal?
Please try to compile Python 3.4 with the attached cygwin_si_band.patch
applied, and then run test_signal. I would like to know if all tests pass, and
if not, which tests are failing. I also would like to know if
test_sigwaitinfo() runs on Cygwin. I'm not sure that signal.alarm(1) is
available on Windows, whereas test_sigwaitinfo() uses this function.
Or you can test manually sigwaitinfo(). Example on Windows using SIGINT and
CTRL+c to send a signal:
import signal
info = signal.sigwaitinfo({signal.SIGINT})
^C
info
signal.struct_siginfo(si_signo=2, si_code=128, si_errno=0, si_pid=0, si_uid=0,
si_status=3, si_band=0)
I don't know how to test sigwaitinfo() on Windows.
--
keywords: +patch
Added file: http://bugs.python.org/file34693/cygwin_si_band.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21085
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20767] Some python extensions can't be compiled with clang 3.4
Changes by Dirkjan Ochtman dirk...@ochtman.nl: -- nosy: +djc ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20767 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20767] Some python extensions can't be compiled with clang 3.4
Dirkjan Ochtman added the comment: Can we have some more feedback on this? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20767 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20767] Some python extensions can't be compiled with clang 3.4
STINNER Victor added the comment: See also issue #21122. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20767 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21120] PyArena type is used in headers from the limited API
Changes by STINNER Victor victor.stin...@gmail.com: -- nosy: +loewis ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21120 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21111] PyLong_AsUnsignedLongAndOverflow does not exist
STINNER Victor added the comment: Sounds reasonable to me. Were there particular uses you needed this for? And do you want to work on a patch? I don't understand why PyArg_Parse*() functions have formats for integers checking overflow for signed integers, but not for unsigned integers. For the zlib module, I had to develop my own format format (to get an unsigned int with overflow check) :-( -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21122] CPython fails to build modules with LLVM LTO on Mac OS
Jonas Wagner added the comment: I am indeed using Clang 3.4 (both the one that ships with Mac OS, and a version compiled from the sources). However, the errors I get are rather different than #20767. In particular, Clang finishes successfully and does produce shared object files; they just don't seem to be loadable. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21122 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21122] CPython fails to build modules with LLVM LTO on Mac OS
STINNER Victor added the comment: What is your clang version? See also issue #20767. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21122 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20767] Some python extensions can't be compiled with clang 3.4
Dirkjan Ochtman added the comment: That does look to be a different issue, though. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20767 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18644] Got ResourceWarning: unclosed file when using test function from formatter module
R. David Murray added the comment: There were a bunch of changes to pydoc in 3.4, so I'm not surprised that it doesn't use DumbWriter any more (possibly as part of the formatter pending deprecation). I think I was answering why it wasn't deprecated as part of the htmllib deprecation. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18644 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21117] inspect.signature: inaccuracies for partial functions
R. David Murray added the comment:
OK, I didn't even realize that was possible with partial. Now I understand
Yuri's original point. His example is wrong:
def foo(a, b):
...print(a, b)
x2 = partial(foo, 'x')
str(inspect.signature(x2))
'(b)'
This is the correct example:
x = partial(foo, a='x')
x('b')
Traceback (most recent call last):
File stdin, line 1, in module
TypeError: foo() got multiple values for argument 'a'
The current signature for this is the one Yuri gave:
str(inspect.signature(x))
(a='x', b)
Which is about as close as one can come to the rather non-intuitve
(non-pythonic?) behavior that partial has here. Perhaps this a bug in partial?
If so it is unfortunately one with ugly backward compatibility implications.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21117
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21121] -Werror=declaration-after-statement is added even for extension modules through setup.py
Changes by Stefan Krah stefan-use...@bytereef.org: -- nosy: +larry priority: normal - high ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21121 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21117] inspect.signature: inaccuracies for partial functions
R. David Murray added the comment: By didn't know that was possible, I mean binding a positional argument as a keyword argument in the partial. If nobody else thought that was possible, maybe can just fix it :) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21117 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21085] compile error Python3.3 on Cygwin
dellair jie added the comment: Victor, I suppose that Python needs to be built successfully before running test_signal. Three patches were applied in Python 3.4.0. However, the build failed to build _struct module. Should I open another Issue to track it? As long as the build goes through completely on Cygwin, I will go back and do the signal test. Br, Dellair -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21085 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21123] Compilation error on _struct module on Python 3.4
New submission from dellair jie: Dear all, I am compiling Python 3.4 on Cygwin 1.7.17. The following has been done in order to reach the point where _struct module failed. A clean Python 3.4 Applied patches: cygwin_si_band.patch in Issue21085 0001-CYGWIN-issue13756-Python-make-fail-on-cygwin.patch in issue13756 0019-MINGW-export-_PyNode_SizeOf-as-PyAPI-for-parser-modu.patch in issue186373 configure + make The issue happened during make: building '_struct' extension gcc -Wno-unused-result -Werror=declaration-after-statement -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I./Include -I. -IInclude -I/cygdrive/c/temp/Python-3.4.0/Include -I/cygdrive/c/temp/Python-3.4.0 -c /cygdrive/c/temp/Python-3.4.0/Modules/_struct.c -o build/temp.cygwin-1.7.17-i686-3.4/cygdrive/c/temp/Python-3.4.0/Modules/_struct.o /cygdrive/c/temp/Python-3.4.0/Modules/_struct.c:1630:5: error: initializer element is not constant /cygdrive/c/temp/Python-3.4.0/Modules/_struct.c:1630:5: error: (near initialization for ‘unpackiter_type.ob_base.ob_base.ob_type’) Please feel free to find the build.log and the output of _struct.c.txt (gcc with -dD -E -DPy_BUILD_core) for more information. Thanks in advance, Br, Dellair -- files: _struct.c.txt messages: 215320 nosy: dellair.jie priority: normal severity: normal status: open title: Compilation error on _struct module on Python 3.4 versions: Python 3.4 Added file: http://bugs.python.org/file34694/_struct.c.txt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21123 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21124] Compilation error on _struct module on Python 3.4
New submission from dellair jie: Dear all, I am compiling Python 3.4 on Cygwin 1.7.17. The following has been done in order to reach the point where _struct module failed. A clean Python 3.4 Applied patches: cygwin_si_band.patch in Issue21085 0001-CYGWIN-issue13756-Python-make-fail-on-cygwin.patch in issue13756 0019-MINGW-export-_PyNode_SizeOf-as-PyAPI-for-parser-modu.patch in issue186373 configure + make The issue happened during make: building '_struct' extension gcc -Wno-unused-result -Werror=declaration-after-statement -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I./Include -I. -IInclude -I/cygdrive/c/temp/Python-3.4.0/Include -I/cygdrive/c/temp/Python-3.4.0 -c /cygdrive/c/temp/Python-3.4.0/Modules/_struct.c -o build/temp.cygwin-1.7.17-i686-3.4/cygdrive/c/temp/Python-3.4.0/Modules/_struct.o /cygdrive/c/temp/Python-3.4.0/Modules/_struct.c:1630:5: error: initializer element is not constant /cygdrive/c/temp/Python-3.4.0/Modules/_struct.c:1630:5: error: (near initialization for ‘unpackiter_type.ob_base.ob_base.ob_type’) Please feel free to find the build.log and the output of _struct.c.txt (gcc with -dD -E -DPy_BUILD_core) for more information. Thanks in advance, Br, Dellair -- files: _struct.c.txt messages: 215321 nosy: dellair.jie priority: normal severity: normal status: open title: Compilation error on _struct module on Python 3.4 versions: Python 3.4 Added file: http://bugs.python.org/file34695/_struct.c.txt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21124 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21124] Compilation error on _struct module on Python 3.4
dellair jie added the comment: The full build log -- Added file: http://bugs.python.org/file34696/Build.log ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21124 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21117] inspect.signature: inaccuracies for partial functions
Yury Selivanov added the comment: @Nick: Ouch... I'm halfway through the implementation, and it seems like your idea isn't going to work. Example (from unittest): def foo(a=1, b=2, c=3): pass _foo = partial(foo, a=10, c=13) Now, the signature for _foo, with your logic applied, will be: (b=2, *, a=10, c=13) If, however, you try to do the following call: _foo(11) It will fail with a TypeError got multiple values for argument 'a', because 'partial' will actually do this call: foo(11, a=10, c=13) I now remember this obstacle, that's why I have '_partial_kwarg'. So unfortunately, why I really like your idea, I don't think we can make it work. Now, I still want to get rid the '_partial_kwarg' attribute. Are you guys OK, if I introduce PartialParameter PartialSignature classes? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21117 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21117] inspect.signature: inaccuracies for partial functions
Yury Selivanov added the comment: @R. David: Yes, thank you, David. Too bad I haven't seen your last messages before I started working on the patch... -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21117 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21117] inspect.signature: inaccuracies for partial functions
R. David Murray added the comment: We'll have to wait for Nick to chime in, but I'll make a couple of comments. First, I think this is a bug in partial, so I think we need to decide what, if anything, to do about that first, before we decide if signature needs to compensate for it or not. The other comment is about ==/__hash__, in case that is involved in the solution: two objects may very well have the same __hash__ and *not* be equal, but they cannot have different __hash__es and *be* equal. The equality comparison algorithm uses __hash__ as a shortcut. If two objects have different hashes, they are not equal and we return False. If they have the same hash, then a full equality comparison is done before the result of __eq__ is returned. You will understand that this must be the case if you think about the nature of hashing: it throws away information. Cryptographic hashes used for identification are constructed such that the *probability* of a collision is very low, but it is still not zero, so how they are used is just as important as how they work. Our __hash__es are generally not that strong, so collision is likely. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21117 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21125] traceback.extract_tb says quadruple when it means tuple
New submission from Glenn Maynard: https://docs.python.org/2/library/traceback.html A “pre-processed” stack trace entry is a quadruple (filename, line number, function name, text) representing the information that is usually printed for a stack trace. There's no such thing as a quadruple. This should be tuple. -- assignee: docs@python components: Documentation messages: 215326 nosy: Glenn.Maynard, docs@python priority: normal severity: normal status: open title: traceback.extract_tb says quadruple when it means tuple ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21125 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21117] inspect.signature: inaccuracies for partial functions
Yury Selivanov added the comment: First, I think this is a bug in partial, so I think we need to decide what, if anything, to do about that first, before we decide if signature needs to compensate for it or not. Agree. Although, it looks like it's not something that partial is doing, it seems like this call logic is implemented somewhere way deeper. The other comment is about ==/__hash__ [...] Agree. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21117 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21117] inspect.signature: inaccuracies for partial functions
Yury Selivanov added the comment: Although, it looks like it's not something that partial is doing, it seems like this call logic is implemented somewhere way deeper. Forget about what I said. Yes, it's a bug in partial. Fixing it, will require having the code from Signature.bind reflected to C -- IOW you need to introspect the callable, get information about its parameters, and then compute the actual args kwargs. Which will make functools.partial much much slower. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21117 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21117] inspect.signature: inaccuracies for partial functions
R. David Murray added the comment: Oh, the error message comes from deep in the guts of python, yes. I'm saying that the fact that partial lets you write partial(foo, a='bar') when a is a positional argument is a bug. Even if other people agree with me (and they may not, consenting adults and all that), it may be a bug we are stuck with. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21117 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21125] traceback.extract_tb says quadruple when it means tuple
R. David Murray added the comment: A google for quadruple got me wikipedia as the first hit, with this as the match text: Quadruple may refer to: A 4-tuple, ... So, it's tech-speak. The alternative would be to say either a 4-tuple or a tuple of four elements. I'm fine with someone making that change, but I don't think it is terrible that the word is used the way it is. -- nosy: +r.david.murray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21125 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21123] Compilation error on _struct module on Python 3.4
dellair jie added the comment: Duplicated with Issue21124 -- resolution: - duplicate status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21123 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21076] Turn signal.SIG* constants into enums
Giampaolo Rodola' added the comment: If there are no other concerns I will commit latest patch tomorrow, then do the renaming. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21076 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15067] Clean up the sqlite3 docs
Roundup Robot added the comment: New changeset 2e13f0d49b8e by Zachary Ware in branch '2.7': Issue #15067: Remove reference to a rejected PEP. http://hg.python.org/cpython/rev/2e13f0d49b8e New changeset 4a2dabac976d by Zachary Ware in branch '3.4': Issue #15067: Port 2.7 sqlite3 docs to 3.4 http://hg.python.org/cpython/rev/4a2dabac976d New changeset 2c7ebb930b64 by Zachary Ware in branch 'default': Closes #15067: Merge port of 2.7 sqlite3 docs. http://hg.python.org/cpython/rev/2c7ebb930b64 -- nosy: +python-dev resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15067 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19546] configparser leaks implementation detail
Claudiu.Popa added the comment: But the last traceback conveys enough information, the user can see immediately that the given section does not exist. My problem with the current behaviour is that the first error distracts the user, while the actual problem is the second traceback. But I have another example which might contradict my proposal. In the example in the second traceback, it's not clear what `Bad value substitution` stands for and the first traceback adds the relevant context (the fact that key is missing). But I guess this stands for another issue, for enhancing the message for InterpolationMissingOptionError to transmit the fact that a given option is missing. Traceback (most recent call last): File C:\Python34\lib\configparser.py, line 410, in _interpolate_some v = map[var] File C:\Python34\lib\collections\__init__.py, line 789, in __getitem__ return self.__missing__(key)# support subclasses that define __missing__ File C:\Python34\lib\collections\__init__.py, line 781, in __missing__ raise KeyError(key) KeyError: 'home_dir1' During handling of the above exception, another exception occurred: Traceback (most recent call last): File stdin, line 1, in module File C:\Python34\lib\configparser.py, line 1204, in __getitem__ return self._parser.get(self._name, key) File C:\Python34\lib\configparser.py, line 773, in get d) File C:\Python34\lib\configparser.py, line 374, in before_get self._interpolate_some(parser, option, L, value, section, defaults, 1) File C:\Python34\lib\configparser.py, line 413, in _interpolate_some option, section, rest, var) configparser.InterpolationMissingOptionError: Bad value substitution: section: [Paths] option : my_dir key: home_dir1 rawval : /lumberjack -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19546 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21111] PyLong_AsUnsignedLongAndOverflow does not exist
Changes by Mark Dickinson dicki...@gmail.com: -- components: +Interpreter Core -Extension Modules stage: - needs patch type: - enhancement versions: +Python 3.5 -Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21126] Integrate doctest.run_docstring_examples() with unittest
New submission from Giampaolo Rodola': In order to run a certain function via doctest run_docstring_examples() can be used: http://stackoverflow.com/a/10081450/376587 The function returns None though. I am in a situation where I want to run a single function's doctest from a unittest and want to fail in case the doctest fails. Patch in attachment makes run_docstring_examples() return a list of TestResults instances so that you can do: class TestFoo(unittest.TestCase): def test_foo(self): ret = doctest.run_docstring_examples(somefun, globals()) self.assertFalse(ret[0].failed) Patch lacks tests because run_docstring_examples() is currently not tested. I will open a separate ticket for that. -- files: doctest.patch keywords: patch messages: 215335 nosy: giampaolo.rodola, tim.peters priority: normal severity: normal status: open title: Integrate doctest.run_docstring_examples() with unittest versions: Python 3.5 Added file: http://bugs.python.org/file34697/doctest.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21126 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19546] configparser leaks implementation detail
R. David Murray added the comment: Why? Just let the context convey the information. It's not like we are building a UI here, this is for the programmer. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19546 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19546] configparser leaks implementation detail
R. David Murray added the comment: Although I will grant you that I have to guess at what the bad value substitution error message is trying to tell me, so that error message could use some improvement. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19546 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17846] Building Python on Windows - Supplementary info
michael kearney added the comment: Observation: Tools\buildbot\build.bat solves all the problems I was having. That is to say, a single command exists to build python on windows w/o problems. It has worked since at least since python 3.3.1, which I think preceded my original submission. So this has existed all this time, but has not been suggested as the solution it seems to be. What's wrong with it? Is it about to be deprecated perhaps? The DevGuide recommends external.bat in the same directory. build.bat calls external.bat and does more. Detail: If I 1. place the unzipped downloaded file folder isolated within another folder so that external projects can be built adjacent to python. 2. make certain that svn,nasm,VC++, are in my path. 3. cd to the python root 4. execute the command : Tools\buildbot\build.bat Then python_d.exe is created in the PCbuild folder. This is true for python 3.3.1, 3.3.2, 3.3.4, 3.4.0, and the current development version. I have built all since yesterday. I skipped 3.3.3 only because I didn't have the source downloaded OK, I lied a little. 1. The 3.3.1 release python.org areas had a corrupt openSSL rev d, I think. I modified my local external.bat to get a later version to solve that problem. 2. Other releases build debug tcltk release libs when debug libs are needed, and vice versa. I made copies of whatever existed and renamed the copy to whatever was required. But this is nothing compared what I was going through before. I personally like to have python.exe around also. To create python.exe, I only now open pcbuild.sln to start VC++, chose the release configuration, and hit F7. I have learned that it is best to run build.bat first before using pcbuild.sln with the VC++ IDE to build anything. It currently does not work for AMD64 but I maguessing that ti would be a good model to follow. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17846 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21118] str.translate is absurdly slow in majority of use cases (takes up to 60x longer than similar functions)
Josh Rosenberg added the comment: @haypo: Are you planning to run with this then? Or shall I pick up where your patch leaves off? Thanks for the pointer to the codecs charmap_build; it's not documented anywhere that I can tell, so I didn't even know it existed. Now to dig into the source to figure out what it does and how to use it (both in C and Python). I know about the fundamental design differences that makes bytes.translate kick str.translate's butt; my plan to make a special purpose mapping-like object that didn't require C layer code to wrap up Py_UCS4 in PyLong, or pull Py_UCS4 out of PyUnicode/PyLong objects was largely to try and get a bytes.translate like implementation, but if codecs.charmap_build()/PyUnicode_BuildEncodingMap() can get me 90% of the way there without reinventing the wheel, it's clearly worth looking at. Again, let me know if it's okay if I try to finish off the work you began, or if you'd prefer to do it yourself. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21118 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21117] inspect.signature: inaccuracies for partial functions
Nick Coghlan added the comment: Huh, that actually sounds like a possible design flaw in the core argument binding semantics. I'll have to think about that one some more. In the meantime, as far as this issue goes, I'm inclined to say that signature should throw an exception to be clear that such a malformed object has *no* usable signature, as attempting to call it will always fail. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21117 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21117] inspect.signature: inaccuracies for partial functions
Nick Coghlan added the comment: Oh, wait, it *does* have a usable signature. It's just that all the *subsequent* positional-or-keyword parameters also have to be marked as keyword-only. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21117 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21127] Path objects cannot be constructed from str subclasses
New submission from Antony Lee: Trying to construct a Path object from a str subclass, e.g. class S(str): pass Path(S(foo)) fails because the subclass cannot be interned. I think that the interning should simply be removed for non-exactly-str arguments (it is only here for performance reasons, right?), or at least the error should be more explicit (note, in particular, that there is no error if one tries 'Path(S(foo/bar))' instead, which only confuses the matter more). In practice, I found out this via numpy, which provides its own str subclass, numpy.str_. -- components: Library (Lib) messages: 215342 nosy: Antony.Lee priority: normal severity: normal status: open title: Path objects cannot be constructed from str subclasses versions: Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21127 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21128] testing stdlib and compatibility with pypy
New submission from mattip: In continuation of issue 20887, this patch closes and removes all temp files created while running regression tests for stdlib 2.7.6 on win32 and pypy. Note that a gc.collect was required to release the closed files in test_argparse, as well as making them all rw. -- components: Tests files: patch messages: 215343 nosy: mattip priority: normal severity: normal status: open title: testing stdlib and compatibility with pypy type: behavior versions: Python 2.7 Added file: http://bugs.python.org/file34698/patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21128 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21122] CPython fails to build modules with LLVM LTO on Mac OS X
Ned Deily added the comment: Just as an experiment (using the 3.4 branch and the Xcode 5.1 clang), the list of unique symbols not found during the test dlopen in setup.py when using -flto: _PyArg_ParseTuple _PyArg_ParseTupleAndKeywords _PyBaseObject_Type _PyBool_Type _PyByteArray_Type _PyBytes_Type _PyCFunction_Type _PyExc_AssertionError _PyExc_BufferError _PyExc_EOFError _PyExc_IndexError _PyExc_IOError _PyExc_KeyError _PyExc_LookupError _PyExc_MemoryError _PyExc_NotImplementedError _PyExc_OSError _PyExc_OverflowError _PyExc_RuntimeError _PyExc_TypeError _PyExc_ValueError _PyModule_Create2 __Py_NoneStruct Anyone see a pattern there? Do we know if anyone has tried to use LTO with a Python build previously? I've never tried it myself and there certainly could be ld and/or dyld differences on OS X. Also, some thought would need to go into and tests developed to see what the performance trade-offs are. For example, I could imagine that LTO might be have more impact if the standard library extension modules were statically linked, e.g. via Modules/Setup*. And there are at least three separate current build configurations to consider on OS X: unshared, --enable-shared, --enable-framework. One would need to look at things like what effect these all have on memory and shared memory footprints as well as cpu resources and real time, with and without LTO and/or other optimizations. It certainly would be an interesting project for someone with the interest and time. Potentially supporting LTO seems to me to be more of a feature than a bug so I think should be considered a 3.5 issue, at least initially. -- components: +Build -Extension Modules nosy: +brett.cannon, ned.deily, ronaldoussoren title: CPython fails to build modules with LLVM LTO on Mac OS - CPython fails to build modules with LLVM LTO on Mac OS X type: compile error - versions: +Python 3.5 -Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21122 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21082] os.makedirs(exist_ok=True) is not thread-safe: umask is set temporary to 0, serious security problem
Roundup Robot added the comment: New changeset 9186f4a18584 by Benjamin Peterson in branch '3.2': remove directory mode check from makedirs (closes #21082) http://hg.python.org/cpython/rev/9186f4a18584 New changeset 6370d44013f7 by Benjamin Peterson in branch '3.3': merge 3.2 (#21082) http://hg.python.org/cpython/rev/6370d44013f7 New changeset c24dd53ab4b9 by Benjamin Peterson in branch '3.4': merge 3.3 (#21082) http://hg.python.org/cpython/rev/c24dd53ab4b9 New changeset adfcdc831e98 by Benjamin Peterson in branch 'default': merge 3.4 (#21082) http://hg.python.org/cpython/rev/adfcdc831e98 -- nosy: +python-dev resolution: - fixed stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21082 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21082] os.makedirs(exist_ok=True) is not thread-safe: umask is set temporary to 0, serious security problem
Benjamin Peterson added the comment: I've now removed the offending behavior. exist_ok is still racy because it uses path.isdir() in the exceptional case, but fixing that can be an enhancement elsewhere. -- nosy: +benjamin.peterson ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21082 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21117] inspect.signature: inaccuracies for partial functions
Yury Selivanov added the comment: Oh, wait, it *does* have a usable signature. It's just that all the *subsequent* positional-or-keyword parameters also have to be marked as keyword-only. Interesting idea. I'll incorporate this logic into the patch. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21117 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21121] -Werror=declaration-after-statement is added even for extension modules through setup.py
Ned Deily added the comment: It looks like -Werror=declaration-after-statement was added to BASECFLAGS in configure.ac during the 3.4 development cycle by a3559c8c614b and e47806951fb2. Unfortunately, BASECFLAGS propagates through to extension module builds as well. If -Werror=declaration-after-statement should only be restricted to the build of the interpreter executable itself, one option *might be* to move the test and definition to CFLAGSFORSHARED in configure.ac. A workaround could be to define CFLAGS before rebuilding a module: export CFLAGS=$(python3.4 -c 'import sysconfig; print(sysconfig.get_config_var(CFLAGS).replace(-Werror=declaration-after-statement,))') (As usual, my brain hurts after trying to sift through the myriad build flags and their interactions in configure.ac, Makefile, and setup.py.) -- nosy: +benjamin.peterson, ned.deily ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21121 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21124] _struct module compilation error under Cygwin 1.7.17 on Python 3.4
Ned Deily added the comment: This looks like a duplicate of Issue6672. -- components: +Build nosy: +ned.deily resolution: - duplicate stage: - committed/rejected status: open - pending superseder: - Add Mingw recognition to pyport.h to allow building extensions title: Compilation error on _struct module on Python 3.4 - _struct module compilation error under Cygwin 1.7.17 on Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21124 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21127] Path objects cannot be constructed from str subclasses
Changes by Ned Deily n...@acm.org: -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21127 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21128] testing stdlib and compatibility with pypy
Changes by Ned Deily n...@acm.org: -- keywords: +patch nosy: +serhiy.storchaka stage: - patch review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21128 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21121] -Werror=declaration-after-statement is added even for extension modules through setup.py
nils added the comment: The workaround indeed works. At least I can work now until this gets officialy fixed. Thanks! export CFLAGS=$(python3.4 -c 'import sysconfig; print(sysconfig.get_config_var(CFLAGS).replace(-Werror=declaration-after-statement,))') -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21121 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21129] Segfault in python interpreter
New submission from Mayank Gupta: If I open the python interpreter: $ python Then type def to_hex(i): result = hex(i)[2:] My interpreter segfaults (EXC_BAD_ACCESS). Here's a backtrace from lldb: (lldb) bt * thread #1: tid = 0x152e7f, 0x0001002eff97 readline.so`call_readline + 647, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0) * frame #0: 0x0001002eff97 readline.so`call_readline + 647 frame #1: 0x00018852 Python`PyOS_Readline + 274 frame #2: 0x0001a0a8 Python`tok_nextc + 104 frame #3: 0x0001a853 Python`PyTokenizer_Get + 147 frame #4: 0x0001544a Python`parsetok + 218 frame #5: 0x0001000e7722 Python`PyParser_ASTFromFile + 146 frame #6: 0x0001000e8983 Python`PyRun_InteractiveOneFlags + 243 frame #7: 0x0001000e8c6e Python`PyRun_InteractiveLoopFlags + 78 frame #8: 0x0001000e9451 Python`PyRun_AnyFileExFlags + 161 frame #9: 0x0001000ffc9f Python`Py_Main + 2111 frame #10: 0x00010f14 Python I am using cpython 2.7.3. -- components: Interpreter Core messages: 215351 nosy: mayank priority: normal severity: normal status: open title: Segfault in python interpreter type: crash versions: Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21129 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21129] Segfault in python interpreter
Zachary Ware added the comment: If you're using OS X 10.9+, you'll need to upgrade your Python installation. See #18458. -- nosy: +zach.ware resolution: - duplicate stage: - committed/rejected status: open - closed superseder: - interactive interpreter crashes and test_readline fails on OS X 10.9 Mavericks due to libedit update ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21129 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4712] Document pickle behavior for subclasses of dicts/lists
Changes by Eric Snow ericsnowcurren...@gmail.com: -- nosy: +eric.snow versions: +Python 3.5 -Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4712 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21125] traceback.extract_tb says quadruple when it means tuple
Raymond Hettinger added the comment: I'll make the change to 4-tuple. -- assignee: docs@python - rhettinger nosy: +rhettinger ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21125 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21125] traceback.extract_tb says quadruple when it means tuple
Roundup Robot added the comment: New changeset 1c112eb4eb56 by Raymond Hettinger in branch '2.7': Issue 21125: minor wording tweak. http://hg.python.org/cpython/rev/1c112eb4eb56 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21125 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21125] traceback.extract_tb says quadruple when it means tuple
Roundup Robot added the comment: New changeset dfa399e74fcf by Raymond Hettinger in branch '3.4': Issue 21125: minor documentation tweak. http://hg.python.org/cpython/rev/dfa399e74fcf -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21125 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21125] traceback.extract_tb says quadruple when it means tuple
Raymond Hettinger added the comment: Thanks for the bug report, Glenn. -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21125 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20968] mock.MagicMock does not mock __truediv__
Raymond Hettinger added the comment: The patch looks clean and correct. It passes the test suite. I recommend going ahead and applying the patch. -- nosy: +rhettinger ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20968 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18652] Add itertools.first_true (return first true item in iterable)
Changes by Joshua Bronson jabron...@gmail.com: -- nosy: +jab ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18652 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
