[issue3710] Reference leak in thread._local

Changes by Ray.Allen : -- nosy: +ysj.ray ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/

[issue11209] Example for itertools.count is misleading

Raymond Hettinger added the comment: Fixed in 2.7 and 3.1. Was already fixed in 3.2. Thanks for the report. -- nosy: +rhettinger resolution: -> fixed status: open -> closed ___ Python tracker

[issue11209] Example for itertools.count is misleading

Alex added the comment: Patch for 2.7. -- keywords: +patch nosy: +alex Added file: http://bugs.python.org/file20758/python-11209.diff ___ Python tracker ___

[issue11209] Example for itertools.count is misleading

New submission from Johannes Ammon : The example code for itertools.count (http://docs.python.org/library/itertools.html#itertools.count) says # count(2.5, 0.5) -> 3.5 3.0 4.5 ... I think that should read # count(2.5, 0.5) -> 2.5 3.0 3.5 ... -- assignee: docs@python componen

[issue1635741] Interpreter seems to leak references after finalization

Changes by Ray.Allen : -- nosy: +ysj.ray ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue9523] Improve dbm modules

Changes by Ray.Allen : Removed file: http://bugs.python.org/file20726/issue_9523.diff ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue9523] Improve dbm modules

Changes by Ray.Allen : Removed file: http://bugs.python.org/file19987/issue_9523.diff ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue9523] Improve dbm modules

Changes by Ray.Allen : Removed file: http://bugs.python.org/file18402/issue8634.diff ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue7330] PyUnicode_FromFormat segfault

Changes by Ray.Allen : Removed file: http://bugs.python.org/file20731/issue_7330.diff ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue7330] PyUnicode_FromFormat segfault

Changes by Ray.Allen : Removed file: http://bugs.python.org/file19132/issue_7330.diff ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue7330] PyUnicode_FromFormat segfault

Changes by Ray.Allen : Removed file: http://bugs.python.org/file18305/issue_7330.diff ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue11207] Pythong seg fault with PIL/numpy

Antoine Pitrou added the comment: Judging from the traceback, you should probably report that issue to numpy instead. -- nosy: +pitrou resolution: -> invalid status: open -> pending ___ Python tracker __

[issue11207] Pythong seg fault with PIL/numpy

David Knapp added the comment: Sorry I'm not all that experienced with gdb. Let me know if there's more to get. (gdb) bt #0 _unaligned_strided_byte_copy (dst=0xcb9623 "\366\377\177", outstrides=1, src= 0x73503da5 , instrides=4969607, N=1, elsize=) at /usr/include/bits/string3

[issue11205] Evaluation order of dictionary display is different from reference manual.

Raymond Hettinger added the comment: How much to change and how far to backport may make for a good python-dev discussion. ISTM that changing generated code goes hand-in-hand with changing opcode semantics (as long as the magic number gets bumped). OTOH, none of this may be worth backport

[issue11208] example misprint in documentation whatsnew/3.2

New submission from July Tikhonov : >>> list(accumulate(8, 2, 50)) fails. Correct version is >>> list(accumulate([8, 2, 50])) -- assignee: docs@python components: Documentation files: whatsnew.3.2.accumulate.example.diff keywords: patch messages: 128529 nosy: docs@python, july priority

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Antoine Pitrou added the comment: > I'm still not comfortable with a convention that relies on *clients* > of the PEP 3118 API not mucking with the internals of the Py_buffer > struct. Which clients? Those who export the buffer, or those who consume it? > I'm *much* happier with the rule based

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Nick Coghlan added the comment: I should note that the idea of using a Py_buffer's "internal" field as the unique ID rather than the Py_buffer's address does have some merit, but I still overall prefer a design that places fewer constraints on API consumers. -- __

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Nick Coghlan added the comment: As far as the question of re-exporting the underlying view or not goes, I agree having "memoryview(a)" potentially refer to different underlying memory from "a" itself (because the source object has changed since the first view was exported) is a recipe for con

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Nick Coghlan added the comment: I'm still not comfortable with a convention that relies on *clients* of the PEP 3118 API not mucking with the internals of the Py_buffer struct. I'm *much* happier with the rule based on malloc/free semantics where the *pointer* passed to PyObject_GetBuffer mus

[issue11207] Pythong seg fault with PIL/numpy

Brett Cannon added the comment: Can you give a longer backtrace? Since that failure is happening in a system library we need to know where the segfault first occurs in either PIL, numpy, or CPython. And have you tried this in Python 2.7? -- nosy: +brett.cannon status: open -> pending

[issue11207] Pythong seg fault with PIL/numpy

New submission from David Knapp : Python had a seg fault with the following simple code. >>> import PIL.Image as Img >>> import numpy as np >>> i = Img.open('/home/falmarri/Dropbox/obey.jpg') >>> n = np.array(bytearray(i.tostring()),dtype=np.uint16) zsh: segmentation fault python Running it un

[issue11205] Evaluation order of dictionary display is different from reference manual.

Skip Montanaro added the comment: > To avoid introducing a ROT_TWO, the store STORE_MAP and MAP_ADD > opcodes need minor modifications (just switch the u and w variable > assignments). Either of which would not be possible in anything other that 3.3 or later, right? -- __

[issue11205] Evaluation order of dictionary display is different from reference manual.

Raymond Hettinger added the comment: takayuki, a special thanks to you for submitting such a well-researched bug report :-) -- ___ Python tracker ___ __

[issue11205] Evaluation order of dictionary display is different from reference manual.

Raymond Hettinger added the comment: If only a test had been checked-in eight years ago ... It looks like a number of things have to be changed in order to bring behavior back to what the docs promise. Dict literals and dict comprehensions need to be fixed in both the compile.py and compile

[issue11149] [PATCH] Configure should enable -fwrapv for clang

Ismail Donmez added the comment: @Antoine Pitrou , that is tracked by http://bugs.python.org/issue1621 -- ___ Python tracker ___ ___

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Antoine Pitrou added the comment: That said: > Having the memoryview "own" the exported buffer would be a simple > solution to the above issue. If you can implement that without exhibing the issues we discussed above (e.g. O(N) memory consumption when doing repetitive slicing), then why not.

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Antoine Pitrou added the comment: > Problems remain. Suppose `bf_getbuffer` for memoryview is implemented > so that it returns a view exported by the original object (and not the > memoryview). Consider an example: > > >>> obj = PictureSet() # exposes a buffer, say, to "pic_1" > >

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Pauli Virtanen added the comment: Ok, here's a patch with some suggested documentation changes + the minimal changes in memoryview to make bf_releasebuffer behave as advertised. Probably shouldn't be applied as-is, though. Problems remain. Suppose `bf_getbuffer` for memoryview is implemented

[issue9298] binary email attachment issue with base64 encoding

Yves Dorfsman added the comment: encoders.py: Fixes the issue of base64'ed being > 76 chars test_email.py: -test that base64'ed binary is split into 76 chars lines -WARRNING: Changes the test for MIMEApplication.test_body: -it changes the name of the variable 'bytes' to 'bytesdata' -

[issue9298] binary email attachment issue with base64 encoding

Changes by Yves Dorfsman : Removed file: http://bugs.python.org/file20743/issue9298.patch ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue9298] binary email attachment issue with base64 encoding

Changes by Yves Dorfsman : Removed file: http://bugs.python.org/file20742/issue9298-test.py ___ Python tracker ___ ___ Python-bugs-list mailing

[issue1011113] Make “install” find the build_base directory

Changes by Alexis Metaireau : -- nosy: +alexis ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue1635363] Add command line help to windows unistall binary

Changes by Alexis Metaireau : -- nosy: +alexis ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Antoine Pitrou added the comment: > - For each buffer yielded by `bf_getbuffer`, `bf_releasebuffer` > is called exactly once. > > Each `bf_releasebuffer` call is guaranteed to get the same > view->internal pointer as filled in previously by the > corresponding `bf_getbuffer`. > > All

[issue1092365] Distutils needs a way *not* to install files

Changes by Alexis Metaireau : -- nosy: +alexis ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue1294032] Distutils writes keywords comma-separated

Changes by Alexis Metaireau : -- nosy: +alexis ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue1597850] Cross compiling patches for MINGW

Changes by Alexis Metaireau : -- nosy: +alexis ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue1083299] Distutils doesn't pick up all the files it should.

Changes by Éric Araujo : -- components: +Distutils2 nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue1083299] Distutils doesn't pick up all the files it should.

Changes by Alexis Metaireau : -- components: -Distutils2 nosy: +alexis ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue901727] extra_path kwarg to setup() undocumented

Alexis Metaireau added the comment: Still, the extra_path argument exists and can be used, it's worth to have it documented somewhere, especially if someone have done it. That's also true that apiref.rst is outdated in d2, and will need a complete reshape :) -- ___

[issue2200] find_executable fails to find .bat files on win32

Éric Araujo added the comment: Not yet. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue901727] extra_path kwarg to setup() undocumented

Éric Araujo added the comment: You shouldn’t have :) apiref.rst is very outdated in d2, because the setup function does not exist. The docs could be adjusted to document Distribution instead of setup, but we’re not even sure Distribution will stay. I think I will make a compromise here and

[issue5243] Missing dependency in distutils build

Éric Araujo added the comment: If we haven’t closed it, it’s because it has not been. -- ___ Python tracker ___ ___ Python-bugs-list m

[issue5302] Allow package_data globs match directories

Éric Araujo added the comment: Even if MANIFEST.in is gone, we still have a way to include files, so the request to allow globs to match directories still apply. -- ___ Python tracker _

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Pauli Virtanen added the comment: Ok, good, that diversion was then avoided :) *** So, am I on the right track that there would not be many objections to clarifying the docs of Py_buffer spec by stating: - For each buffer yielded by `bf_getbuffer`, `bf_releasebuffer` is called exactly

[issue7546] msvc9compiler.py: add .asm extension

Changes by Alexis Metaireau : -- nosy: +alexis ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue11205] Evaluation order of dictionary display is different from reference manual.

Changes by Antoine Pitrou : -- nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue11205] Evaluation order of dictionary display is different from reference manual.

Skip Montanaro added the comment: As Georg suggested, it is correct in 2.4, wrong in 2.5. -- ___ Python tracker ___ ___ Python-bugs-l

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Antoine Pitrou added the comment: > dup_buffer does *dst = *src, which overwrites the view.internal > pointer obtained from one GetBuffer call with a pointer obtained from > a previous one. Ah, ok, then it deserves fixing. -- ___ Python tracker

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Pauli Virtanen added the comment: [clip] > This is a different issue. It is the issue relevant for this discussion. As written in my comment: "So, `bf_releasebuffer` cannot rely on (i) the data in Py_buffer being what `bf_getbuffer` put there, and (ii) getting the same Py_buffer data only onc

[issue2200] find_executable fails to find .bat files on win32

Alexis Metaireau added the comment: Have the patch been applied ? (the state is still open since last message) -- nosy: +alexis ___ Python tracker ___ ___

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Antoine Pitrou added the comment: > > Hmm, there's a misunderstanding. bf_releasebuffer is called exactly > > once for each call to bf_getbuffer. > > Wrong: http://bugs.python.org/issue7433 This is a different issue. > static int > memory_getbuf(PyMemoryViewObject *self, Py_buffer *view, int

[issue11205] Evaluation order of dictionary display is different from reference manual.

Georg Brandl added the comment: BTW, it would be nice to know if this behavior was consistent with the docs at any time (the merge of the AST branch in 2.5 might be an obvious candidate where it was broken). Also interesting would be what other implementations of Python do. -- _

[issue6087] distutils.sysconfig.get_python_lib gives surprising result when used with a Python build

Changes by Alexis Metaireau : -- nosy: +alexis ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue901727] extra_path kwarg to setup() undocumented

Alexis Metaireau added the comment: I've applied the patch on distutils2. This can now be closed. -- nosy: +alexis ___ Python tracker ___ __

[issue11205] Evaluation order of dictionary display is different from reference manual.

R. David Murray added the comment: Interesting. I would actually have expected the observed behavior. I think of the : in a dictionary literal as an assignment. -- nosy: +r.david.murray ___ Python tracker _

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Pauli Virtanen added the comment: > Hmm, there's a misunderstanding. bf_releasebuffer is called exactly > once for each call to bf_getbuffer. Wrong: http://bugs.python.org/issue7433 static int memory_getbuf(PyMemoryViewObject *self, Py_buffer *view, int flags) { int res = 0; CHECK_RELE

[issue11205] Evaluation order of dictionary display is different from reference manual.

Skip Montanaro added the comment: 3.2 and earlier versions are all frozen, but for 3.3 it might make sense to bump the version number of the bytecode and change STORE_MAP to take the key and value in the opposite order, thus allowing to remove the ROT_TWO I had to add to make this work.

[issue5243] Missing dependency in distutils build

Alexis Metaireau added the comment: Has the patch been applied on distutils(1/2) ? -- nosy: +alexis ___ Python tracker ___ ___ Python-

[issue5302] Allow package_data globs match directories

Alexis Metaireau added the comment: The MANIFEST.in is definitely gone in distutils2. Can we close that? (don't have the rights to do so ‑ it can be handy on distutils2 bugs) -- nosy: +alexis ___ Python tracker

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Antoine Pitrou added the comment: > The problem in the current way is that the structure sent to > `bf_releasebuffer` does not contain the same data as what was filled > in by `bf_getbuffer`, and since the contents are dup-ed, > `bf_releasebuffer` is called multiple times with the same data. Hm

[issue11205] Evaluation order of dictionary display is different from reference manual.

Georg Brandl added the comment: I don't think so -- it's a very minor deviation from the spec and not a critical bug. -- ___ Python tracker ___

[issue11205] Evaluation order of dictionary display is different from reference manual.

Skip Montanaro added the comment: Georg, I think this might need to sneak into 3.2. -- nosy: +georg.brandl ___ Python tracker ___ __

[issue11205] Evaluation order of dictionary display is different from reference manual.

Skip Montanaro added the comment: Okay, this looks better. I was confusing myself with leftover .pyc files I think. Test included. -- Added file: http://bugs.python.org/file20754/compile.diff ___ Python tracker

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Pauli Virtanen added the comment: Hi, Please focus on the constraints of the consumer not mucking with the content of `Py_buffer`, and calling `bf_releasebuffer` only with data obtained from `bf_getbuffer` and only one. If we agree on this, then how to exactly to do the implementation is jus

[issue11205] Evaluation order of dictionary display is different from reference manual.

Skip Montanaro added the comment: It's not so easy as first appeared. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue11205] Evaluation order of dictionary display is different from reference manual.

Changes by Skip Montanaro : Removed file: http://bugs.python.org/file20753/compile.diff ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue11205] Evaluation order of dictionary display is different from reference manual.

Skip Montanaro added the comment: Working on a test case too. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue5231] Change format of a memoryview

Nick Coghlan added the comment: It is, but keep issue 10181 in mind (since that may lead to some restructuring of the memoryview code, potentially leading to a need to update your patch). -- ___ Python tracker ___

[issue11205] Evaluation order of dictionary display is different from reference manual.

Skip Montanaro added the comment: Here's a patch. -- keywords: +patch nosy: +skip.montanaro versions: +Python 3.1, Python 3.2, Python 3.3 Added file: http://bugs.python.org/file20753/compile.diff ___ Python tracker

[issue11205] Evaluation order of dictionary display is different from reference manual.

Changes by yeswanth : -- nosy: +swamiyeswanth ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue5231] Change format of a memoryview

Xuanji Li added the comment: Is this issue from 2 years ago still open? I checked the docs and it seems to be. If it is, I would like to work on a patch and submit it soon. -- ___ Python tracker _

[issue5231] Change format of a memoryview

Changes by Xuanji Li : -- nosy: +xuanji ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/m

[issue11206] test_readline unconditionally calls clear_history()

New submission from Georg Brandl : This function apparently is not available in all readline versions; e.g. the GNU readline 5.2 currently installed on dinsdale. This can be fixed (together with the unconditional reliance of test_distutils and test_zipfile on zlib) after 3.2 final. --

[issue11160] ZipFile.comment expects bytes

STINNER Victor added the comment: > can we use str.encode() function to convert string into bytes ? Can you try different ZIP archivers to check which encoding is expected? WinZip, WinRAR, 7-zip, "zip" command line program on Linux, etc. And do you have any reference into a ZIP documentation?

[issue11197] information leakage with SimpleHTTPServer

Georg Brandl added the comment: Lowering priority. -- priority: deferred blocker -> critical ___ Python tracker ___ ___ Python-bugs-l

[issue11205] Evaluation order of dictionary display is different from reference manual.

New submission from takayuki : Running the following code shows "2 1 4 3", but in reference manual http://docs.python.org/reference/expressions.html#expression-lists the evaluation order described as {expr1: expr2, expr3: expr4} def f(i): print i return i {f(1):f(2), f(3):f(4)} I found