[issue19509] No SSL match_hostname() in ftp, imap, nntp, pop, smtp modules

Roundup Robot added the comment: New changeset 1a945fb875bf by Christian Heimes in branch 'default': Issue 19509: Don't call match_hostname() twice in http.client. http://hg.python.org/cpython/rev/1a945fb875bf -- ___ Python tracker

[issue12837] Patch for issue #12810 removed a valid check on socket ancillary data

Charles-François Natali added the comment: I agree with Antoine. Silencing warning is fine, as long as it's not to the detriment of clarity (see Debian Openssl's vulnerability extreme example). -- ___ Python tracker

[issue16669] Docstrings for namedtuple

Terry J. Reedy added the comment: > I find the help() output way too verbose with its endless listing of all the > built-in behaviors.) Then you might agree to a patch, on a separate issue. Let's set help aside for the moment. I am familiar with running Sphinx on .rst files, but not on docstr

[issue19892] register.send_metadata fails with EOFError: EOF when reading a line

Jean Jordaan added the comment: A closer look suggests this is an issue in zest.releaser -- resolution: -> invalid status: open -> closed ___ Python tracker ___

[issue19892] register.send_metadata fails with EOFError: EOF when reading a line

New submission from Jean Jordaan: On Ubuntu 12.04, using https://pypi.python.org/pypi/zest.releaser ./bin/release [...] INFO: Running: /.../bin/python setup.py register sdist --formats=zip upload Showing first few lines... running register running egg_info writing requirements to Products.CMFPlo

[issue19683] test_minidom has many empty tests

Julian Gindi added the comment: I agree that they should be implemented. I'll fill them in and submit a patch in a day or so. -- nosy: +Julian.Gindi ___ Python tracker ___ _

[issue19891] Exiting Python REPL prompt with user without home directory throws error in atexit._run_exitfuncs

New submission from Vajrasky Kok: $ sudo adduser --no-create-home cutecat Adding user `cutecat' ... Adding new group `cutecat' (1007) ... Adding new user `cutecat' (1005) with group `cutecat' ... Not creating home directory `/home/cutecat'. Enter new UNIX password: Retype new UNIX password: pas

[issue19776] Provide expanduser() on Path objects

Vajrasky Kok added the comment: Documentation, please (Doc/library/pathlib.rst)! This is the docstring of Path.cwd. """Return a new path pointing to the current working directory (as returned by os.getcwd()). """ This is the docstring of Path.expanduser. """ Return a new path with expanded ~ a

[issue16669] Docstrings for namedtuple

Guido van Rossum added the comment: On Wed, Dec 4, 2013 at 5:40 PM, Terry J. Reedy wrote: > 1. I posted on SO the simple Py 3 solution that replaces the previously > posted wrapper solutions needed for Py 2. Thanks, that will give people some pointers for Python 3. We need folks to upvote it.

[issue19775] Provide samefile() on Path objects

Changes by Vajrasky Kok : Added file: http://bugs.python.org/file32979/pathlib_samefile_v3.patch ___ Python tracker ___ ___ Python-bugs-list m

[issue19775] Provide samefile() on Path objects

Changes by Vajrasky Kok : Removed file: http://bugs.python.org/file32978/pathlib_samefile_v3.patch ___ Python tracker ___ ___ Python-bugs-list

[issue19775] Provide samefile() on Path objects

Changes by Vajrasky Kok : Added file: http://bugs.python.org/file32978/pathlib_samefile_v3.patch ___ Python tracker ___ ___ Python-bugs-list m

[issue19775] Provide samefile() on Path objects

Changes by Vajrasky Kok : Removed file: http://bugs.python.org/file32977/pathlib_samefile_v3.patch ___ Python tracker ___ ___ Python-bugs-list

[issue19775] Provide samefile() on Path objects

Vajrasky Kok added the comment: Thanks for the review! Attached the patch addressing the request by Antoine. -- Added file: http://bugs.python.org/file32977/pathlib_samefile_v3.patch ___ Python tracker ___

[issue19888] type.__new__() name argument is ignored

Changes by Benjamin Peterson : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue16669] Docstrings for namedtuple

Terry J. Reedy added the comment: Serhiy: I am not familiar with C PyStructSequence and how an instance of one appears in Python code. I agree that more methods should have docstrings. Guido: 1. I posted on SO the simple Py 3 solution that replaces the previously posted wrapper solutions neede

[issue12837] Patch for issue #12810 removed a valid check on socket ancillary data

Antoine Pitrou added the comment: Is there any point in littering the source code to avoid platform-specific warnings? The difference is probably that some fields are defined unsigned on OS X while they're signed on other platforms. (also, your patch has lots of unrelated changes) --

[issue19885] lzma segfault when __init__ with non-existent file after executing the constructor (Python 2.7)

Vajrasky Kok added the comment: Wait, you're right. I have not been able to reproduce this under Python downloaded from Python.org. [sky@localhost cpython2.7]$ ./python Python 2.7.6+ (2.7:ae9fb85ab4e0, Dec 5 2013, 08:24:11) [GCC 4.7.2 20121109 (Red Hat 4.7.2-8)] on linux2 Type "help", "copyri

[issue19888] type.__new__() name argument is ignored

Antoine Pitrou added the comment: (you can open a new issue for the __name__ / __qualname__ discrepancy, though) -- ___ Python tracker ___ ___

[issue19888] type.__new__() name argument is ignored

Antoine Pitrou added the comment: Barry: that's because __name__ is 'foo' while __qualname__ is 'Obj'. I'm gonna close the bug, since it's invalid. -- nosy: +pitrou resolution: -> invalid ___ Python tracker _

[issue19888] type.__new__() name argument is ignored

Changes by Antoine Pitrou : -- versions: +Python 2.7, Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue19889] Revision information missing in Python 2.6.9

Barry A. Warsaw added the comment: I think this is due to the switch from Subversion to Mercurial, which if I'm reading PEP 385 and remembering correctly, happened about the time of Python 2.6.7. IIRC, we released that source tarball from Subversion so you're seeing svn build number. When we

[issue19775] Provide samefile() on Path objects

Antoine Pitrou added the comment: Thanks for the patch! Some comments: 1. It should path objects as well as str objects. 2. I don't think you have to call resolve() here. 3. you should probably test what happens when one of the files doesn't exist 4. you need to update the documentation too ---

[issue19887] Path.resolve() ENAMETOOLONG on pathologic symlinks

Antoine Pitrou added the comment: This is https://bitbucket.org/pitrou/pathlib/issue/9/pathresolve-fails-on-complex-symlinks As noted there: """It's a ENAMETOOLONG error when calling readlink(), because there are many "." components. This is really an edge case caused by the specific test set

[issue19890] Typo in multiprocessing docs

New submission from Antony Lee: The docs for multiprocessing refer to BaseProxy._callMethod() while it should be _callmethod. -- assignee: docs@python components: Documentation messages: 205261 nosy: Antony.Lee, docs@python priority: normal severity: normal status: open title: Typo in m

[issue19888] type.__new__() name argument is ignored

Changes by Barry A. Warsaw : -- versions: +Python 3.3, Python 3.4 -Python 2.7, Python 3.2 ___ Python tracker ___ ___ Python-bugs-list

[issue19888] type.__new__() name argument is ignored

Barry A. Warsaw added the comment: At best, this is an undocumented (afaict) change in behavior in 3.3. Let's boil it down: -snip snip- class Type(type): def __new__(mcls, name, bases, namespace): return super().__new__(mcls, 'foo', bases, namespace) class Obj(metaclass=Ty

[issue19888] type.__new__() name argument is ignored

Changes by Barry A. Warsaw : -- resolution: invalid -> status: closed -> open ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue19888] type.__new__() name argument is ignored

Changes by Barry A. Warsaw : -- title: possible memory corruption caused by for-loop iteration over namespace.items() in a metaclass defining __new__ -> type.__new__() name argument is ignored ___ Python tracker

[issue19889] Revision information missing in Python 2.6.9

Changes by Ned Deily : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/

[issue19866] tests aifc, sunau and wave failures on a fresh Win64 installation

Francisco Martín Brugué added the comment: On 12/03/2013 07:21 PM, Zachary Ware wrote: > > Zachary Ware added the comment: > > Francis, would you like to work on a patch for this? The change should go in > Tools/msi/msi.py, if I'm not mistaken. > > -- > > ___

[issue19839] bz2: regression wrt supporting files with trailing garbage after EOF

Roundup Robot added the comment: New changeset c5349a560703 by Nadeem Vawda in branch '3.3': #19839: Fix regression in bz2 module's handling of non-bzip2 data at EOF. http://hg.python.org/cpython/rev/c5349a560703 New changeset bec2033ee2ec by Nadeem Vawda in branch '3.3': #19839: Fix lzma module

[issue19888] possible memory corruption caused by for-loop iteration over namespace.items() in a metaclass defining __new__

Barry A. Warsaw added the comment: D'oh! Should have looked closer. ;) -- ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue19888] possible memory corruption caused by for-loop iteration over namespace.items() in a metaclass defining __new__

Changes by Zygmunt Krynicki : -- resolution: -> invalid status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue19889] Revision information missing in Python 2.6.9

New submission from Marc-Andre Lemburg: Not sure whether this can be considered a bug, but Python 2.6.7 for example showed the build revision in the sys.version: >>> sys.version '2.6.7 (r267:88850, Feb 9 2012, 18:56:05) \n[GCC 4.5.0 20100604 [gcc-4_5-branch revision 160292]]' whereas Python

[issue19888] possible memory corruption caused by for-loop iteration over namespace.items() in a metaclass defining __new__

Zygmunt Krynicki added the comment: This is not a bug, name spills out of for ... loop and then gets passed to __new__ -- ___ Python tracker ___

[issue19888] possible memory corruption caused by for-loop iteration over namespace.items() in a metaclass defining __new__

Zygmunt Krynicki added the comment: Experimenting with a few modifications lead to the following observations: 1) objects with short names (defined inside the Obj class) tend to be ignored and don't trigger the bug 2) Longer names tend to trigger the bug, ordering is not deterministic 3) Callin

[issue19888] possible memory corruption caused by for-loop iteration over namespace.items() in a metaclass defining __new__

Zygmunt Krynicki added the comment: 2.7 test program -- Added file: http://bugs.python.org/file32976/issue-19888.py27.py ___ Python tracker ___ __

[issue19888] possible memory corruption caused by for-loop iteration over namespace.items() in a metaclass defining __new__

Barry A. Warsaw added the comment: Also seems to be triggered on 2.7 (with appropriate syntax adjustments in bug.py) -- versions: +Python 2.7 ___ Python tracker ___

[issue19888] possible memory corruption caused by for-loop iteration over namespace.items() in a metaclass defining __new__

Barry A. Warsaw added the comment: Note that just iterating over namespace doesn't trigger the problem, e.g. instead of for name, value in namespace.items(): pass using list(namespace.items()) seems to work. -- ___ Python tracker

[issue19888] possible memory corruption caused by for-loop iteration over namespace.items() in a metaclass defining __new__

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue19888] possible memory corruption caused by for-loop iteration over namespace.items() in a metaclass defining __new__

New submission from Zygmunt Krynicki: It seems that a particular code sequence causes memory corruption (but not a crash so far) in the interpreter. I've attached a test case that fails assertion on python3.2 (tested on current amd64 12.04 builds) and works on python3.3 (tested on current amd6

[issue16669] Docstrings for namedtuple

Guido van Rossum added the comment: I don't know if it's worth reopening this, but I had a need for generating docs including attribute docstrings for a namedtuple class using Sphinx, and I noticed a few things... (1) Regarding there not being demand: There's a StackOverflow question for this

[issue19859] functools.lru_cache keeps objects alive forever

Raymond Hettinger added the comment: I'm not in favor of filling the docs with warnings like this. It tends to make everything sound dangerous even when the tools are doing exactly what they are supposed to do. Every container (except for the weakref containers) keeps their references alive.

[issue19871] json module won't parse a float that starts with a decimal point

Serhiy Storchaka added the comment: There are too many cases where json and Python syntax differ. Final comma("[1, 2,]"), non-string keys ({1: 2}), tuples ("(1, 2)"), leading zeros ("0001"), hexadecimal integers ("0xaf"), escapes of astral characters('"\U0001d504"'), single quotes ("'spam'"),

[issue19871] json module won't parse a float that starts with a decimal point

Tim Peters added the comment: We should adhere to the json spec, but there's no harm (and some real good!) in the docs pointing out notable cases where json and Python syntax differ. -- nosy: +tim.peters ___ Python tracker

[issue19887] Path.resolve() fails on deep symlinks

New submission from Serhiy Storchaka: Here is a script which success with os.path.realpath(), but fails with pathlib.Path.resolve(). The `readlink -f` also success with these examples. -- components: Library (Lib) files: pathlib_resolve_test.py messages: 205245 nosy: pitrou, serhiy.stor

[issue19871] json module won't parse a float that starts with a decimal point

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue19882] Closing a socket when makefile() is used

Roundup Robot added the comment: New changeset e10bb7c1b8f8 by Antoine Pitrou in branch '3.3': Issue #19882: tweak docs for socket.close() http://hg.python.org/cpython/rev/e10bb7c1b8f8 -- nosy: +python-dev ___ Python tracker

[issue19882] Closing a socket when makefile() is used

Antoine Pitrou added the comment: Fixed, thanks! -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___

[issue19871] json module won't parse a float that starts with a decimal point

Mark Dickinson added the comment: > Oddly, with all of the strictness in JSON, the exponent-marker "e" > can be upper- or lower-case I'd guess that the aim is that common floating-point output formats from a variety of languages are valid JSON. That would also explain why both '+' and '-' are

[issue19509] No SSL match_hostname() in ftp, imap, nntp, pop, smtp modules

Roundup Robot added the comment: New changeset b6fce698e467 by Christian Heimes in branch 'default': Issue #19509: Don't close the socket in do_handshake() when hostname verification fails. http://hg.python.org/cpython/rev/b6fce698e467 -- ___ Python

[issue19882] Closing a socket when makefile() is used

Antoine Pitrou added the comment: Your observations are right, indeed. I'll make the doc changes. -- nosy: +pitrou stage: -> patch review versions: +Python 2.7 ___ Python tracker __

[issue19886] Better estimated memory requirements for bigmem tests

Serhiy Storchaka added the comment: These are experimental values. I hacked tests and ran them with less sizes (using `ulimit -v` to hard limit memory size). And then I had approximated measured values. On Windows values can be larger (due different memory management). -- ___

[issue19886] Better estimated memory requirements for bigmem tests

Antoine Pitrou added the comment: Why did you compute those estimates? When coming up with factors such as 3.3 or 3.57 (!), it would be nice to add a comment to explain the reasoning. (otherwise, thanks a lot for doing this) -- ___ Python tracker <

[issue19881] Fix bigmem pickle tests

Serhiy Storchaka added the comment: Patch about bigmem limits was moved to issue19886. -- ___ Python tracker ___ ___ Python-bugs-list

[issue19886] Better estimated memory requirements for bigmem tests

New submission from Serhiy Storchaka: Some bigmem tests actually consume much more memory than declare. This can cause swapping and too long time of test run. Here is a patch which improves estimates. -- components: Tests files: bigmem_tests.patch keywords: patch messages: 205236 nosy:

[issue19881] Fix bigmem pickle tests

Changes by Serhiy Storchaka : Removed file: http://bugs.python.org/file32972/pickle_bigmem_limits.patch ___ Python tracker ___ ___ Python-bugs

[issue18840] Tutorial recommends pickle module without any warning of insecurity

Antoine Pitrou added the comment: Correction: you can't pickle executable code, you can pickle references to well-known objects (by name): >>> def f(): pass ... >>> pickle.dumps(f) b'\x80\x03c__main__\nf\nq\x00.' >>> pickle.dumps(f.__code__) Traceback (most recent call last): File "", line 1

[issue18840] Tutorial recommends pickle module without any warning of insecurity

Westley Martínez added the comment: Sounds good to me. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https

[issue19876] selectors (and asyncio?): document behaviour on closed files/sockets

Guido van Rossum added the comment: The more I think about this the more I believe unregister() should catch the OSError (but not the KeyError). Every unregister() implementation starts by calling super().unregister(key), which has a side effect (it removes the key from the _fd_to_key dict).

[issue19885] lzma segfault when __init__ with non-existent file after executing the constructor (Python 2.7)

Nadeem Vawda added the comment: To clarify, which version(s) does this affect? I have not been able to reproduce against 3.4, and 2.7 does not included the lzma module in the first place. -- ___ Python tracker

[issue19509] No SSL match_hostname() in ftp, imap, nntp, pop, smtp modules

Guido van Rossum added the comment: See my messages on the review. Is it absolutely necessary to close the socket when the hostname verification fails? -- ___ Python tracker __

[issue19876] selectors (and asyncio?): document behaviour on closed files/sockets

Guido van Rossum added the comment: I just ran into a live case of the platform differences here. Check out http://bugs.python.org/review/19509/ (issue 19509). Christian uploaded a patch for asyncio, and when I tested it I got a double traceback and a hang. This could have been avoided if t

[issue19885] lzma segfault when __init__ with non-existent file after executing the constructor (Python 2.7)

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue19885] lzma segfault when __init__ with non-existent file after executing the constructor (Python 2.7)

Changes by Vajrasky Kok : -- title: lzma.LZMAFile.__init__() segfault when __init__ with non-existent file after executing the constructor -> lzma segfault when __init__ with non-existent file after executing the constructor (Python 2.7) ___ Python

[issue19885] lzma.LZMAFile.__init__() segfault when __init__ with non-existent file after executing the constructor

New submission from Vajrasky Kok: [sky@localhost cutecat]$ cat /tmp/lzma_segfault.py import lzma file = lzma.LZMAFile("/tmp/file.lzma", "w") file.write(b"") file.close() with lzma.LZMAFile("/tmp/file.lzma", "w") as f: f.__init__("non-existent") [sky@localhost cutecat]$ python /tmp/lzma_s

[issue19884] Importing readline produces erroneous output

Vajrasky Kok added the comment: Reproducible under Fedora 18. $ ./python -c "import readline" | hexdump -C 1b 5b 3f 31 30 33 34 68 |.[?1034h| 0008 $ TERM=dumb ./python -c "import readline" | hexdump -C -- nosy: +vajrasky

[issue19875] test_getsockaddrarg occasional failure

John W. O'Brien added the comment: For reference: CPython code comments showing that this may be an anticipated problem: http://hg.python.org/cpython/file/0830670a9d9d/Lib/test/support/__init__.py#l562 An example of another project that seems to have tackled this problem in the way neologix s

[issue7060] test_multiprocessing dictionary changed size errors and hang

Antoine Pitrou added the comment: Okay, let's say it is fixed. Adding Richard to nosy so that he can review the issue if he's interested. -- resolution: -> out of date stage: needs patch -> committed/rejected ___ Python tracker

[issue7105] weak dict iterators are fragile because of unpredictable GC runs

Antoine Pitrou added the comment: I'm ok with the backport. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue19859] functools.lru_cache keeps objects alive forever

Antoine Pitrou added the comment: Just adding a note in the documentation sounds enough. -- nosy: +pitrou ___ Python tracker ___ ___ P

[issue19881] Fix bigmem pickle tests

Antoine Pitrou added the comment: (we did have a bigmem buildbot but the bigmem tests tended to crash it, as some memory estimates are widely inaccurate) -- ___ Python tracker _

[issue19884] Importing readline produces erroneous output

Antoine Pitrou added the comment: I can't reproduce under Ubuntu 13.10. Is this Red Hat-specific? (according to Dave, """This is a readline bug; it looks like it should not emit those characters when stdout is not a tty""") -- nosy: +dmalcolm, pitrou versions: +Python 3.4

[issue19881] Fix bigmem pickle tests

Changes by Serhiy Storchaka : Added file: http://bugs.python.org/file32972/pickle_bigmem_limits.patch ___ Python tracker ___ ___ Python-bugs-l

[issue19881] Fix bigmem pickle tests

Changes by Serhiy Storchaka : Removed file: http://bugs.python.org/file32969/pickle_bigmem_limits.patch ___ Python tracker ___ ___ Python-bugs

[issue19859] functools.lru_cache keeps objects alive forever

Radomir Dopieralski added the comment: > Umm, that's part of the operational definition of a value based cache > - it needs to keep things alive, so that if a different instance shows > up with the same value, it will still get a cache hit. If it only kept the return value alive, that wouldn't b

[issue18840] Tutorial recommends pickle module without any warning of insecurity

Nick Coghlan added the comment: Since this particular tutorial section was written long before the json module was part of the standard library, I think it makes sense to switch now we have the option. pickle is definitely a useful tool, but now that JSON is available by default, it's now one

[issue19859] functools.lru_cache keeps objects alive forever

Nick Coghlan added the comment: On 4 December 2013 20:15, Radomir Dopieralski wrote: > But I think it's would be still worthwhile to add a note to the lru_cache's > documentation, saying something like: > > """ > Warning! lru_cache will keep references to all the arguments for which it > keeps

[issue19884] Importing readline produces erroneous output

New submission from Bohuslav "Slavek" Kabrda: A simple reproducer: python -c 'import readline' | xxd 000: 1b5b 3f31 3033 3468 .[?1034h This was reported at [1] and originally at [2]. The readline maintainer suggests [3] using: rl_variable_bind ("enable-meta-key", "off

[issue19787] tracemalloc: set_reentrant() should not have to call PyThread_delete_key()

Kristján Valur Jónsson added the comment: +1 Why don't we just fix this and see where the chips fall? -- ___ Python tracker ___ ___ Py

[issue13797] Allow objects implemented in pure Python to export PEP 3118 buffers

Changes by Martin Panter : -- nosy: +vadmium ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue7105] weak dict iterators are fragile because of unpredictable GC runs

Kristján Valur Jónsson added the comment: That's the spirit, Guido :) I just think people are being extra careful after the "regression" introduced in 2.7.5. However, IMHO we must never let the odd mistake scare us from making necessary moves. Unless Antoine explicitly objects, I think I'll sub

[issue19687] Fixes for elementtree integer overflow

Serhiy Storchaka added the comment: See also *first* patch in issue16986. -- nosy: +eli.bendersky, scoder, serhiy.storchaka ___ Python tracker ___ ___

[issue19883] Integer overflow in zipimport.c

Changes by Serhiy Storchaka : -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue19859] functools.lru_cache keeps objects alive forever

Radomir Dopieralski added the comment: Thank you for your attention. I'm actually quite happy with the solution we have, it works well. That's actually I thought that it may be worthwhile to try and push it upstream to Python. I can totally understand why you don't want to add too much to the

[issue19687] Fixes for elementtree integer overflow

Christian Heimes added the comment: New patch with fixes for element_ass_subscr(). -- Added file: http://bugs.python.org/file32971/elementtree_overflow2.patch ___ Python tracker

[issue19883] Integer overflow in zipimport.c

STINNER Victor added the comment: See also zipfile.py which is probably more correct than zipimport.c: zipfile uses for example "L" format for struct.unpack (*unsigned* long) to decode header fields. -- ___ Python tracker

[issue19883] Integer overflow in zipimport.c

STINNER Victor added the comment: read_directory() uses fseek() and ftell() which don't support offset larger than LONG_MAX (2 GB on 32-bit system). I don't know if it's an issue. What happens if the file is longer? "header_offset += arc_offset;" can overflow or not? This instuction looks wei

[issue19883] overflow in zipexport.c

New submission from Christian Heimes: MSVC complains about "conversion from 'Py_ssize_t' to 'long', possible loss of data" in zipimport.c. header_offset is a Py_ssize_t but fseek() only takes a long. On 64bit Windows Py_ssize_t is a 64bit data type but long is still a 32bit data type. It's sa

[issue19859] functools.lru_cache keeps objects alive forever

Raymond Hettinger added the comment: > Limiting the cache size is also not a solution in the > practical example with request that I linked to in the > previous comment, because we can't know in advance how > many times per request the function is going to be called, > picking an arbitrary numb

[issue19881] Fix bigmem pickle tests

Serhiy Storchaka added the comment: Here is a patch with new bigmem limits. Currently bigmem tests consumes much more memory than they declare. This can cause memory swapping and too long time of test's running. -- Added file: http://bugs.python.org/file32969/pickle_bigmem_limits.patch

[issue18840] Tutorial recommends pickle module without any warning of insecurity

Changes by Ezio Melotti : -- nosy: +ezio.melotti stage: needs patch -> patch review type: -> enhancement ___ Python tracker ___ ___ P

[issue19881] Fix bigmem pickle tests

Serhiy Storchaka added the comment: Alexandre, if you have enough memory, could you please check that memory requirements for bigmem tests are correct? -- ___ Python tracker ___

[issue12837] Patch for issue #12810 removed a valid check on socket ancillary data

Christian Heimes added the comment: I'd like to see the warning silenced before 3.4 gets released, too. How about a check like (Py_ssize_t)msg->msg_controllen > 0xL instead? I'd also be fine with pragmas. -- nosy: +christian.heimes versions: +Python 3.4 ___