[issue33330] Better error handling in PyImport_Cleanup()

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue31493] IDLE cond context: fix code update and font update timers

Terry J. Reedy added the comment: The patch fixed immediate problem #2 above. #1 is a separate enhancement and I listed it as #4 on the new master issue #33610. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed

[issue32831] IDLE: Add docstrings and tests for codecontext

Terry J. Reedy added the comment: If you are following up with a new patch that includes code changes, make a new issue. In the opening message, please briefly list the mini-issues fixed so I can refer changes to purposes. Perhaps something like * getspacesfirstword -

[issue33441] Expose the sigset_t converter via private API

Serhiy Storchaka added the comment: Since posix_spawn() has been removed in 3.7, there is no need to backport this feature. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python

[issue33610] IDLE: Make multiple improvements to CodeContext

Change by Terry J. Reedy : -- dependencies: +IDLE cond context: fix code update and font update timers, IDLE: Add docstrings and tests for codecontext, Idle Code Context: separate changing current and future editors stage: test needed -> title: IDLE: Improve

[issue33537] Help on importlib.resources outputs the builtin open description

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue33475] Fix converting AST expression to string and optimize parenthesis

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue33610] IDLE: Improve CodeContext (various issues)

New submission from Terry J. Reedy : There are a number of possible improvements to CodeContext. They be separate issues (and PRs) that are dependencies of this master index issue. Some should be fairly easy now that we have the new tests. 1. #32831 added docstrings and

[issue33454] Mismatched C function signature in _xxsubinterpreters.channel_close()

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: -Python 3.7 ___ Python tracker

[issue27300] tempfile.TemporaryFile(): missing errors=... argument

Serhiy Storchaka added the comment: Thank you Stephan for your contribution! -- resolution: -> fixed stage: -> resolved status: open -> closed versions: +Python 3.8 -Python 3.6 ___ Python tracker

[issue27300] tempfile.TemporaryFile(): missing errors=... argument

New submission from Serhiy Storchaka : New changeset 825aab95fde959541859383f8ea7e7854ebfd49f by Serhiy Storchaka (sth) in branch 'master': bpo-27300: Add the errors parameter to tempfile classes. (GH-6696)

[issue27485] urllib.splitport -- is it official or not?

Serhiy Storchaka added the comment: This change made test_urlparse failing when ran with -We. Or just producing a lot of warnings in the default mode. == ERROR: test_splitattr

[issue13886] readline-related test_builtin failure

Serhiy Storchaka added the comment: This old issue still is not fixed. Martin, Xavier, could you open a PR please? -- ___ Python tracker

[issue31529] IDLE: Add docstrings and tests for editor.py reload functions

Terry J. Reedy added the comment: There is a reference to this issue in #31494, msg302628 (CodeContext loops). -- ___ Python tracker

[issue33565] strange tracemalloc results

INADA Naoki added the comment: I can't reproduce it: File "test1.py", line 19, in do_get_obj response = s3_client.get_object(Bucket='archpi.dabase.com', Key='style.css') File "/Users/inada-n/tmp/boto-leak/venv/lib/python3.6/site-packages/botocore/client.py",

[issue33604] HMAC default to MD5 marked as to be removed in 3.6

miss-islington added the comment: New changeset 2751dccca4098b799ea575bb35cec9959c74684a by Miss Islington (bot) in branch '3.7': bpo-33604: Remove Pending from hmac Deprecation warning. (GH-7062)

[issue33355] Windows 10 buildbot: 15 min timeout on test_mmap.test_large_filesize()

David Bolen added the comment: I have migrated the win8 and win10 builders to a different machine type on Azure, which seems to have restored more reasonable performance for the tests, at least in the first set of builds. Assuming that continues to hold true, it should

[issue33604] HMAC default to MD5 marked as to be removed in 3.6

Change by miss-islington : -- pull_requests: +6695 ___ Python tracker ___

[issue33604] HMAC default to MD5 marked as to be removed in 3.6

Gregory P. Smith added the comment: New changeset 8bb0b5b03cffa2a2e74f248ef479a9e7fbe95cf4 by Gregory P. Smith (Matthias Bussonnier) in branch 'master': bpo-33604: Remove Pending from hmac Deprecation warning. (GH-7062)

[issue33570] OpenSSL 1.1.1 / TLS 1.3 cipher suite changes

miss-islington added the comment: New changeset cd57b48ef9a70b7ef693ba52aaf38d7c945ab5d3 by Miss Islington (bot) in branch '3.7': bpo-33570: TLS 1.3 ciphers for OpenSSL 1.1.1 (GH-6976)

[issue33609] Document that dicts preserve insertion order

New submission from Yury Selivanov : I don't see it documented that dicts preserve insertion order. 3.7 what's new points to [1], but that section doesn't have a "version changed" tag. IMO, [1] should have two version changed tags: one for 3.6, and one for 3.7. Also, it

[issue33608] [subinterpreters] Add a cross-interpreter-safe mechanism to indicate that an object may be destroyed.

Change by STINNER Victor : -- title: Add a cross-interpreter-safe mechanism to indicate that an object may be destroyed. -> [subinterpreters] Add a cross-interpreter-safe mechanism to indicate that an object may be destroyed.

[issue33607] [subinterpreters] Explicitly track object ownership (and allocator).

Change by STINNER Victor : -- title: Explicitly track object ownership (and allocator). -> [subinterpreters] Explicitly track object ownership (and allocator). ___ Python tracker

[issue33570] OpenSSL 1.1.1 / TLS 1.3 cipher suite changes

Change by miss-islington : -- pull_requests: +6694 ___ Python tracker ___

[issue33570] OpenSSL 1.1.1 / TLS 1.3 cipher suite changes

Christian Heimes added the comment: New changeset e8eb6cb7920ded66abc5d284319a8539bdc2bae3 by Christian Heimes in branch 'master': bpo-33570: TLS 1.3 ciphers for OpenSSL 1.1.1 (GH-6976) https://github.com/python/cpython/commit/e8eb6cb7920ded66abc5d284319a8539bdc2bae3

[issue33608] Add a cross-interpreter-safe mechanism to indicate that an object may be destroyed.

Change by pmpp : -- nosy: +pmpp ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue33608] Add a cross-interpreter-safe mechanism to indicate that an object may be destroyed.

STINNER Victor added the comment: "That is relatively straight-forward except in one case: indicating that the other interpreter doesn't need the object to exist any more (similar to PyBuffer_Release() but more general)" Why an interpreter would access an object from a

[issue33604] HMAC default to MD5 marked as to be removed in 3.6

Change by Serhiy Storchaka : -- nosy: +christian.heimes, gregory.p.smith ___ Python tracker ___

[issue33569] dataclasses InitVar does not maintain any type info

Eric V. Smith added the comment: This seems like a reasonable request. -- nosy: +eric.smith ___ Python tracker ___

[issue33562] Check that the global settings for asyncio are not changed by tests

Change by STINNER Victor : -- nosy: +vstinner ___ Python tracker ___ ___

[issue33604] HMAC default to MD5 marked as to be removed in 3.6

Matthias Bussonnier added the comment: I've sent two PRs, one that updates the deprecation from PendingDeprecationWarning to DeprecationWarning that likely should get applied to 3.6, and 3.7 ? And a PR to actually remove the default in 3.8. --

[issue32400] inspect.isdatadescriptor false negative

Change by Aaron Hall : -- nosy: +Aaron Hall ___ Python tracker ___ ___

[issue33604] HMAC default to MD5 marked as to be removed in 3.6

Change by Matthias Bussonnier : -- pull_requests: +6693 ___ Python tracker ___

[issue33565] strange tracemalloc results

Alexander Mohr added the comment: yes, memory does go up. If you click the botocore bug link you'll see a graph of memory usage over time. -- ___ Python tracker

[issue33605] Detect accessing event loop from a different thread outside of _debug

Yury Selivanov added the comment: > I suggest that asyncio should be stricter about this error and that methods > and functions that operate on the event loop, such as call_soon, call_later, > create_task, ensure_future, and close, should all call _check_thread() even >

[issue33607] Explicitly track object ownership (and allocator).

STINNER Victor added the comment: "Either we'd add 2 pointer-size fields to PyObject or we would keep a separate hash table (or two) pointing from each object to the info (...)" The expect a huge impact on the memory footprint. I dislike the idea. Currently, the smallest

[issue33565] strange tracemalloc results

STINNER Victor added the comment: > this means 21 blocks were not released, and in this case leaked because > nothing should be held onto after the first iteration (creating the initial > connector in the connection pool. In the head object case that's going to be > a

[issue33516] unittest.mock: Add __round__ to supported magicmock methods

STINNER Victor added the comment: Thank you Martijn Pieters for the feature request/bug report, and thanks John Reese for the implementation! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___

[issue33516] unittest.mock: Add __round__ to supported magicmock methods

STINNER Victor added the comment: New changeset 6c4fab0f4b95410a1a964a75dcdd953697eff089 by Victor Stinner (John Reese) in branch 'master': bpo-33516: Add support for __round__ in MagicMock (GH-6880)

[issue23188] Provide a C helper function to chain raised (but not yet caught) exceptions

Eric Snow added the comment: good point :) -- ___ Python tracker ___ ___

[issue33608] Add a cross-interpreter-safe mechanism to indicate that an object may be destroyed.

Eric Snow added the comment: As a lesser (IMHO) alternative, we could also modify Py_DECREF to respect a new "shared" marker of some sort (perhaps relative to #33607), but that would probably still require one of the refcount-based solutions (and add a branch to

[issue33608] Add a cross-interpreter-safe mechanism to indicate that an object may be destroyed.

New submission from Eric Snow : In order to keep subinterpreters properly isolated, objects from one interpreter should not be used in C-API calls in another interpreter. That is relatively straight-forward except in one case: indicating that the other interpreter

[issue33109] argparse: make new 'required' argument to add_subparsers default to False instead of True

Serhiy Storchaka added the comment: Please ignore the last paragraph. It was my mistake, all add_subparsers() parameters are keyword-only, and _SubParsersAction is a privale class. -- ___ Python tracker

[issue33109] argparse: make new 'required' argument to add_subparsers default to False instead of True

Anthony Sottile added the comment: The bug is orthogonal, you can trigger it without the `required=` keyword argument via the (currently suggested) monkeypatch workaround which restores the pre-3.3 behaviour: import argparse parser = argparse.ArgumentParser() subp =

[issue33607] Explicitly track object ownership (and allocator).

New submission from Eric Snow : When an object is created it happens relative to the current thread (ergo interpreter) and the current allocator (part of global state). We do not track either of these details for the object. It may make sense to start doing so

[issue33109] argparse: make new 'required' argument to add_subparsers default to False instead of True

Serhiy Storchaka added the comment: Wouldn't be better to first fix this bug, and only after that add the 'required' parameter? Adding it introduced yet one bug: when pass arguments as positional, the 'help' argument will be swallowed. You can add new parameters

[issue33606] Improve logging performance when logger disabled

New submission from Vinay Sajip : If a logger is disabled (by setting it's disabled attribute to True), the check for this is done late in the dispatch of the logging event - during the handle() call - rather than isEnabledFor(), which would short-circuit some

[issue33603] Subprocess Thread handles grow with each call and aren't released [Windows]

Change by Gregory P. Smith : -- title: Subprocess Thread handles grow with each call and aren't released until script ends -> Subprocess Thread handles grow with each call and aren't released [Windows] ___ Python tracker

[issue33593] Support heapq on typed arrays?

Raymond Hettinger added the comment: As noted by Serhiy, the interaction with the Array type would incur significant overhead. Your fastest approach will be to follow his suggest to first convert to a list and then perform heap manipulations. Marking this as

[issue33109] argparse: make new 'required' argument to add_subparsers default to False instead of True

Anthony Sottile added the comment: That's a separate issue (also a bug introduced by the bad 3.3 patch): https://bugs.python.org/issue29298 I have an open PR to fix it as well but it has not seen review action: https://github.com/python/cpython/pull/3680 --

[issue33109] argparse: make new 'required' argument to add_subparsers default to False instead of True

Serhiy Storchaka added the comment: I tried to use add_subparsers() with required=True and have found it not usable. import argparse parser = argparse.ArgumentParser(prog='PROG') subparsers = parser.add_subparsers(required=True) parser_a =

[issue33605] Detect accessing event loop from a different thread outside of _debug

New submission from Hrvoje Nikšić : Looking at StackOverflow's python-asyncio tag[1], it appears that it's a very common mistake for users to invoke asyncio functions or methods from a thread other than the event loop thread. In some cases this happens because the user is

[issue33603] Subprocess Thread handles grow with each call and aren't released until script ends

Eryk Sun added the comment: The 2nd example with subprocess.run() creates two threads in the Python process, since you're redirecting both stdout and stderr to pipes and run() calls communicate(). The first example with subprocess.Popen() shouldn't create any threads. In

[issue33604] HMAC default to MD5 marked as to be removed in 3.6

Change by Matthias Bussonnier : -- keywords: +patch pull_requests: +6692 stage: -> patch review ___ Python tracker ___

[issue33604] HMAC default to MD5 marked as to be removed in 3.6

New submission from Matthias Bussonnier : HMAC docs says digestmod=md5 default will be removed in 3.6, but was not. We should likely bumpt that to 3.8 in the documentation, and actually remove it in 3.8 -- messages: 317322 nosy: mbussonn priority: normal

[issue33109] argparse: make new 'required' argument to add_subparsers default to False instead of True

Anthony Sottile added the comment: Is there then no pathway for actually fixing the bug? aka how can I get `required=True` to be the default. -- ___ Python tracker

[issue33531] test_asyncio: test_subprocess test_stdin_broken_pipe() failure on Travis CI

Terry J. Reedy added the comment: The patch seems to have worked. The last AppVeyor failure was a day ago, when testing the 3.7 backport of the fix. https://ci.appveyor.com/project/python/cpython/history -- ___ Python tracker

[issue33109] argparse: make new 'required' argument to add_subparsers default to False instead of True

Ned Deily added the comment: > Considering the huge popularity of these SO questions, I don't think this > should be reverted [...] As I understand it (and, again, I make no claim to be an argparse expert), there does not seem to be one absolutely correct answer here; there

[issue30940] Documentation for round() is incorrect.

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue33603] Subprocess Thread handles grow with each call and aren't released until script ends

GranPrego added the comment: Process explorer is showing the handles as belonging to the python executable. I can see the cmd process start,then the executable which terminates cleanly. I can see thread handles appearing under the python process, with some

[issue33593] Support heapq on typed arrays?

Serhiy Storchaka added the comment: Workaround: alist = list(a) heapq.heapify(alist) a[:] = alist And it should be not much slower than using heapq.heapify() directly if it could support general sequences. Using it with array.array would add significant overhead

[issue33603] Subprocess Thread handles grow with each call and aren't released until script ends

Change by Antoine Pitrou : -- nosy: +giampaolo.rodola, gregory.p.smith ___ Python tracker ___

[issue33592] Document contextvars C API

miss-islington added the comment: New changeset afec2d583a06849c5080c6cd40266743c8e04b3e by Miss Islington (bot) in branch '3.7': bpo-33592: Document the C API in PEP 567 (contextvars) (GH-7033)

[issue33593] Support heapq on typed arrays?

Diego Argueta added the comment: However I do see your point about the speed. -- ___ Python tracker ___

[issue23188] Provide a C helper function to chain raised (but not yet caught) exceptions

Serhiy Storchaka added the comment: There is usually more complex code between PyErr_Fetch() and _PyErr_ChainExceptions(): PyObject *exc, *val, *tb, *close_result; PyErr_Fetch(, , ); close_result = _PyObject_CallMethodId(result, _close,

[issue33597] Compact PyGC_Head

Yury Selivanov added the comment: This is such a great idea. +1 from me. -- nosy: +yselivanov ___ Python tracker ___

[issue33603] Subprocess Thread handles grow with each call and aren't released until script ends

Eryk Sun added the comment: The thread handle that CreateProcess returns gets immediately closed in Popen._execute_child, so I can't see how this is due to subprocess. Please check to make sure these thread handles aren't for threads in your own process. Set the lower pane

[issue33593] Support heapq on typed arrays?

Diego Argueta added the comment: I was referring to the C arrays in the Python standard library: https://docs.python.org/3/library/array.html -- ___ Python tracker

[issue33592] Document contextvars C API

Change by miss-islington : -- pull_requests: +6691 ___ Python tracker ___

[issue33592] Document contextvars C API

Yury Selivanov added the comment: New changeset b2f5f59ae15564b991f3ca4850e6ad28d9faacbc by Yury Selivanov (Elvis Pranskevichus) in branch 'master': bpo-33592: Document the C API in PEP 567 (contextvars) (GH-7033)

[issue33565] strange tracemalloc results

Alexander Mohr added the comment: that's not going to affect http://pytracemalloc.readthedocs.io/api.html#get_traced_memory. There is no filter for that :) as to your sum that's exactly what my original callstack lists: 21 memory blocks: 4.7 KiB this means 21 blocks

[issue33565] strange tracemalloc results

STINNER Victor added the comment: Oh. Usually, I strip traces allocated by tracemalloc using filters: http://pytracemalloc.readthedocs.io/examples.html#pretty-top snapshot = snapshot.filter_traces(( tracemalloc.Filter(False, ""),

[issue23188] Provide a C helper function to chain raised (but not yet caught) exceptions

Eric Snow added the comment: FTR, see PEP 490 ("Chain exceptions at C level") which proposed implicitly chaining exceptions in the PyErr_* API. While that PEP was rejected (not all exceptions should be chained), it does make a good point about the clunkiness of

[issue33597] Compact PyGC_Head

INADA Naoki added the comment: In Doc folder: make clean make PYTHON=../python venv /usr/bin/time make html master: 113.15user 0.41system 1:55.46elapsed 98%CPU (0avgtext+0avgdata 205472maxresident)k 18800inputs+223544outputs (1major+66066minor)pagefaults

[issue33565] strange tracemalloc results

Alexander Mohr added the comment: I believe your method is flawed, when enabling tracemalloc it's going to be using memory as well to store the traces. I still believe you need to use the method I mentioned and further even if we don't take into account the total memory

[issue33590] sched.enter priority has no impact on execution

Raymond Hettinger added the comment: It would be nice to either modify the example or add another example to show the use of enterabs() and of the priority field being used as a tie breaker for two events scheduled at the same time. -- nosy: +rhettinger

[issue33593] Support heapq on typed arrays?

Raymond Hettinger added the comment: I don't think we should go down this path. The efficiency of the C implementation depends on it being tightly coupled to lists. This tool is used in the schedulers of various async tools (such as Tornando), used for merge(),

[issue33597] Compact PyGC_Head

INADA Naoki added the comment: @Serhiy php implemented similar idea recently. https://react-etc.net/entry/improvements-to-garbage-collection-gc-php-7-3-boosts-performance-in-benchmark In short, each tracked object have only "index" of GC struct, not "pointer". GC

[issue33597] Compact PyGC_Head

Antoine Pitrou added the comment: Le 22/05/2018 à 17:31, INADA Naoki a écrit : > > INADA Naoki added the comment: > > $ ./python-gc -c 'import asyncio,sys; sys._debugmallocstats()' Thanks. You can also collect peak memory stats during the benchmark

[issue30877] possibe typo in json/scanner.py

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue2504] Add gettext.pgettext() and variants support

Éric Araujo added the comment: It was an answer to «Is there anything I can do to help get this into the codebase» Feel free to take this on! I’ll try to review. -- ___ Python tracker

[issue33597] Compact PyGC_Head

Serhiy Storchaka added the comment: This is an interesting idea. The other problem with the garbage collecting is that it modifies the memory of all collectable objects. This leads to deduplicating virtually all memory blocks after the fork, even if these objects

[issue33597] Compact PyGC_Head

INADA Naoki added the comment: $ ./python-gc -c 'import asyncio,sys; sys._debugmallocstats()' master: # bytes in allocated blocks=4,011,368 # bytes in available blocks= 136,640 50 unused pools * 4096 bytes =

[issue33597] Compact PyGC_Head

Antoine Pitrou added the comment: Interesting. Do you have any comparisons on memory footprint too? -- ___ Python tracker ___

[issue33603] Subprocess Thread handles grow with each call and aren't released until script ends

New submission from GranPrego : On windows 7 / 10 I'm using subprocess to launch a dos cmdline executable and returning the results, which is all working fine. However, each time I make a call, the Python handle count is gradually increasing, jumping up , back a

[issue33238] AssertionError on await of Future returned by asyncio.wrap_future

Change by Jason Haydaman : -- keywords: +patch pull_requests: +6690 stage: -> patch review ___ Python tracker ___

[issue33597] Compact PyGC_Head

INADA Naoki added the comment: $ ./python -m perf compare_to master.json twogc.json -G --min-speed=2 Slower (3): - scimark_monte_carlo: 268 ms +- 9 ms -> 278 ms +- 8 ms: 1.04x slower (+4%) - fannkuch: 1.03 sec +- 0.02 sec -> 1.06 sec +- 0.02 sec: 1.03x slower (+3%) -

[issue33601] [EASY DOC] Py_UTF8Mode is not documented

Serhiy Storchaka added the comment: If there are reasons of including it in the limited API, it should be documented. -- ___ Python tracker

[issue33602] Remove set and queue references from Data Types

Change by Andrés Delfino : -- keywords: +patch pull_requests: +6689 stage: -> patch review ___ Python tracker ___

[issue33602] Remove set and queue references from Data Types

New submission from Andrés Delfino : Data Types mentions sets (which are now built-in) and synchronized queues (now mentioned in Concurrent Execution). I'm proposing fixing this. PR also adds mention to bytearray. -- assignee: docs@python components: Documentation

[issue33601] [EASY DOC] Py_UTF8Mode is not documented

STINNER Victor added the comment: I wasn't sure if I should document it, but after talking with Serhiy on IRC, I now agree that the new variable should be documented. It should be documented at: https://docs.python.org/dev/c-api/init.html#global-configuration-variables

[issue29640] _PyThreadState_Init and fork race leads to inconsistent key list

STINNER Victor added the comment: > But! I suppose we could fix the bug only for platforms with > PTHREAD_KEY_T_IS_COMPATIBLE_WITH_INT. Yes, this is my proposal. >> I propose to cast pthread_key_create() result to int, but only define >> PyThread_create_key() in

[issue28240] Enhance the timeit module: display average +- std dev instead of minimum

Serhiy Storchaka added the comment: Yes, it was my thought. But seems you are right, it is easier to use Python as a programming language. In the past I used the CLI because the programming interface didn't supported autoranging. Although I would change the

[issue33565] strange tracemalloc results

STINNER Victor added the comment: A memory leak is when each iteration adds a fixed number of bytes of the memory: I'm talking about tracemalloc.get_traced_memory()[0] value. For example, if you compare the total traced memory between your iteration 30 and iteration 20,

[issue33197] Confusing error message when constructing invalid inspect.Parameters

Dong-hee Na added the comment: Can I get a code review for PR 6636? -- ___ Python tracker ___

[issue33470] Changes from GH-1638 (GH-3575, bpo-28411) are not documented in Porting to Python 3.7

STINNER Victor added the comment: > Also, the actual removal of the "modules" field was reverted. Oh... I didn't understand that part :-) Ok. In this case it's fine to close this documentation issue. Nothing should be documented for 3.7 ;-) --

[issue33601] Py_UTF8Mode is not documented

New submission from Serhiy Storchaka : Py_UTF8Mode was added to the limited API in 3.7, but it is not documented anywhere. -- assignee: docs@python components: Documentation messages: 317286 nosy: docs@python, ncoghlan, serhiy.storchaka, vstinner priority:

[issue23860] Windows: Failure to check return value from lseek() in Modules/mmapmodule.c

STINNER Victor added the comment: Oh right, PR 7017 does that: it removes the lseek() call ;-) -- ___ Python tracker ___

[issue23860] Windows: Failure to check return value from lseek() in Modules/mmapmodule.c

STINNER Victor added the comment: "At the moment, I'm not sure if it's needed or not, but if it's only an issue with XP, then it might not be worth fixing...:)" If the workaround is no longer needed, the lseek() call should be removed. -- components: +Windows

[issue28167] remove platform.linux_distribution()

STINNER Victor added the comment: FYI I created bpo-33600: "[EASY DOC] Python 2: document that platform.linux_distribution() has been removed". -- ___ Python tracker

  1   2   >