[issue17226] libintl should also check for libiconv
Alan Hourihane added the comment: Sure this is on an Atari m68k platform called FreeMiNT. Traditionally in configure scripts you'll see it checked as *-mint* -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17226 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17228] Building without PYMALLOC fails
Changes by Dirkjan Ochtman dirk...@ochtman.nl: -- nosy: +hynek, ned.deily, ronaldoussoren ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17228 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17228] Building without PYMALLOC fails
Changes by Dirkjan Ochtman dirk...@ochtman.nl: -- nosy: +djc ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17228 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7469] Design and History FAQ entry on Floating Point does not mention short repr.
Mark Dickinson added the comment: Agreed; I think this did all get updated at one point or another. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7469 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17231] Mark __del__ not being called in cycles as an impl detail
Mark Dickinson added the comment: Just for the record, the python-dev discussion starts here: http://mail.python.org/pipermail/python-dev/2013-February/124044.html -- nosy: +mark.dickinson ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17231 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17234] python-2.7.3-r3: crash in visit_decref()
New submission from Martin Mokrejs: Hi, I do see relatively often a crash in python. Here is one stacktrace from my Gentoo Linux running 3.7.4 kernel: (gdb) where #0 0x7f624f340f08 in visit_decref () from /usr/lib64/libpython2.7.so.1.0 #1 0x7f624f2a455a in list_traverse () from /usr/lib64/libpython2.7.so.1.0 #2 0x7f624f3412c7 in collect () from /usr/lib64/libpython2.7.so.1.0 #3 0x7f624f341f11 in _PyObject_GC_Malloc () from /usr/lib64/libpython2.7.so.1.0 #4 0x7f624f2cdd59 in PyType_GenericAlloc () from /usr/lib64/libpython2.7.so.1.0 #5 0x7f624f2d09c3 in type_call () from /usr/lib64/libpython2.7.so.1.0 #6 0x7f624f27bdc3 in PyObject_Call () from /usr/lib64/libpython2.7.so.1.0 #7 0x7f624f310d76 in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0 #8 0x7f624f31285e in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0 #9 0x7f624f313905 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.7.so.1.0 #10 0x7f624f313a32 in PyEval_EvalCode () from /usr/lib64/libpython2.7.so.1.0 #11 0x7f624f32d97c in run_mod () from /usr/lib64/libpython2.7.so.1.0 #12 0x7f624f32e53d in PyRun_StringFlags () from /usr/lib64/libpython2.7.so.1.0 #13 0x7f624f30a44e in builtin_eval () from /usr/lib64/libpython2.7.so.1.0 #14 0x7f624f312456 in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0 #15 0x7f624f313905 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.7.so.1.0 #16 0x7f624f2a104c in function_call () from /usr/lib64/libpython2.7.so.1.0 #17 0x7f624f27bdc3 in PyObject_Call () from /usr/lib64/libpython2.7.so.1.0 #18 0x7f624f28a82f in instancemethod_call () from /usr/lib64/libpython2.7.so.1.0 #19 0x7f624f27bdc3 in PyObject_Call () from /usr/lib64/libpython2.7.so.1.0 #20 0x7f624f30c9b7 in PyEval_CallObjectWithKeywords () from /usr/lib64/libpython2.7.so.1.0 #21 0x7f624612f807 in call_with_frame.isra.9 () from /usr/lib64/python2.7/lib-dynload/pyexpat.so #22 0x7f6246132080 in my_StartElementHandler () from /usr/lib64/python2.7/lib-dynload/pyexpat.so #23 0x7f6245ed0fb0 in doContent () from /usr/lib64/libexpat.so.1 #24 0x7f6245ed21b4 in contentProcessor () from /usr/lib64/libexpat.so.1 #25 0x7f6245ecce2a in XML_ParseBuffer () from /usr/lib64/libexpat.so.1 #26 0x7f6246132d5b in xmlparse_Parse () from /usr/lib64/python2.7/lib-dynload/pyexpat.so #27 0x7f624f312456 in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0 #28 0x7f624f296379 in gen_send_ex.isra.1 () from /usr/lib64/libpython2.7.so.1.0 #29 0x7f624f2ce40f in wrap_next () from /usr/lib64/libpython2.7.so.1.0 #30 0x7f624f27bdc3 in PyObject_Call () from /usr/lib64/libpython2.7.so.1.0 #31 0x7f624f310d76 in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0 #32 0x7f624f31285e in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0 #33 0x7f624f31285e in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0 #34 0x7f624f31285e in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0 #35 0x7f624f31285e in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0 #36 0x7f624f313905 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.7.so.1.0 #37 0x7f624f313a32 in PyEval_EvalCode () from /usr/lib64/libpython2.7.so.1.0 #38 0x7f624f32d97c in run_mod () from /usr/lib64/libpython2.7.so.1.0 #39 0x7f624f32e750 in PyRun_FileExFlags () from /usr/lib64/libpython2.7.so.1.0 #40 0x7f624f32f1cf in PyRun_SimpleFileExFlags () from /usr/lib64/libpython2.7.so.1.0 #41 0x7f624f3407e2 in Py_Main () from /usr/lib64/libpython2.7.so.1.0 #42 0x7f624ec8f91d in __libc_start_main () from /lib64/libc.so.6 #43 0x0040094d in _start () (gdb) -- messages: 182371 nosy: mmokrejs priority: normal severity: normal status: open title: python-2.7.3-r3: crash in visit_decref() type: crash versions: Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17234 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17235] make sharedinstall ignores ./configure settings
New submission from Michael Kuhn: I need to install Python 2.7 in two architectures, but under one file system. I thus configure: /home/cellnet/michaelk/SRC/Python-2.7.3 ./configure --prefix=/home/cellnet/michaelk/biocluster --exec-prefix=/home/cellnet/michaelk/biocluster -q When I compile and then run make install, it will try to copy libraries to /home/cellnet/michaelk/lib64/python, i.e. it will try to copy files outside the specified prefixes. The step is make sharedinstall, which fails because I've temporarily made the lib64 directory read-only: [michaelk@biocluster2] /home/cellnet/michaelk/SRC/Python-2.7.3 make sharedinstall running build running build_ext building dbm using bdb Python build finished, but the necessary bits to build these modules were not found: bsddb185 dl gdbm imageopsunaudiodev To find the necessary bits, look in setup.py in detect_modules() for the module's name. running build_scripts ./python -E ./setup.py install \ --prefix=/home/cellnet/michaelk/biocluster \ --install-scripts=/home/cellnet/michaelk/biocluster/bin \ --install-platlib=/home/cellnet/michaelk/biocluster/lib/python2.7/lib-dynload \ --root=/ running install running build running build_ext building dbm using bdb Python build finished, but the necessary bits to build these modules were not found: bsddb185 dl gdbm imageopsunaudiodev To find the necessary bits, look in setup.py in detect_modules() for the module's name. running build_scripts running install_lib copying build/lib.linux-x86_64-2.7/_ctypes.so - /home/cellnet/michaelk/lib64/python error: could not delete '/home/cellnet/michaelk/lib64/python/_ctypes.so': Permission denied make: *** [sharedinstall] Error 1 -- components: Build messages: 182372 nosy: Michael.Kuhn priority: normal severity: normal status: open title: make sharedinstall ignores ./configure settings type: behavior versions: Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17235 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17232] Improve -O docs
Ramchandra Apte added the comment: It should also add that in the future, more optimizations may be added i.e. a peephole optimizer, etc. -- nosy: +Ramchandra Apte ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17232 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17234] python-2.7.3-r3: crash in visit_decref()
Ramchandra Apte added the comment: Sorry, but this doesn't give enough information to fix it, nevertheless reproduce it. Please tell us what Python was running. Also run python with -X faulthandler and give the results. -- nosy: +Ramchandra Apte ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17234 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17234] python-2.7.3-r3: crash in visit_decref()
Ramchandra Apte added the comment: Oops. Please ignore the sentence about adding -X faulthandler. Please install the faulthandler module [0] and run import faulthandler;faulthandler.enable(), and then reproduce the bug. ^0 https://pypi.python.org/pypi/faulthandler/ -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17234 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17232] Improve -O docs
Maciej Fijalkowski added the comment: There were not for at least 10 years. I would also be the first one to strongly object adding optimizations only under -O, because that already changes semantics. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17232 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17236] format_spec for sequence joining
New submission from Tobia Conforto:
The format specification mini-language (format_spec) supported by format() and
str.format() is a feature that allows passing short options to the classes of
the values being formatted, to drive their string representation (__format__
method)
The most common operation done to sequences (lists, tuples, sets...) during
conversion to string is arguably the string join operation, possibly coupled
with a nested string formatting of the sequence items.
I propose the addition of a custom format_spec for sequences, that allows to
easily specify a string for the join operation and optionally a nested
format_spec to be passed along to format the sequence items.
Here is the proposed addition:
seq_format_spec ::= join_string [: item_format_spec] | format_spec
join_string ::= '' join_string_char* '' | ' join_string_char* '
join_string_char ::= any character except {, }, newline, or the quote
item_format_spec ::= format_spec
In words, if the format_spec for a sequence starts with a single or double
quote, it will be interpreted as a join operation, optionally followed by
another colon and the format_spec for the sequnce items.
If the format_spec does not start with ' or , of if the quote is not balanced
(does not appear again in the format_spec), then it's assumed to be a generic
format string and the implementation would call super(). This ensures backwards
compatibility with existing code that may be using object's __format__
implementation on various sequence objects.
Please note I'm NOT proposing a change in the language or in the implementation
of format() and str.format(). This is just the addition of a __format__ method
to lists, tuples, sets and other sequence classes. The choice of whether to do
that in all those sequence classes or as an addition to object's __format__ is
an implementation detail.
Examples:
Basic usage: either {0:, } or {0:', '} when used in a format operation will
do this: , .join(str(x) for x in argument_0) in a more compact, possibly more
efficient, and arguably easier to read syntax.
Nested (regular) format_spec: {0:, :.1f} will join a list of floats using ,
as the separator and .1f as the format_spec for each float.
Nested join format_spec: {0:\n:, } will join a list of lists, using \n as
the outer separator and , as the inner separator. This could go on
indefinitely (but will rarely need to do so.)
I do not have a patch ready, but I can work on it and submit it for evaluation,
if this enhancement is accepted.
--
messages: 182376
nosy: tobia
priority: normal
severity: normal
status: open
title: format_spec for sequence joining
type: enhancement
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17236
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11215] test_fileio error on AIX
Changes by alef alessandro.for...@eumetsat.int: -- versions: +Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11215 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7063] Memory errors in array.array
Stefan Krah added the comment: I think msg93598 sums it up: array_ass_slice() is only called with v==NULL, so the issue can't be triggered. However, it's pretty dirty to leave the code as is (IIRC Coverity also had some complaints), so Chuck's suggestion to rewrite the function as array_del_slice() seems good to me. -- priority: normal - low stage: - needs patch type: - enhancement versions: +Python 3.3, Python 3.4 -Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7063 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17236] format_spec for sequence joining
R. David Murray added the comment: IMO, this is a python-ideas level suggestion. Please propose it on that mailing list. You can reopen the issue if you get a positive response there. -- nosy: +eric.smith, r.david.murray resolution: - later stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17236 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17232] Improve -O docs
Nick Coghlan added the comment: Ramchandra, as it turns out, if we deem an optimization semantically safe, we do it without -O, it we deem it unsafe, we don't do it at all. Thus, the real effect is to remove assert statements and optimise code as if __debug__ was replaced by a literal zero (effectively). So a more meaningful description would be: -O Removes assert statements and any code conditional on the value of __debug__. This changes the filename extension for compiled (bytecode) files from .pyc to .pyo. See also PYTHONOPTIMIZE. -- nosy: +ncoghlan ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17232 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17237] m68k aligns on 16bit boundaries.
New submission from Alan Hourihane: On m68k this assert triggers in Python/unicodeobject.c:4658 because m68k architectures can align on 16bit boundaries. assert(!((size_t) dest LONG_PTR_MASK)); I'm not sure of the wider implications in Python as to how to rectify. -- components: Build messages: 182381 nosy: alanh priority: normal severity: normal status: open title: m68k aligns on 16bit boundaries. versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17237 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17237] m68k aligns on 16bit boundaries.
Christian Heimes added the comment: We don't have a m86k test box and I don't think we support this platform either. -- nosy: +christian.heimes, trent ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17237 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17222] py_compile.compile() explicitly sets st_mode for written files
Brett Cannon added the comment: So that all happens because importlib does an atomic write of the file which uses os.replace(): http://hg.python.org/cpython/file/83d70dd58fef/Lib/importlib/_bootstrap.py#l121 . Unless there is some way that I can't think of to have the atomic write still exist but not change the type of file it replaces I am still not willing to revert my change just for this use case. There should be a single implementation of bytecode file generation and py_compile (along with compileall) should be nothing more than convenience modules for forcing the generation of those files under the same semantics as if they were done as a side-effect of importing some source code. -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17222 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17099] Raise ValueError when __loader__ not defined for importlib.find_loader()
Changes by Ankur Ankan ankuran...@gmail.com: -- nosy: +Ankur.Ankan ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17099 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7063] Memory errors in array.array
Chuck added the comment: I attached a patch, in which I removed v and all code having to do with inserting elements. In particular, I changed the value of b to being positive, since there is no distinction between increasing and decreasing size anymore. -- keywords: +patch nosy: +Chuck Added file: http://bugs.python.org/file29121/array_del_slice.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7063 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15767] add ImportNotFoundError
Brett Cannon added the comment: The original need was for internal importlib usage, but upon reflection it could also be used by the eval loop for that (http://hg.python.org/cpython/file/83d70dd58fef/Python/ceval.c#l4560), so I'm fine with changing the name to ImportNotFoundError. -- title: add ModuleNotFoundError - add ImportNotFoundError ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15767 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15976] Inconsistent behavior of search_for_exec_prefix() results in startup failure in certain cases
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +loewis, ncoghlan stage: - needs patch versions: +Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15976 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17232] Improve -O docs
Changes by Brett Cannon br...@python.org: -- nosy: +brett.cannon ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17232 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17228] Building without PYMALLOC fails
Brett Cannon added the comment: Why not define uint for the whole file regardless of PYMALLOC? -- nosy: +brett.cannon ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17228 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17231] Mark __del__ not being called in cycles as an impl detail
Changes by Brett Cannon br...@python.org: -- nosy: +brett.cannon ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17231 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17237] m68k aligns on 16bit boundaries.
Alan Hourihane added the comment: I'm willing to help fix, but there are m68k emulators out there which I guess suffice for a test box. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17237 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17237] m68k aligns on 16bit boundaries.
Stefan Krah added the comment: TBH, I don't think we should support this platform officially. Is that processor still in use (e.g. in embedded systems)? -- nosy: +skrah ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17237 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17237] m68k aligns on 16bit boundaries.
Ramchandra Apte added the comment: Wikipedia says derivative processors are still widely used in embedded applications. in m68k article. -- nosy: +Ramchandra Apte ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17237 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17237] m68k aligns on 16bit boundaries.
Jesús Cea Avión added the comment: Freescale (ex-Motorola) ColdFire architecture is alive and doing well. And I know people still running Motorola 68040 Apple machines. The problem is not a m68k emulator, but to build all the needed environment on it: OS, compilers, network, etc. If the original submitter is willing to help... -- nosy: +jcea ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17237 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13700] imaplib.IMAP4.authenticate authobject does not work correctly in python3
Demian Brecht added the comment: Has there been any further work/review done on this issue? I just ran into the problem myself on 3.4(dev) and can verify that the patch (imaplib_authenticate_v.patch) fixes the issue. -- nosy: +dbrecht versions: +Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13700 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17238] Enhance import statement completion
New submission from Ramchandra Apte: [patch under development] I propose to add completions for import tab from tab from x import tab Also, if one types imp.tab , IDLE should import the module and list dir(module). (There will be an option to disable/enable the last two completion cases as some users object to it importing modules for completion) -- components: IDLE messages: 182392 nosy: Ramchandra Apte, terry.reedy priority: normal severity: normal status: open title: Enhance import statement completion type: enhancement versions: Python 3.3, Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17238 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17239] XML vulnerabilities in Python
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +eli.bendersky, ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17239 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17239] XML vulnerabilities in Python
New submission from Christian Heimes: Experimental fix for XML vulnerabilities against default. It's NOT ready and needs lots of polishing. https://pypi.python.org/pypi/defusedxml contains explanations of all issues https://pypi.python.org/pypi/defusedexpat is a standalone version of part of the patches for Python 2.6 to 3.3 -- components: Extension Modules, Library (Lib), XML files: xmlbomb_20130219.patch keywords: patch messages: 182393 nosy: barry, benjamin.peterson, christian.heimes, georg.brandl, larry priority: release blocker severity: normal stage: needs patch status: open title: XML vulnerabilities in Python type: security versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4 Added file: http://bugs.python.org/file29122/xmlbomb_20130219.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17239 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17238] Enhance import statement completion
Changes by Ezio Melotti ezio.melo...@gmail.com: -- stage: - needs patch versions: -Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17238 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13719] bdist_msi upload fails
Christian Heimes added the comment: I have been bitten by the bug today, too. -- nosy: +christian.heimes versions: +Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13719 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17240] argparse: subcommand name and arity
New submission from Thibault Kruse:
I realize there have been several suggestions around argparse subcommands. Mine
is related to this isse:
http://bugs.python.org/issue9253
In short, I suggest that the add_subparsers() function take an argument like
nargs that determines how many times user may or have to use a subcommand. E.g.
?, 1, +, *. The multiples are useful for things like setup.py build bist
upload or make build test doc. I notice currently the subparsers object
created by add_subparsers() has this:
subparsers.nargs
'A...'
Does anyone know what that notation implies?
The default for nargs can be whatever it currently is, though issue9253 makes
me wonder whether there currently is any default behavior over different
argparse versions.
Also, I believe subcommands should have a name by which the choice of the
subcommands ends up in the arg namespace.
E.g.:
import argparse
argparser = argparse.ArgumentParser()
subparsers = argparser.add_subparsers()
subparser1 = subparsers.add_parser('foo')
subparser1.add_argument('--fooopt')
subparser2 = subparsers.add_parser('bar')
subparser2.add_argument('--baropt')
argparser.parse_args(['foo'])
Namespace(fooopt=None)
This is not satisfactory. I would prefer:
import argparse
argparser = argparse.ArgumentParser()
subparsers = argparser.add_subparsers('cmd1') % name here
subparser1 = subparsers.add_parser('foo')
subparser1.add_argument('--fooopt')
subparser2 = subparsers.add_parser('bar')
subparser2.add_argument('--baropt')
argparser.parse_args(['foo'])
Namespace(fooopt=None, cmd1='foo') % value here
The dest member of subparsers already seems to work as intended:
subparsers.dest='cmd1'; but users should not have to set it like that, to
improve early error checking.
--
components: Library (Lib)
messages: 182395
nosy: Thibault.Kruse
priority: normal
severity: normal
status: open
title: argparse: subcommand name and arity
type: enhancement
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17240
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15767] add ImportNotFoundError
Antoine Pitrou added the comment: The original need was for internal importlib usage, but upon reflection it could also be used by the eval loop for that (http://hg.python.org/cpython/file/83d70dd58fef/Python/ceval.c#l4560), so I'm fine with changing the name to ImportNotFoundError. I don't understand what ImportNotFoundError means: an import was not found? ModuleNotFoundError was obvious. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15767 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17222] py_compile.compile() explicitly sets st_mode for written files
Antoine Pitrou added the comment: Unless there is some way that I can't think of to have the atomic write still exist but not change the type of file it replaces How about using the `mode` to write_atomic? (which, incidentally, is already used to mirror the .py file's permissions in SourceFileLoader._cache_bytecode) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17222 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13700] imaplib.IMAP4.authenticate authobject does not work correctly in python3
R. David Murray added the comment: Demian: thanks for the reminder, and the confirmation that it works on a real server. Erno: thanks for the test fix. That was a pretty stupid mistake on my part :) -- resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13700 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13700] imaplib.IMAP4.authenticate authobject does not work correctly in python3
Roundup Robot added the comment: New changeset 3d4302718e7c by R David Murray in branch '3.2': #13700: Make imap.authenticate with authobject work. http://hg.python.org/cpython/rev/3d4302718e7c New changeset b21f955b8ba2 by R David Murray in branch '3.3': Merge: #13700: Make imap.authenticate with authobject work. http://hg.python.org/cpython/rev/b21f955b8ba2 New changeset d404d33a999c by R David Murray in branch 'default': Merge: #13700: Make imap.authenticate with authobject work. http://hg.python.org/cpython/rev/d404d33a999c -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13700 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17222] py_compile.compile() explicitly sets st_mode for written files
Brett Cannon added the comment: Use the mode how exactly? I mean isn't the problem the os.replace() call and not os.open() on the source file? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17222 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17239] XML vulnerabilities in Python
Changes by Franck Michea franck.mic...@gmail.com: -- nosy: +kushou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17239 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15767] add ImportNotFoundError
Brett Cannon added the comment: Technically it should be ModuleOrSomeObjectNotFoundBecauseFromListIsTheBaneOfMyExistenceError, but we might be starting to mix paints for paints a shed shortly. Fine, that's 1 to 1 for ModuleNotFoundError vs. ImportNotFoundError. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15767 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17222] py_compile.compile() explicitly sets st_mode for written files
Antoine Pitrou added the comment: Use the mode how exactly? I mean isn't the problem the os.replace() call and not os.open() on the source file? If you want to reproduce the original file's access rights, you have to pass the right mode flags to os.open(). Of course, this won't recreate symlinks and the like. But I don't think we can do something for that anyway, since we want to replace to happen automatically. People who like to have symlinks for their pyc files probably have their own custom scripts to create pyc files, so they should just re-use them. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17222 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17222] py_compile.compile() explicitly sets st_mode for written files
Antoine Pitrou added the comment: Of course, this won't recreate symlinks and the like. But I don't think we can do something for that anyway, since we want to replace to happen automatically. I meant: we want the replace to happen atomically :-) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17222 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15767] add ImportNotFoundError
Chris Jerdonek added the comment: If we can promise not to use it in the from-import case :) I'm okay with the more specific name (in fact it is preferable). From Brett's response, it sounds like we have flexibility there and don't need it to be the same? For from-import I would prefer the generic ImportError or adding a new type between ImportError and ModuleNotFoundError (like ImportNotFoundError) over using a name that is not entirely correct. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15767 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17241] Python-2.3.5.exe file possibly corrupt
New submission from Jeff Mansfield: Python-2.3.5.exe seems to be corrupt. I’ve tried downloading Python-2.3.5.exe a number of times in the past week, and so have a few of my colleagues. It always transfers in an incomplete manner, resulting in only 4.7 out of 9.1 MB. I have tried from several different Windows 7 boxes, with the same results. Perhaps something in my environment is messed up, but it may be that the file is corrupt on your server. -- messages: 182405 nosy: jeff_mansfield priority: normal severity: normal status: open title: Python-2.3.5.exe file possibly corrupt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17241 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17240] argparse: subcommand name and arity
Chris Jerdonek added the comment:
This is not satisfactory. I would prefer:
import argparse
argparser = argparse.ArgumentParser()
subparsers = argparser.add_subparsers('cmd1') % name here
Have you tried passing by keyword?
subparsers = argparser.add_subparsers(dest='cmd1')
It seems to work. I observed something similar for the metavar parameter on
issue 14039.
'A...'
Does anyone know what that notation implies?
I could be wrong, but I think this is just an arbitrary string for internal use.
--
nosy: +chris.jerdonek
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17240
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17241] Python-2.3.5.exe file possibly corrupt
Ezio Melotti added the comment: I tried to download it on a win xp machine and I succeeded at the first attempt (even thought it seemed to be stuck for a few seconds before reaching 100%). I was also able to start the installer, even thought I didn't install it. This is the version I downloaded: http://www.python.org/ftp/python/2.3.5/Python-2.3.5.exe May I ask you why you are attempting to download such an old release, and not even the latest 2.3 (there's 2.3.7 available, that also includes some security fixes)? -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17241 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14219] make the Classes tutorial more gentle
Changes by Tshepang Lekhonkhobe tshep...@gmail.com: -- title: start the Class tutorial in a more gentle manner - make the Classes tutorial more gentle versions: +Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14219 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17241] Python-2.3.5.exe file possibly corrupt
Jeff Mansfield added the comment: Ezio, It is what was in use on my old machine, and I don't want to move versions. Thanks, Jeff -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17241 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15767] add ImportNotFoundError
Serhiy Storchaka added the comment: Can this be the same ImportError but with special flag? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15767 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17237] m68k aligns on 16bit boundaries.
Antoine Pitrou added the comment: Which branch or version of Python is that? -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17237 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15767] add ImportNotFoundError
Barry A. Warsaw added the comment: On Feb 19, 2013, at 07:24 PM, Serhiy Storchaka wrote: Can this be the same ImportError but with special flag? Like an attribute on the exception? +1 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15767 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17242] Fix code highlight in devguide/docquality.rst
New submission from Berker Peksag: See for the current version: http://docs.python.org/devguide/docquality.html#helping-with-the-developer-s-guide -- components: Devguide files: devguide-highlight.diff keywords: patch messages: 182412 nosy: berker.peksag, ezio.melotti priority: normal severity: normal status: open title: Fix code highlight in devguide/docquality.rst Added file: http://bugs.python.org/file29123/devguide-highlight.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17242 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17033] RPM spec file has old config_binsuffix value
Taavi Burns added the comment: I'm not sure my vote means much, but the spec file didn't work for me on CentOS 5 anyway (weird issue with the -dev RPM trying to find python2.72.7). I think I'd prefer a README with suggested places to look for a working spec file than have this blessed-but-broken one in the source tree… -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17033 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17239] XML vulnerabilities in Python
Changes by Serhiy Storchaka storch...@gmail.com: -- nosy: +serhiy.storchaka ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17239 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15767] add ImportNotFoundError
Antoine Pitrou added the comment: Can this be the same ImportError but with special flag? Like an attribute on the exception? +1 ImportError.has_different_meaning_but_too_lazy_to_create_a_distinct_exception_class_for_it ? (or perhaps you would prefer the camelCase version :-)) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15767 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15767] add ImportNotFoundError
Brett Cannon added the comment: Chris: Having a more generic name for import-from at the eval loop level on top of NoModuleFoundError is breaking the practicality over purity rule. ImportSearchFailed might be the closest we can come to a generic name for what occurred. Serihy Barry: no. We do that now and it's already a nasty little hack. It would be better to let people catch an exception signaling that an import didn't happen because some module is missing than require introspection on a caught ImportError to tell what is going on (there's a reason why Antoine went to all of that trouble to add new exceptions so we don't have to look at the errno attribute on OSError). Exceptions are structured to work off of inheritance hierarchies (says the man who co-wrote the PEP to make all PEPs inherit from BaseException). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15767 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17222] py_compile.compile() explicitly sets st_mode for written files
Brett Cannon added the comment: I think Arfever is more frustrated by the os.replace() call than the permissions. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17222 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17237] m68k aligns on 16bit boundaries.
Alan Hourihane added the comment: As mention in the versions. It is Python 3.3.0. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17237 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17242] Fix code highlight in devguide/docquality.rst
Roundup Robot added the comment: New changeset 6015789cbce0 by Ezio Melotti in branch 'default': #17242: fix code highlight. Patch by Berker Peksag. http://hg.python.org/devguide/rev/6015789cbce0 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17242 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17222] py_compile.compile() explicitly sets st_mode for written files
Antoine Pitrou added the comment: Ah, right. Well, there would be an argument not to use os.replace() in py_compile, since it's an offline processing step which generally shouldn't race with another (online) processing step. Still, I wonder what the use case is (apart from the /dev/null case for which the answer is simply don't do it :-)). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17222 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17242] Fix code highlight in devguide/docquality.rst
Ezio Melotti added the comment: Fixed, thanks for the patch! -- resolution: - fixed stage: - committed/rejected status: open - closed type: - enhancement ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17242 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17237] m68k aligns on 16bit boundaries.
Antoine Pitrou added the comment: Ok, could you post the whole C stack trace? (using e.g. gdb) By the way, this is not about the alignment of m68k architectures: x86 can align on a byte boundary and doesn't trigger the assert. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17237 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17222] py_compile.compile() explicitly sets st_mode for written files
Brett Cannon added the comment: Exactly, and I don't want to have to slice up the internal API anymore in order to support this edge case which I don't think is important enough to support. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17222 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17242] Fix code highlight in devguide/docquality.rst
Changes by Ezio Melotti ezio.melo...@gmail.com: -- assignee: - ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17242 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11763] assertEqual memory issues with large text inputs
Ezio Melotti added the comment: There are some tests in the issue11763-2.diff patch. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11763 ___ ___ 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
Changes by Ezio Melotti ezio.melo...@gmail.com: -- components: +Extension Modules type: - behavior versions: +Python 3.3, Python 3.4 ___ 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
[issue17032] Misleading error message: global name 'X' is not defined
Ezio Melotti added the comment: GLOBAL_NAME_ERROR_MSG has been introduced in fd8c7203251f as part of PEP 227 by Jeremy Hylton, so I'm adding him to the nosy to see if he agrees with the change (also adding a couple more devs to see if they have any comments). There's also a typo in the last chunk of the patch. -- nosy: +Jeremy.Hylton, ncoghlan, terry.reedy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17032 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17243] The changes made for issue 4074 should be documented
New submission from R. David Murray: The section of the reference on the gc module goes into some detail on what the thresholds control and when collections are run, but does not currently document the backoff algorithm used when deciding whether or not to collect generation 2. This should presumably be documented. -- messages: 182425 nosy: pitrou, r.david.murray priority: normal severity: normal stage: needs patch status: open title: The changes made for issue 4074 should be documented type: behavior versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17243 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17032] Misleading error message: global name 'X' is not defined
Changes by Philip Jenvey pjen...@underboss.org: -- nosy: +pjenvey ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17032 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17244] py_compile.compile() fails to raise exceptions when writing of target file fails
New submission from Arfrever Frehtes Taifersar Arahesis: Since d4eb02b6aac9 py_compile.compile() fails to raise exceptions when writing of target file fails. $ cd /tmp $ touch test.py $ mkdir dir $ chmod a-w dir mode of ‘dir’ changed from 0755 (rwxr-xr-x) to 0555 (r-xr-xr-x) $ python3.3 -c 'import py_compile; py_compile.compile(test.py, cfile=/tmp/dir/test.pyc)' Traceback (most recent call last): File string, line 1, in module File /usr/lib64/python3.3/py_compile.py, line 141, in compile with open(cfile, 'wb') as fc: PermissionError: [Errno 13] Permission denied: '/tmp/dir/test.pyc' $ python3.4 -c 'import py_compile; py_compile.compile(test.py, cfile=/tmp/dir/test.pyc)' $ python3.3 -c 'import py_compile; py_compile.compile(test.py, cfile=/tmp/dir)' Traceback (most recent call last): File string, line 1, in module File /usr/lib64/python3.3/py_compile.py, line 141, in compile with open(cfile, 'wb') as fc: IsADirectoryError: [Errno 21] Is a directory: '/tmp/dir' $ python3.4 -c 'import py_compile; py_compile.compile(test.py, cfile=/tmp/dir)' $ ls -l dir total 0 $ -- components: Library (Lib) messages: 182426 nosy: Arfrever, brett.cannon, eric.snow, ncoghlan, pitrou priority: normal severity: normal status: open title: py_compile.compile() fails to raise exceptions when writing of target file fails type: behavior versions: Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17244 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6975] symlinks incorrectly resolved on POSIX platforms
Arfrever Frehtes Taifersar Arahesis added the comment: You could probably test '.\\.' and '..\\..' etc. in these tests on Windows. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6975 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17237] m68k aligns on 16bit boundaries.
Alan Hourihane added the comment: It must be about pointer alignment, because that's the whole point of the ASSERT. As for the backtrace, the gdb support on the platform isn't great yet, but here it is Breakpoint 1, ascii_decode (start=0x30c5b04 __len__, end=0x30c5b0b , dest=0x1a6d592 ���) at Objects/unicodeobject.c:4658 4658assert(!((size_t) dest LONG_PTR_MASK)); (gdb) bt #0 ascii_decode (start=0x30c5b04 __len__, end=0x30c5b0b , dest=0x1a6d592 ���) at Objects/unicodeobject.c:4658 #1 0x030595a6 in .L4737 () at Objects/unicodeobject.c:4741 #2 0x03044dba in .L2648 () at Objects/unicodeobject.c:1806 #3 0x03096f54 in PyUnicode_InternFromString (cp=0x30c5b04 __len__) at Objects/unicodeobject.c:14284 #4 0x030c69f6 in .L1892 () at Objects/typeobject.c:6090 #5 0x030c6dc8 in add_operators (type=0x33507c8) at Objects/typeobject.c:6244 #6 0x030bfc66 in .L1249 () at Objects/typeobject.c:4182 #7 0x030bfbae in .L1241 () at Objects/typeobject.c:4146 #8 0x02ff62a8 in _Py_ReadyTypes () at Objects/object.c:1576 #9 0x0300e688 in .L60 () at Python/pythonrun.c:301 #10 0x0300ea5c in Py_InitializeEx (install_sigs=1) at Python/pythonrun.c:401 #11 0x0300ea6e in Py_Initialize () at Python/pythonrun.c:407 #12 0x02ff9fca in .L135 () at Modules/main.c:657 #13 0x02ff24be in .L6 () at ./Modules/python.c:90 #14 0x03329d5a in .L76 () #15 0x0331731e in .L69 () -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17237 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17237] m68k aligns on 16bit boundaries.
Serhiy Storchaka added the comment: What will happened if you just remove this line? -- nosy: +serhiy.storchaka type: - crash ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17237 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17237] m68k aligns on 16bit boundaries.
Changes by Serhiy Storchaka storch...@gmail.com: -- components: +Unicode -Build nosy: +ezio.melotti versions: +Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17237 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17237] m68k aligns on 16bit boundaries.
Antoine Pitrou added the comment: It must be about pointer alignment, because that's the whole point of the ASSERT. Indeed, it's about pointer alignment, but it's not about the CPU. It's about the compiler (or the platform's C ABI). Apparently the compiler doesn't align struct fields to natural boundaries like most other compilers do, which means the size of the PyASCIIObject struct (in unicodeobject.h) ends up not being a multiple of 4, which in turn means the dest pointer (allocated from the end of that structure) is not 4 byte-aligned either. However, you can probably safely remove the assert(), since it is there to warn about misalignment on platforms which *are* alignment-sensitive. There is another assert() of the same kind in unicodeobject.c, which you can remove too. It would be nice if the C source could be improved here, but it's not obvious which rule to enforce exactly. We want to be lenient if the misalignment is a product of the compiler's alignment rules, but not if it's a mistake on our part. Which compiler is it? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17237 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17237] m68k aligns on 16bit boundaries.
Alan Hourihane added the comment: It's GCC 4.6.3. GCC has the -malign-int but mentions this isn't in best interest of m68k ABI compatibility if it's used. -- components: +Build -Unicode type: crash - versions: -Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17237 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17244] py_compile.compile() fails to raise exceptions when writing of target file fails
Brett Cannon added the comment: It's because of this try/except to silence failed bytecode creation: http://hg.python.org/cpython/file/d404d33a999c/Lib/importlib/_bootstrap.py#l1105 I hate the py_compile module. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17244 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17237] m68k aligns on 16bit boundaries.
Alan Hourihane added the comment: Oh, and as for pointer alignment, I probably just wasn't clear in the initial report. But we agree on m68k C ABI. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17237 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17237] m68k aligns on 16bit boundaries.
Antoine Pitrou added the comment: Ok, so we could simply disable the assert on m68k, if you can confirm it works. Do you want to provide a patch? I don't know what the preprocessor conditional should look like. -- components: +Interpreter Core -Build stage: - needs patch type: - crash versions: +Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17237 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17237] m68k aligns on 16bit boundaries.
Serhiy Storchaka added the comment: Perhaps we should disable not only assert, but all optimized code inside #if SIZEOF_LONG = SIZEOF_VOID_P / #endif block. Benchmarks needed to measure either unaligned writing speedup or slowdown decoding. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17237 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17237] m68k aligns on 16bit boundaries.
mirabilos added the comment: @skrah: “I don't think we should support this platform officially.” Please don’t break what works. We have almost complete (about three quarters of roughly 10'000 source packages) Debian unstable working on m68k, with several versions of Python in use. Thanks! @pitrou: “x86 can align on a byte boundary and doesn't trigger the assert.” That’s because most compilers on i386 do “natural alignment” – in fact, most compilers on most platforms do. “natural alignment” means 4-byte quantities get aligned on 4-byte boundaries, 8-byte quantities on 8-byte boundaries, etc. On m68k, the lowest alignment for almost all larger-than-a-byte data types is 2 byte, even though that one is strict. This means that, for example, an int is often only 2-byte aligned. @alanh: “GCC has the -malign-int but mentions this isn't in best interest of m68k ABI compatibility if it's used.” Indeed, because that would break the C and kernel/syscall ABI. @all: what _precisely_ is the assertion needed to check for? @pitrou: “since it is there to warn about misalignment on platforms which *are* alignment-sensitive” Well, m68k is. Just the numbers differ. (It also has int, long and pointer at 32 bit.) We had a similar issue in the Linux kernel, where it used the lower two bits of an address for flags (urgh…) which could only be solved by using GCC’s __attribute__((__aligned__(4))) on the quantities in question, but that may or may not be the required case here, which is why I’m asking. I can test any trees on my VMs, but that takes a day or two, of course, at 50-200 BogoMIPS. You can do that yourself by running a VM as well, the Debian Wiki has instructions, if anyone is interested. Otherwise, it’ll just get tested as soon as it hits Debian (unstable, usually we don’t build experimental packages except on explicit request by the packagers, due to lack of time / horsepower)… Thanks doko for linking this issue! -- nosy: +mirabilos ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17237 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15767] add ImportNotFoundError
Barry A. Warsaw added the comment: On Feb 19, 2013, at 07:49 PM, Brett Cannon wrote: Serihy Barry: no. We do that now and it's already a nasty little hack. It would be better to let people catch an exception signaling that an import didn't happen because some module is missing than require introspection on a caught ImportError to tell what is going on (there's a reason why Antoine went to all of that trouble to add new exceptions so we don't have to look at the errno attribute on OSError). Exceptions are structured to work off of inheritance hierarchies (says the man who co-wrote the PEP to make all PEPs inherit from BaseException). The difference being that checking errno on OSError/IOError is essentially required to do anything useful with it, while this one seems like a rare corner case (we've been doing pretty well without it so far). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15767 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17237] m68k aligns on 16bit boundaries.
Antoine Pitrou added the comment: We had a similar issue in the Linux kernel, where it used the lower two bits of an address for flags (urgh…) which could only be solved by using GCC’s __attribute__((__aligned__(4))) on the quantities in question, but that may or may not be the required case here, which is why I’m asking. It is not required since, as you say, m68k only requires 2-byte alignment. However, as Serhiy said, it may (or may not) be better for performance. At this point, only people with access to a m68k machine or VM (and motivated enough :-)) can do the necessary tests and propose a way forward. (but, performance notwithstanding, fixing the build should be a simple matter of silencing the assert with an appropriate #if line) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17237 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17237] m68k aligns on 16bit boundaries.
Stefan Krah added the comment: mirabilos rep...@bugs.python.org wrote: Please dont break what works. We have almost complete (about three quarters of roughly 10'000 source packages) Debian unstable working on m68k, with several versions of Python in use. Thanks! Are you saying that the complete test suite works on m68k except for this assert? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17237 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17192] libffi-3.0.12 import
Gregory P. Smith added the comment: An update to libffi is needed for all maintained versions of Python. In 2.7, we're running into the stack being misaligned in 32-bit x86 code which is something a libffi update fixes. It is a simple patch: http://patchwork.ozlabs.org/patch/58128/ which comes to the official libffi releases via https://github.com/atgreen/libffi/commit/3f5b1375ab1e2b8e3d593e21b27097a4a50f9b83#src/x86/sysv.S. The problem: without the stack being 16-byte aligned, code generated by modern compilers like recent gcc/g++ or clang assumed that the stack is 16 byte aligned and uses SSE instructions in some circumstances that require this. Without this fix, any ctypes call into such code will crash. Sure, that tiny patch could be cherry picked into our libffi, but we IMNSHO may as well just update the entire thing given that we embed a very old copy rather than use it as an external dependency. -- nosy: +benjamin.peterson, georg.brandl, gregory.p.smith, larry priority: normal - release blocker versions: +Python 2.7, Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17192 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17237] m68k aligns on 16bit boundaries.
mirabilos added the comment: @pitrou: As for performance, 2-byte and 4-byte are the same on m68k, given that they usually have RAM which doesn’t benefit from that kind of alignment, and systems that are structured accordingly. The “best” cpp define I don’t know, but my system defines __m68k__ and Alan would probably be able to say whether this is defined on ColdFire, too. @skrah: No, I specifically did not say that ☺ But it works pretty damn well. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17237 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17245] ctypes libffi needs to align the x86 stack to 16 bytes
New submission from Gregory P. Smith: The problem: without the stack being 16-byte aligned, code generated by modern compilers like recent gcc/g++ or clang assumed that the stack is 16 byte aligned and uses SSE instructions in some circumstances that require this. Without this fix, any ctypes call into such code will crash. I mentioned this in the comment on issue17192 which seeks to update our ancient copy of libffi but we may want to do this independently of that. In 2.7, we're running into the stack being misaligned in 32-bit x86 code which is something a libffi update fixes. It is a trivial patch: http://patchwork.ozlabs.org/patch/58128/ which made it into the official libffi releases in 2010 via https://github.com/atgreen/libffi/commit/3f5b1375ab1e2b8e3d593e21b27097a4a50f9b83#src/x86/sysv.S. patch against 2.7 attached. it should apply to any tree easily enough. -- assignee: gregory.p.smith files: fix_libffi_x86_stack_align.gps01.diff keywords: patch messages: 182442 nosy: benjamin.peterson, georg.brandl, gregory.p.smith, larry priority: release blocker severity: normal stage: patch review status: open title: ctypes libffi needs to align the x86 stack to 16 bytes type: crash versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4 Added file: http://bugs.python.org/file29124/fix_libffi_x86_stack_align.gps01.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17245 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17192] libffi-3.0.12 import
Benjamin Peterson added the comment: By all means, upgrade it. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17192 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17192] libffi-3.0.12 import
Gregory P. Smith added the comment: http://bugs.python.org/issue17245 filed to track the stack alignment issue. The only reason i set this as release blocker is to let a release manager decide which of these two issues to proceed with for 2.7.4 and 3.2.4 (and 3.3.1). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17192 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12014] str.format parses replacement field incorrectly
Ben Wolfson added the comment: My own preference is to let this quote from PEP 3101 dominate the behaviour: The rules for parsing an item key are very simple. If it starts with a digit, then it is treated as a number, otherwise it is used as a string. That means Petri's suggested solution (allowing any character except a closing square bracket and braces in the item key) sounds good to me. But ... that isn't what the quotation from the PEP says, since it doesn't exclude braces. I also don't really see why the PEP should be given much authority in this issue, since it pays extremely cursory attention to this part of the format. In any case, judging by the filename and description (god knows I can't remember, having written it nine months ago), strformat-no-braces.diff implements that behavior. (Oh, now I see from an earlier comment of mine that that is, in fact, what it does.) Meanwhile, it was five months ago that Eric Smith said It's on my list of things to look at. I have a project due next week, then I'll have some time. I understand that this is not the biggest deal, but the patch is also pretty compact and (I think) easily understood. Petri seemed to think it was mostly ok in May 2012, when, IIRC, several people on python-dev agreed that the current behavior should be changed. God only knows how unicode_format.h has changed in the interim. Peer review for academic papers moves substantially faster than this. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12014 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17246] cgitb fails when frame arguments are deleted (due to inspect bug I think)
New submission from Andrew Lutomirski: inspect.formatargvalues assumes (incorrectly) that every argument in args is a key in values. This isn't very hard to break -- see the attachment for a complete example. -- components: Library (Lib) files: test_cgitb.py messages: 182446 nosy: Andrew.Lutomirski priority: normal severity: normal status: open title: cgitb fails when frame arguments are deleted (due to inspect bug I think) versions: Python 2.7 Added file: http://bugs.python.org/file29125/test_cgitb.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17246 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17247] Decimal doesn't support aligned fill
New submission from Christian Heimes:
{:06}.format(1.2)
'1.2000'
{:06}.format(decimal.Decimal(1.2))
Traceback (most recent call last):
File stdin, line 1, in module
ValueError: invalid format string
--
assignee: skrah
messages: 182447
nosy: christian.heimes, skrah
priority: normal
severity: normal
status: open
title: Decimal doesn't support aligned fill
type: behavior
versions: Python 3.3, Python 3.4
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17247
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17247] Decimal doesn't support aligned fill
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti, mark.dickinson stage: - needs patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17247 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17192] libffi-3.0.12 import
Matthias Klose added the comment: before the updates, ... there seem to be two test failures on sparc solaris. the local libffi/src/sparc/v8.S change was integrated upstream, so I don't yet what could cause these failures. or did they fail before too? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17192 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17247] Decimal doesn't support aligned fill
Stefan Krah added the comment:
3.2 has a better error message:
{:06}.format(Decimal(1.2))
Traceback (most recent call last):
File stdin, line 1, in module
File /usr/lib/python3.2/decimal.py, line 3632, in __format__
spec = _parse_format_specifier(specifier, _localeconv=_localeconv)
File /usr/lib/python3.2/decimal.py, line 5600, in _parse_format_specifier
format specifier: + format_spec)
ValueError: Alignment conflicts with '0' in format specifier: 06
That's because '0' already has a special meaning:
Preceding the width field by a zero ('0') character enables sign-aware
zero-padding for numeric types. This is equivalent to a fill character of '0'
with an alignment type of '='.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17247
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17247] Decimal doesn't support aligned fill
Christian Heimes added the comment: The output is from Python 3.3. Why has Python 3.3 a less informative error message than 3.2? I also wonder why it works with floats if it has a special meaning? Either float or Decimal is broken. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17247 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
