[issue26106] Move licences to literal blocks

Roundup Robot added the comment: New changeset a04d9589e2c4 by Victor Stinner in branch '3.5': Issue #26106: doc: Move text of licenses to parsed literal block https://hg.python.org/cpython/rev/a04d9589e2c4 -- nosy: +python-dev ___ Python tracker

[issue22872] multiprocessing.Queue raises AssertionError

Berker Peksag added the comment: See issue 5001 for more general cleanup in multiprocessing. > [...] (2) altering the behavior in a new release version (perhaps 3.6 when it > comes) and documenting that change appropriately there. +1. We can also document AssertionError in older Python version

[issue26171] heap overflow in zipimporter module

Roundup Robot added the comment: New changeset 01ddd608b85c by Benjamin Peterson in branch '3.4': prevent buffer overflow in get_data (closes #26171) https://hg.python.org/cpython/rev/01ddd608b85c New changeset 985fc64c60d6 by Benjamin Peterson in branch '2.7': prevent buffer overflow in get_dat

[issue26172] iBook can't open ePub

Roundup Robot added the comment: New changeset 562179b7912f by Benjamin Peterson in branch '3.4': remove script from epub (closes #26172) https://hg.python.org/cpython/rev/562179b7912f New changeset 56e68089ad65 by Benjamin Peterson in branch '3.5': merge 3.4 (#26172) https://hg.python.org/cpyth

[issue26172] iBook can't open ePub

New submission from INADA Naoki: Script cannot run in iBook is included in ePub. Attached patch resolves the issue. -- assignee: docs@python components: Documentation files: epub.patch keywords: patch messages: 258734 nosy: docs@python, naoki priority: normal severity: normal status: ope

[issue26171] heap overflow in zipimporter module

New submission from Insu Yun: in zipimport.c 1116 bytes_size = compress == 0 ? data_size : data_size + 1; 1117 if (bytes_size == 0) 1118 bytes_size++; 1119 raw_data = PyBytes_FromStringAndSize((char *)NULL, bytes_size); If compress != 0, then bytes_size = data_size +

[issue26169] Pasting 900000 chars into a tk Entry widget fails

New submission from Terry J. Reedy: '\x41' == 'A'. I don't know what 'BOF' has to do with the character 'A' or a string of them. A python or pythonw process 'hanging' does not itself mean that there is a buffer overflow, though I can understand why you suspect it. Python itself is pretty mu

[issue26167] Improve copy.copy speed for built-in types (list/set/dict)

Josh Rosenberg added the comment: Good point. Though I don't see any attached patches... -- ___ Python tracker ___ ___ Python-bugs-lis

[issue22490] Using realpath for __PYVENV_LAUNCHER__ makes Homebrew installs fragile

Jason R. Coombs added the comment: I believe this behavior (presence of the __PYVENV_LAUNCHER__ and inheritance in child processes) continues to cause problems. See https://github.com/pypa/virtualenv/issues/845 for a simple reproducing of the issue, even on pip 6+. -- nosy: +jason.coo

[issue25704] Update the devguide to 3.5

Berker Peksag added the comment: Thanks, Stéphane! Ned applied most of your patch in f53eac8da0b8. I left "sudo apt-get build-dep python3.4" as is since python3.5 is not available in the latest LTS release of Ubuntu. -- resolution: -> fixed stage: patch review -> resolved status: open

[issue25704] Update the devguide to 3.5

Roundup Robot added the comment: New changeset 32545ee8d673 by Berker Peksag in branch 'default': Issue #25704: Update Python version to 3.5 where appropriate https://hg.python.org/devguide/rev/32545ee8d673 -- nosy: +python-dev ___ Python tracker

[issue26170] pip Crash on Unpacking in get_platform() line 119

Changes by Berker Peksag : -- stage: -> resolved type: crash -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue26170] pip Crash on Unpacking in get_platform() line 119

Donald Stufft added the comment: Hey, This is actually a bug with pip not with CPython and is being tracked by https://github.com/pypa/pip/issues/3408. It's fixed in pip's repository and we'll soon have an 8.0.1 release out to fix it. -- nosy: +dstufft resolution: -> third party stat

[issue26170] pip Crash on Unpacking in get_platform() line 119

New submission from Vinyl Darkscratch-Kazotetsu: Since upgrading to pip 8.0, I get a crash whenever I try to run it. It fails to unpack to major, minor, and micro for the release, saying there's only two values. Traceback (most recent call last): File "/Library/Frameworks/Python.framework/V

[issue25843] code_richcompare() don't use constant type when comparing code constants

STINNER Victor added the comment: Patch version 4: Fix _PyCode_ConstantKey: * always return a tuple * create a frozenset/set if input is a set/frozenset, items are unordered * enhance unit tests: compare values using repr() to compare value + type at once * fix reference leak Other minor chan

[issue25843] code_richcompare() don't use constant type when comparing code constants

STINNER Victor added the comment: And sorry, I missed your comments, it looks like some emails were seen as spam :-/ -- ___ Python tracker ___ __

[issue26169] Buffer OverFlow in IDLE 2.7.11

Changes by Soufiane BOUSSALI : -- title: Buffer OverFlow in IDLE -> Buffer OverFlow in IDLE 2.7.11 ___ Python tracker ___ ___ Python-b

[issue25591] refactor imaplib tests

Maciej Szulik added the comment: David I think I've re-implemented, using the new style, all the methods from ThreadedNetworkedTests and ThreadedNetworkedTestsSSL, the new classes are NewIMAPTests and NewIMAPSSLTests accordingly. -- stage: -> patch review Added file: http://bugs.pytho

[issue26152] A non-breaking space in a source

Andrew Barnert added the comment: > Assuming Andrew is correct, it sounds like the tokenizer is treating the NBSP > and the “2” as part of the same token, because NBSP is non-ASCII. It's more complicated than that. When you get an invalid character, it splits the token up. So, in this case, yo

[issue24520] Stop using deprecated floating-point environment functions on FreeBSD

STINNER Victor added the comment: "I expect the man page mentions it because it is mentioned in the standard. In the bugs section it does say the pragma is unimplemented." Ah ah, funnny. Sorry, I was confused by the manual page. I pushed your patch to Python 2.7, 3.5 and default (3.6) branches

[issue24520] Stop using deprecated floating-point environment functions on FreeBSD

Roundup Robot added the comment: New changeset 76f35f35be50 by Victor Stinner in branch '3.5': Replace fpgetmask() with fedisableexcept() https://hg.python.org/cpython/rev/76f35f35be50 New changeset 6134d9ecab60 by Victor Stinner in branch 'default': Merge 3.5 (issue #24520) https://hg.python.or

[issue26169] Buffer OverFlow in IDLE

Changes by SilentGhost : -- nosy: +kbk, roger.serwy, terry.reedy title: Buffer OverFlow -> Buffer OverFlow in IDLE ___ Python tracker ___

[issue26165] devguide: table summarizing status of Python branches

STINNER Victor added the comment: > If possible, add Months or Quarter (Q1-4) for the EoL's, if those are > defined, would be great. I added the estimated *day* of the end-of-line. But the release manager is free to adjust it. > We @ FreeBSD/Python would like to proactively (as early as possi

[issue26165] devguide: table summarizing status of Python branches

Roundup Robot added the comment: New changeset 75b95ada261f by Victor Stinner in branch 'default': Add a table "Status of Python branches" to the front page https://hg.python.org/devguide/rev/75b95ada261f -- nosy: +python-dev ___ Python tracker

[issue26165] devguide: table summarizing status of Python branches

STINNER Victor added the comment: I pushed a first version of the table. It can be adjusted later if needed. -- resolution: -> fixed status: open -> closed ___ Python tracker __

[issue26169] Buffer OverFlow

Changes by Soufiane BOUSSALI : Added file: http://bugs.python.org/file41674/py2.7.11.png ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue26169] Buffer OverFlow

Changes by Soufiane BOUSSALI : -- components: IDLE files: poc.py nosy: Soufiane BOUSSALI priority: normal severity: normal status: open title: Buffer OverFlow type: crash versions: Python 2.7 Added file: http://bugs.python.org/file41673/poc.py ___ Pyt

[issue25520] unittest load_tests protocol not working as documented

Stefan Seefeld added the comment: Hi, I'm investigating more issues related to test loading, and thus I have discovered issue #16662. I have found quite a number of inconsistencies and bugs in the loading of tests. But without getting a sense of what the supposed behavior is I find it difficu

[issue26152] A non-breaking space in a source

Adam Bartoš added the comment: It could still point to the first or the last byte of the invalid token rather than to the start of the next token. Also, by the Python implementation of the tokenizer in tokenize module we get an ERRORTOKEN containing a non-breaking space followed by a number to

[issue26152] A non-breaking space in a source

Martin Panter added the comment: Assuming Andrew is correct, it sounds like the tokenizer is treating the NBSP and the “2” as part of the same token, because NBSP is non-ASCII. -- ___ Python tracker __

[issue26152] A non-breaking space in a source

Adam Bartoš added the comment: We have one particular invalid token, so why it should point to the next token rather than to the invalid one? -- ___ Python tracker ___ _

[issue26167] Improve copy.copy speed for built-in types (list/set/dict)

Serhiy Storchaka added the comment: methodcaller is not needed. We can use just list.copy etc. Proposed patch speeds up copying list, dict, set, bytearray, slice, NotImplemented. It makes deepcopying list, tuple, dict a little faster. It makes the code for copying and deepcopying using reduce

[issue26152] A non-breaking space in a source

Martin Panter added the comment: The caret always points to the end of the token, I think. -- nosy: +martin.panter ___ Python tracker ___

[issue26162] thread error

Eryk Sun added the comment: It's no surprise to see a memory error at 845 threads if you're using 32-bit Python, which is limited to 2 GiB of address space. python.exe is built with a default stack reservation of 200 bytes, so 845 threads reserve a total of about 1.58 GiB. Consider also th

[issue26168] Py_BuildValue may leak 'N' arguments on PyTuple_New failure

Changes by Josh Rosenberg : -- nosy: +josh.r ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue26168] Py_BuildValue may leak 'N' arguments on PyTuple_New failure

Changes by Serhiy Storchaka : -- nosy: +serhiy.storchaka stage: -> needs patch versions: +Python 3.5, Python 3.6 ___ Python tracker ___ _

[issue25007] Add support of copy protocol to zlib compressors and decompressors

Serhiy Storchaka added the comment: I agree with Josh. Needed __deepcopy__ and tests. And I think there may be problem with sharing a docstring (that includes a signature) between copy() and __copy__(). It is better to just add separate method that calls the implementation of copy().

[issue26168] Py_BuildValue may leak 'N' arguments on PyTuple_New failure

New submission from squidevil: Expected behavior: Calling Py_BuildValue with a 'N' argument should take ownership of the N object, and on failure (returns NULL), call Py_DECREF() on any N argument. The documentation explicitly says that this is the intended usage: "N": Same as "O", excep

[issue25843] code_richcompare() don't use constant type when comparing code constants

Serhiy Storchaka added the comment: It looks to me that the patch makes set and frozenset constants to be equal, but makes sets with different order (as {2**62, 1} and {1, 2**62}) differ. And looks you had missed my comments to previous patches. -- stage: -> patch review versions: -P

[issue26167] Improve copy.copy speed for built-in types (list/set/dict)

Changes by Josh Rosenberg : -- title: Improve copy.copy speed for built-in types -> Improve copy.copy speed for built-in types (list/set/dict) ___ Python tracker ___ ___

[issue25007] Add support of copy protocol to zlib compressors and decompressors

Josh Rosenberg added the comment: Patch looks good, but incomplete. Supporting __deepcopy__ (as a simple wrapper around __copy__ that ignores the second argument) would provide complete support. Also, should there be tests? I mean, I assume the .copy() method itself is tested, but just to det

[issue26166] zlib compressor/decompressor objects should support copy protocol

Josh Rosenberg added the comment: Oops. Sorry. I swear I searched, but I can't figure out how I missed the obvious duplicate there. -- ___ Python tracker ___ ___

[issue26167] Improve copy.copy speed for built-in types

New submission from Josh Rosenberg: copy.copy uses a relatively high overhead approach to copying list, set and dict, using: def _copy_with_constructor(x): return type(x)(x) This is despite the fact that all three types implement a .copy() method, and there is already a defined me

[issue25702] Link Time Optimizations support for GCC and CLANG

Steve Dower added the comment: MSVC has had Link-Time Code Generation for many releases, and it should have been used for all 2.7 releases (definitely used in 3.5+) to optimize references between object files. I assume this is equivalent to LTO. We currently don't use PGO in the official Windo

[issue26166] zlib compressor/decompressor objects should support copy protocol

Serhiy Storchaka added the comment: This is a duplicate of issue25007. -- nosy: +serhiy.storchaka resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Add support of copy protocol to zlib compressors and decompressors

[issue26150] SequenceMatcher's algorithm is not correct

Tim Peters added the comment: Please read the responses to this older report: http://bugs.python.org/issue25391 As they say, it's functioning as designed and documented, so this isn't "a bug". For that reason I'm closing this as "not a bug". As they also say, there are many other possible al

[issue26166] zlib compressor/decompressor objects should support copy protocol

Changes by Josh Rosenberg : -- type: -> enhancement ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue26166] zlib compressor/decompressor objects should support copy protocol

New submission from Josh Rosenberg: zlib.compressobj and zlib.decompressobj objects (actually zlib.Compress and zlib.Decompress, the other names are the function constructors I guess?) have a .copy() method, but don't implement `__copy__` or `__deepcopy__`. This leads to the mildly silly resul

[issue26165] devguide: table summarizing status of Python branches

STINNER Victor added the comment: The table is inspired by http://docs.openstack.org/releases/ which only gives the status, not the past or scheduled end-of-life date. -- ___ Python tracker ___

[issue26165] devguide: table summarizing status of Python branches

koobs added the comment: OH THANK YOU! If possible, add Months or Quarter (Q1-4) for the EoL's, if those are defined, would be great. We @ FreeBSD/Python would like to proactively (as early as possible) set DEPRECATED dates in our ports to ensure our users have ample time to upgrade to later

[issue18858] dummy_threading lacks threading.get_ident() equivalent

Changes by Brett Cannon : -- assignee: -> berker.peksag stage: patch review -> commit review ___ Python tracker ___ ___ Python-bugs-l

[issue25702] Link Time Optimizations support for GCC and CLANG

Brett Cannon added the comment: To help answer MAL's question about Windows: I know the python.org installers are **not** built with PGO, but I don't know about LTO. -- nosy: +steve.dower ___ Python tracker __

[issue26165] devguide: table summarizing status of Python branches

New submission from STINNER Victor: A frequent question is to get the status of a Python branch: is it still maintained? when does the support stop? Attached patch adds a short table giving the current status of Python branches between 2.6 and 3.6 (default). I sorted branches by their status,

[issue26165] devguide: table summarizing status of Python branches

Changes by STINNER Victor : -- nosy: +koobs, larry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue24520] Stop using deprecated floating-point environment functions on FreeBSD

Stefan Krah added the comment: Thanks, then the patch looks good to me. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue24520] Stop using deprecated floating-point environment functions on FreeBSD

Andrew Turner added the comment: I think this patch is correct. Clang, as shipped by FreeBSD, doesn't support FENV_ACCESS. It raises the following warning: fenv_test.c:2:14: warning: pragma STDC FENV_ACCESS ON is not supported, ignoring pragma [-Wunknown-pragmas] #pragma STDC FENV_ACCESS ON

[issue25687] Error during test case and tearDown

Gedai Tamás Bence added the comment: I think it's in the docs, although if you don't find it sufficient I might try to update it. `tearDown method `_ "This is called even if the test method raised an exception [...]

[issue24520] Stop using deprecated floating-point environment functions on FreeBSD

Stefan Krah added the comment: 1) Feedback whether the compiler used on FreeBSD recognizes FENV_ACCESS. 2) If not, an indication why the man page mentions it. -- ___ Python tracker

[issue24520] Stop using deprecated floating-point environment functions on FreeBSD

STINNER Victor added the comment: Andrew Turner: "Can this be applied?" koobs: "What remains to be done/identified/answers here to make progress?" *I* don't understand if replacing fpsetmask() with fedisableexcept() is enough, or if we also need to starting putting "#pragma STDC FENV_ACCESS ON

[issue8519] doc: termios and ioctl reference links

Changes by Guido van Rossum : -- nosy: -Guido.van.Rossum ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue24520] Stop using deprecated floating-point environment functions on FreeBSD

koobs added the comment: This issue is becoming increasingly important as FreeBSD 11.0-RELEASE time nears. What remains to be done/identified/answers here to make progress? -- versions: +Python 2.7, Python 3.5 ___ Python tracker

[issue25934] ICC compiler: ICC treats denormal floating point numbers as 0.0

Mark Dickinson added the comment: The dtoa.c occurrence is also straightforward to fix. It's coming from this declaration: static const double tinytens[] = { 1e-16, 1e-32, 1e-64, 1e-128, 9007199254740992.*9007199254740992.e-256}; We need to be a tiny bit careful here,

[issue4806] Function calls taking a generator as star argument can mask TypeErrors in the generator

Samuel BOVÉE added the comment: Up for this bug. I got this bug in my code and loose one hour to understand what happened. Please review Martin's patch ! -- nosy: +Samuel BOVÉE ___ Python tracker __

[issue25934] ICC compiler: ICC treats denormal floating point numbers as 0.0

Steve Dower added the comment: I'm -0 on changing the universal default (and want to call out that it's a relevant porting note for 3.6, not appropriate for 3.5), but we can presumably fix those in case someone wants to use strict for their own build. -- __

[issue25934] ICC compiler: ICC treats denormal floating point numbers as 0.0

Mark Dickinson added the comment: Thanks. The offending lines in the math module are: static const double degToRad = Py_MATH_PI / 180.0; static const double radToDeg = 180.0 / Py_MATH_PI; It would be trivial to replace these with suitable constants. --

[issue25934] ICC compiler: ICC treats denormal floating point numbers as 0.0

Zachary Ware added the comment: Ah, it's been a while since I tested that, so my reporting was inaccurate. The problem is actually that the compile fails: ..\Modules\mathmodule.c(1924): error C2099: initializer is not a constant [C:\cpython\PCbuild\pythoncore.vcxproj] ..\Modules\mathmodule.c(

[issue8604] Adding an atomic FS write API

STINNER Victor added the comment: It looks like each platform and each filesystem behave differently, with subtle differencies with different kernel versions. I'm not more sure that the Python stdlib is the best place to host an implementation of an "atomic write" API. I now suggest to create

[issue25843] lambdas on the same line may incorrectly share code objects

STINNER Victor added the comment: Let me try to explain this issue again. "f1, f2 = lambda: 1, lambda: 1.0" is compiled to two MAKE_FUNCTION instructions, MAKE_FUNCTION takes a code object as parameter (and a name). The Python compiler merges constants which are seen as "equal", with exception

[issue25843] code_richcompare() don't use constant type when comparing code constants

Changes by STINNER Victor : -- title: lambdas on the same line may incorrectly share code objects -> code_richcompare() don't use constant type when comparing code constants ___ Python tracker

[issue25702] Link Time Optimizations support for GCC and CLANG

R. David Murray added the comment: My understanding is that we (starting with Guido) have made a blanket exception for 2.7 for useful performance and build-system-only related patches. That doesn't mean *anything* can go in (the usual rules about "is this worth it/backward compatible/won't br

[issue8604] Adding an atomic FS write API

Thomas Kluyver added the comment: For reference, we added our own atomic_writing() context manager in Jupyter/IPython, after someone lost work when save failed on a full disk. We initially went for the same approach - write to a temporary file, fsync, rename over the original file - but it cau

[issue18858] dummy_threading lacks threading.get_ident() equivalent

Berker Peksag added the comment: dummy_threading.get_ident() works for me: >>> import dummy_threading as dt >>> dt.get_ident() -1 >>> import threading >>> threading.get_ident() 140498493105920 Here is a patch to compare threading and dummy_threading modules. --

[issue26152] A non-breaking space in a source

Adam Bartoš added the comment: That explains the message. But why is the caret at a wrong place? -- ___ Python tracker ___ ___ Python-

[issue25702] Link Time Optimizations support for GCC and CLANG

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

[issue26145] PEP 511: Add sys.set_code_transformers()

STINNER Victor added the comment: Note: ast.PyCF_TRANSFORMED_AST is not implemented yet. -- ___ Python tracker ___ ___ Python-bugs-lis

[issue26164] test_with_pip() of test_venv fails on Windows buildbots

Donald Stufft added the comment: Upstream issue for this is https://github.com/pypa/pip/issues/3383. -- ___ Python tracker ___ ___ Pyt

[issue21776] distutils.upload uses the wrong order of exceptions

Berker Peksag added the comment: Lib/distutils/command/upload.py has changed a bit after d86214c98a9c. Here is an updated patch. -- nosy: +berker.peksag stage: -> patch review versions: +Python 3.6 Added file: http://bugs.python.org/file41669/issue21776_v2.diff ___

[issue26164] test_with_pip() of test_venv fails on Windows buildbots

New submission from STINNER Victor: http://buildbot.python.org/all/builders/x86%20Windows7%203.5/builds/591/steps/test/logs/stdio == FAIL: test_with_pip (test.test_venv.EnsurePipTest)

[issue26163] FAIL: test_hash_effectiveness (test.test_set.TestFrozenSet)

New submission from STINNER Victor: The buildbot "x86 Ubuntu Shared 3.x" build 12691 failed, the previous builds succeeded. Changes: * f97da0952a2ebe08f2e5999c7473c776c59f3a16 (issue #25982) * 775b74e0e103f816382a0fc009b6ac51ea956750 (issue #26107) http://buildbot.python.org/all/builders/x86%2

[issue17611] Move unwinding of stack for "pseudo exceptions" from interpreter to compiler.

STINNER Victor added the comment: FYI The issue #26107 changed code.co_lnotab to support negative line number deltas. -- nosy: +haypo ___ Python tracker ___

[issue26107] PEP 511: code.co_lnotab: use signed line number delta to support moving instructions in an optimizer

STINNER Victor added the comment: I closed issues #16956 and #21385 as duplicates of this issue. -- ___ Python tracker ___ ___ Python-

[issue16956] Allow signed line number deltas in the code object's line number table

STINNER Victor added the comment: Good news: this issue has been fixed in issue #26107. -- resolution: -> fixed status: open -> closed superseder: -> PEP 511: code.co_lnotab: use signed line number delta to support moving instructions in an optimizer _

[issue21385] in debug mode, compile(ast) fails with an assertion error if an AST node has no line number information

STINNER Victor added the comment: Good news: this issue has been fixed by the commit of the issue #26107. -- resolution: -> fixed status: open -> closed superseder: -> PEP 511: code.co_lnotab: use signed line number delta to support moving instructions in an optimizer ___

[issue26107] PEP 511: code.co_lnotab: use signed line number delta to support moving instructions in an optimizer

STINNER Victor added the comment: > Nice work, my issue21385 is also related. Basically, transforming non-Python > code into Python meant that all line number information, which otherwise > would have been useful for debugging, had to be discarded, or debug builds of > Python would dump cores.

[issue26107] PEP 511: code.co_lnotab: use signed line number delta to support moving instructions in an optimizer

Roundup Robot added the comment: New changeset 775b74e0e103 by Victor Stinner in branch 'default': co_lnotab supports negative line number delta https://hg.python.org/cpython/rev/775b74e0e103 -- ___ Python tracker

[issue26162] thread error

New submission from Ali Razmjoo: Hello, I've got a problem while using threading in python 2.7.10 windows. I copied errors in here https://gist.github.com/Ali-Razmjoo/d503171d338c6381f94f with 845 threads,870 and 1000. there isn't any problem or error with 840-830 threads! -- messages

[issue1674555] sys.path in tests contains system directories

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue8519] doc: termios and ioctl reference links

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue12215] TextIOWrapper: issues with interlaced read-write

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue25982] multiprocessing docs for Namespace lacks class definition

Roundup Robot added the comment: New changeset 8d7aadd40d30 by Senthil Kumaran in branch '2.7': issue25982 - Add a class definition for managers.Namespace in the multiprocessing docs. https://hg.python.org/cpython/rev/8d7aadd40d30 -- ___ Python track

[issue25982] multiprocessing docs for Namespace lacks class definition

Senthil Kumaran added the comment: Thanks for the report. Fixed. -- assignee: davin -> orsenthil nosy: +orsenthil resolution: -> fixed stage: needs patch -> resolved status: open -> closed type: enhancement -> behavior versions: -Python 3.4 ___ Pyth

[issue25982] multiprocessing docs for Namespace lacks class definition

Roundup Robot added the comment: New changeset 32ee5d197500 by Senthil Kumaran in branch '3.5': issue25982 - Add a class definition for managers.Namespace in the multiprocessing docs. https://hg.python.org/cpython/rev/32ee5d197500 New changeset f97da0952a2e by Senthil Kumaran in branch 'default

[issue25702] Link Time Optimizations support for GCC and CLANG

Marc-Andre Lemburg added the comment: On 20.01.2016 11:38, Antoine Pitrou wrote: >> If not, then the patch would also effect the not-so-tiny fraction >> of Python users on Windows ;-) > > I don't see how enabling LTO for gcc and clang could ever affect our Windows > users ;-) You have a point

[issue26161] Use Py_uintptr_t instead of void* for atomic pointers

STINNER Victor added the comment: (Oops, I attached the wrong patch. It's now fixed.) -- Added file: http://bugs.python.org/file41668/atomic_pointer.patch ___ Python tracker ___

[issue26161] Use Py_uintptr_t instead of void* for atomic pointers

New submission from STINNER Victor: Attached patch fixes compiler warnings on atomic pointers. Python has 4 implementations of atomic types: * * GCC 4.7+ builtin atomic operations * GCC x86 and x86_64 assembler * volatile The type of atomic pointers changes depending on the implementation. At

[issue26161] Use Py_uintptr_t instead of void* for atomic pointers

Changes by STINNER Victor : Removed file: http://bugs.python.org/file41667/atomic_pointer.patch ___ Python tracker ___ ___ Python-bugs-list ma

[issue25702] Link Time Optimizations support for GCC and CLANG

Antoine Pitrou added the comment: > If not, then the patch would also effect the not-so-tiny fraction of Python users on Windows ;-) I don't see how enabling LTO for gcc and clang could ever affect our Windows users ;-) -- ___ Python tracker

[issue26160] Tutorial incorrectly claims that (explicit) relative imports don't work in the main module

Martin Panter added the comment: Yes 2.7 is open for changes to the documentation like this, as is 3.5+. It’s been a while since I looked at the tutorial. Does it even mention the “python -m” mode? I don’t think this is the right place to introduce it. Perhaps it would be okay to just say rela

[issue25702] Link Time Optimizations support for GCC and CLANG

Marc-Andre Lemburg added the comment: On 20.01.2016 09:37, Antoine Pitrou wrote: > Let me add that downstream distributors already customize compilation options > (Ubuntu's Python is compiled with both PGO and LTO enabled, AFAIR), so this > change may only really affect the tiny subset of non-W

[issue26154] Add private _PyThreadState_UncheckedGet() to get the current thread state

STINNER Victor added the comment: Function added @fijal: Sorry for the annoyance of the Python 3.5.1 regression. -- resolution: -> fixed status: open -> closed title: Add private _PyThreadState_FastGet() to get the current thread state -> Add private _PyThreadState_UncheckedGet() to g

  1   2   >