[issue21914] Create unit tests for Turtle guionly

RAJALAKSHMI V added the comment: I’m no longer working on this. Please feel free to take it up. Rajalakshmi.V > On 12-Feb-2019, at 11:48 AM, Joannah Nanjekye wrote: > > > Joannah Nanjekye added the comment: > > @RAJALAKSHMI V Any status on this? I would love to take this up if you are no

[issue25461] Unclear language (the word ineffective) in the documentation for os.walk

Joannah Nanjekye added the comment: What is the status on this? From this discussion, it looks like @vstinner pushed changes to resolve this. Do we close this? If this still needs a patch, then one of the patches can be reviewed in a PR on GitHub. -- nosy: +nanjekyejoannah

[issue21914] Create unit tests for Turtle guionly

Joannah Nanjekye added the comment: @RAJALAKSHMI V Any status on this? I would love to take this up if you are no longer working on it. -- nosy: +nanjekyejoannah ___ Python tracker

[issue35973] `growable_int_array type_ignores` in parsetok.c is not always freed.

Guido van Rossum added the comment: Thanks for the report! I think I see a path through the code that doesn't free the memory. Does this patch fix it? diff --git a/Parser/parsetok.c b/Parser/parsetok.c index 1fa4a1286b..6a96f6bc5a 100644 --- a/Parser/parsetok.c +++ b/Parser/parsetok.c @@

[issue35973] `growable_int_array type_ignores` in parsetok.c is not always freed.

Change by Karthikeyan Singaravelan : -- nosy: +gvanrossum ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35934] Add socket.bind_socket() utility function

Giampaolo Rodola' added the comment: Closing this out as duplicate. Will continue in issue35934. -- resolution: -> duplicate stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue17561] Add socket.bind_socket() convenience function

Giampaolo Rodola' added the comment: After iterating over this over the last few days I realized it makes more sense to implement and discuss the whole thing in here and as a single PR, so sorry about previously splitting this in a separate ticket/PR. Relevant PR is now this one and is

[issue35976] PCBuild file changes for arm32 should be separated from code changes for review

Change by Paul Monson : -- keywords: +patch pull_requests: +11855 stage: -> patch review ___ Python tracker ___ ___

[issue35976] PCBuild file changes for arm32 should be separated from code changes for review

Change by Paul Monson : -- components: Build, Windows nosy: Paul Monson, paul.moore, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open title: PCBuild file changes for arm32 should be separated from code changes for review type: enhancement versions:

[issue35813] shared memory construct to avoid need for serialization between processes

Davin Potts added the comment: @giampaolo.rodola: It definitely helps. Conceptually, SyncManager provides "distributed shared memory" where lists, dicts, etc. are held in memory by one process but may be accessed remotely from another via a Proxy Object. Mutating a dict from one process

[issue35971] Documentation should warn about code injection from current working directory

Karthikeyan Singaravelan added the comment: The change in behavior of Perl was discussed in https://mail.python.org/pipermail/python-ideas/2017-June/045842.html -- nosy: +vstinner, xtreak ___ Python tracker

[issue35813] shared memory construct to avoid need for serialization between processes

Raymond Hettinger added the comment: FWIW, I read the draft docs and found them to be at the right level throughout. I definitely wouldn't want anything more terse. -- ___ Python tracker

[issue35972] _xxsubinterpreters: channel_send() may truncate ints on 32-bit platforms

Eric Snow added the comment: Is "long long" (AKA int64_t) 32 bits or 64 bits on a 32-bit platform? It it's always 32 bits then there is no problem here. Otherwise I agree we have a problem to fix. My understanding is that it is the former (always 32 bits). --

[issue35975] Put back the ability to parse files where async/await aren't keywords

Change by Ethan Smith : -- nosy: +Ethan Smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35918] multiprocessing's SyncManager.dict.has_key() method is broken

Giampaolo Rodola' added the comment: New changeset 58f05ce059cc5207320fef27a9fbc0ffdc2b1d1a by Giampaolo Rodola (Miss Islington (bot)) in branch '3.7': bpo-35918: Remove broken has_key method and add test (GH-11819) (#11824)

[issue35918] multiprocessing's SyncManager.dict.has_key() method is broken

Change by miss-islington : -- pull_requests: +11854 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35918] multiprocessing's SyncManager.dict.has_key() method is broken

Giampaolo Rodola' added the comment: New changeset a31f4cc881992e84d351957bd9ac1a92f882fa39 by Giampaolo Rodola (Rémi Lapeyre) in branch 'master': bpo-35918: Remove broken has_key method and add test (#11819) https://github.com/python/cpython/commit/a31f4cc881992e84d351957bd9ac1a92f882fa39

[issue35975] Put back the ability to parse files where async/await aren't keywords

Change by Ivan Levkivskyi : -- nosy: +levkivskyi ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35505] Test test_imaplib fail in test_imap4_host_default_value

Change by Matej Cepl : -- keywords: +patch pull_requests: +11853 stage: -> patch review ___ Python tracker ___ ___

[issue35963] Python/symtable.c: warning: enumeration value ‘FunctionType_kind’ not handled in switch [-Wswitch]"

Change by Guido van Rossum : -- stage: -> resolved ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35766] Merge typed_ast back into CPython

Guido van Rossum added the comment: See https://bugs.python.org/issue35975 -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue35975] Put back the ability to parse files where async/await aren't keywords

New submission from Guido van Rossum : Now that the ast module can be used to parse type comments, there’s one more feature I’d like to lobby for – a flag that modifies the grammar slightly so it resembles an older version of Python (going back to 3.4). This is used in mypy to decouple the

[issue35766] Merge typed_ast back into CPython

Guido van Rossum added the comment: I have some follow-up wishes but I'll create a new issue. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue35963] Python/symtable.c: warning: enumeration value ‘FunctionType_kind’ not handled in switch [-Wswitch]"

Change by Guido van Rossum : -- stage: resolved -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35974] os.DirEntry.inode() returns invalid value within Docker container

New submission from Marat Sharafutdinov : I'm trying to build Python 3.7.2 within official CentOS 7.6.1810 image (https://hub.docker.com/_/centos) and getting the following error during testing: == FAIL: test_attributes

[issue35973] `growable_int_array type_ignores` in parsetok.c is not always freed.

New submission from Brennan Vincent : To reproduce: (1) build python: `../configure --prefix=$HOME/prefix --with-pydebug --without-pymalloc && make install` (2) run with valgrind: `valgrind --leak-check=full ~/prefix/bin/python3` (3) exit immediately from the interpreter by pressing ^D (4)

[issue35813] shared memory construct to avoid need for serialization between processes

Giampaolo Rodola' added the comment: I submitted an initial review / comments in the PR. I think this is good for a first iteration in order to understand what APIs to expose publicly (also, keep in mind I may not have a full picture of how this is intended to be used precisely). As for

[issue35972] _xxsubinterpreters: channel_send() may truncate ints on 32-bit platforms

Change by Alexey Izbyshev : -- keywords: +patch pull_requests: +11852 stage: -> patch review ___ Python tracker ___ ___

[issue35972] _xxsubinterpreters: channel_send() may truncate ints on 32-bit platforms

New submission from Alexey Izbyshev : Victor Stinner pointed out that on x86 Gentoo Installed with X 3.x buildbot, there is a compiler warning: Python/pystate.c:1483:18: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]

[issue35971] Documentation should warn about code injection from current working directory

New submission from Gabriel Corona : The CLI tools shipped in Debian python-rdflib-tools package can load modules from the current directory [1]: $ echo 'print("Something")' > cgi.py $ rdf2dot INFO:rdflib:RDFLib Version: 4.2.2 Something Reading from stdin as None... This

[issue2771] Test issue

Stéphane Wirtel added the comment: irc pong -- nosy: +matrixise ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue35955] difflib reports incorrect location of mismatch

Tim Peters added the comment: It's probably OK, but there's no "pure win" to be had here. There's generally more than one way to convert one string to another, and what "looks right" to humans depends a whole lot on context. For example, consider these strings: "private Thread

[issue35955] difflib reports incorrect location of mismatch

Jason R. Coombs added the comment: Nice insight Tim. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue2771] Test issue

Antoine Pitrou added the comment: notifying a lot of people -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue2771] Test issue

Ernest W. Durbin III added the comment: test -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35963] Python/symtable.c: warning: enumeration value ‘FunctionType_kind’ not handled in switch [-Wswitch]"

STINNER Victor added the comment: Thanks for the fix, Guido ;-) -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue35963] Python/symtable.c: warning: enumeration value ‘FunctionType_kind’ not handled in switch [-Wswitch]"

Guido van Rossum added the comment: New changeset 522346d792d9013140a3f4ad3534ac10f38d9085 by Guido van Rossum in branch 'master': Complete switch cases in symtable.c; fixes bpo-35963 (GH-11821) https://github.com/python/cpython/commit/522346d792d9013140a3f4ad3534ac10f38d9085 --

[issue2771] Test issue

Ernest W. Durbin III added the comment: should be fast send. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue35813] shared memory construct to avoid need for serialization between processes

Davin Potts added the comment: @terry.reedy and @ronaldoussoren: I have asked Van again to provide comments here clarifying the topics of (1) copyright notices and (2) requiring the BSD-licensed-work's author to sign a contributor agreement. Specifically regarding the appearance of

[issue35969] Interpreter crashes with "can't initialize init_sys_streams" when abc fails to import

Karthikeyan Singaravelan added the comment: Sorry by previous reports I was talking about some of the issues where the installers were not correct though I couldn't find the issue at the moment. I just presented it as a data point where some necessary modules that cannot be imported could

[issue2771] Test issue

Ernest W. Durbin III added the comment: test mail sending -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35955] difflib reports incorrect location of mismatch

Karthikeyan Singaravelan added the comment: Thanks for the explanation. This seems to give the desired diff with charjunk=None passed to multiline string comparison helper. I am not sure how useful it would be to pass it to sequence and dict comparison that also use ndiff. I can open a PR if

[issue35969] Interpreter crashes with "can't initialize init_sys_streams" when abc fails to import

Paul Ganssle added the comment: @Karthikeyan I would certainly consider this a duplicate of the encodings bug/behavior that you demonstrate. I don't see an existing bug on the tracker for it, though. I think it's pretty clear that the interpreter needs to fail, but it seems to *crash*

[issue35970] no help flag in base64 util

New submission from Robert Kuska : I failed today to print help message for base64 utility without an error: $ python3 -m base64 -help option -h not recognized usage: /usr/local/Cellar/python/3.7.2_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/base64.py [-d|-e|-u|-t] [file|-]

[issue2771] Test issue

Ernest W. Durbin III added the comment: test comment -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue2771] Test issue

Ernest W. Durbin III added the comment: comment on test issue to test the request time. -- ___ Python tracker ___ ___

[issue35955] difflib reports incorrect location of mismatch

Tim Peters added the comment: difflib generally synchs on the longest contiguous matching subsequence that doesn't contain a "junk" element. By default, `ndiff()`'s optional `charjunk` argument considers blanks and tabs to be junk characters. In the strings: "drwxrwxr-x 2 2000 2000\n"

[issue35967] Better platform.processor support

Change by Ned Deily : -- nosy: +lemburg ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue23460] Decimals do not obey ':g' exponential notation formatting rules

Brennan D Baraban <3...@holbertonschool.com> added the comment: Well, Tuomas, I defer submission of a PR to you, as its your original patch. -- ___ Python tracker ___

[issue35968] lib2to3 cannot parse rf''

Ned Deily added the comment: @xtreak, I concur. While it would have better to originally fix this in the release where f strings first appeared, the window to do that has closed. Sorry! -- nosy: +ned.deily resolution: -> duplicate stage: -> resolved status: open -> closed

[issue35969] Interpreter crashes with "can't initialize init_sys_streams" when abc fails to import

Karthikeyan Singaravelan added the comment: I hope there are certain modules that CPython interpreter expects to load properly. There were some cases in the past where encodings module caused the interpreter to crash. A similar scenario. ➜ cpython git:(master) echo "raise Exception('a')" >

[issue35955] difflib reports incorrect location of mismatch

Karthikeyan Singaravelan added the comment: I am not sure this is a duplicate since the other issue was about newline at the end of strings. This is about the diff being little irrelevant even with newline in the end for strings. Sample program where change in 5th character gives the

[issue35955] difflib reports incorrect location of mismatch

Jason R. Coombs added the comment: I don't think so, because the issue happens on a single line diff... although it's plausible there's a common-mode fix. -- ___ Python tracker

[issue35955] difflib reports incorrect location of mismatch

Chris Jerdonek added the comment: Is this a duplicate of issue24780? -- nosy: +chris.jerdonek ___ Python tracker ___ ___

[issue35969] Interpreter crashes with "can't initialize init_sys_streams" when abc fails to import

Paul Ganssle added the comment: Tested with 3.6 and 2.7 - core dump on 3.6, no core dump on 2.7. The crash on 2.7 goes through a different path, it goes site.py > os.py >= UserDict.py > _abcoll.py > abc.py. That may account for why it's not crashing the interpreter itself. --

[issue35969] Interpreter crashes with "can't initialize init_sys_streams" when abc fails to import

New submission from Paul Ganssle : Just noticed this (tested on Python 3.7 and 3.8): mkdir /tmp/demo cd /tmp/demo cat << EOF > abc.py raise Exception("Hi") EOF PYTHONPATH=: python -c "" This will crash the interpreter with: Fatal Python error: init_sys_streams:

[issue35965] Behavior for unittest.assertRaisesRegex differs depending on whether it is used as a context manager

Karthikeyan Singaravelan added the comment: No problem, after some debugging the statement finally executed is 'exec(compile("set.add(0)", "foo.py", "exec"))' . In Python interpreter this will give the expected error. It also gives the same error before coverage.start() [0] and gives a

[issue35378] multiprocessing.Pool.imaps iterators do not maintain alive the multiprocessing.Pool objects

Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue35378] multiprocessing.Pool.imaps iterators do not maintain alive the multiprocessing.Pool objects

Pablo Galindo Salgado added the comment: New changeset 3766f18c524c57784eea7c0001602017d2122156 by Pablo Galindo in branch 'master': bpo-35378: Fix multiprocessing.Pool references (GH-11627) https://github.com/python/cpython/commit/3766f18c524c57784eea7c0001602017d2122156 --

[issue35968] lib2to3 cannot parse rf''

Karthikeyan Singaravelan added the comment: The reported example works fine on master and 3.7 . The related issue's fix was not backported to 3.6 . 3.6 is in security fixes only mode. So upgrading to 3.7 will help and I propose closing this as a duplicate of issue33266 . ➜ cpython

[issue35968] lib2to3 cannot parse rf''

Karthikeyan Singaravelan added the comment: Seems related : issue33266 -- nosy: +xtreak ___ Python tracker ___ ___

[issue35965] Behavior for unittest.assertRaisesRegex differs depending on whether it is used as a context manager

SylvainDe added the comment: I have no explanation whatsoever but removing the call to coverage seems to remove the issue: https://travis-ci.org/SylvainDe/DidYouMean-Python/builds/491727724 . I guess we can close this issue - sorry for the inconvenience. @nedbat: do you want me to open an

[issue35968] lib2to3 cannot parse rf''

New submission from Dylan Lloyd : ``` #!/usr/bin/env python # -*- coding: utf-8 -*- regex_format = rf'' ``` ``` yapf poc.py ``` ``` Traceback (most recent call last): File "lib/python3.6/site-packages/yapf/yapflib/pytree_utils.py", line 115, in ParseCodeToTree tree =

[issue35965] Behavior for unittest.assertRaisesRegex differs depending on whether it is used as a context manager

SylvainDe added the comment: This is a brilliant idea! I'll give it a try and keep you posted. -- ___ Python tracker ___ ___

[issue35963] Python/symtable.c: warning: enumeration value ‘FunctionType_kind’ not handled in switch [-Wswitch]"

Change by Guido van Rossum : -- keywords: +patch, patch, patch pull_requests: +11848, 11849, 11850 stage: -> patch review ___ Python tracker ___

[issue35963] Python/symtable.c: warning: enumeration value ‘FunctionType_kind’ not handled in switch [-Wswitch]"

Change by Guido van Rossum : -- keywords: +patch, patch pull_requests: +11848, 11849 stage: -> patch review ___ Python tracker ___

[issue35963] Python/symtable.c: warning: enumeration value ‘FunctionType_kind’ not handled in switch [-Wswitch]"

Change by Guido van Rossum : -- keywords: +patch pull_requests: +11848 stage: -> patch review ___ Python tracker ___ ___

[issue35963] Python/symtable.c: warning: enumeration value ‘FunctionType_kind’ not handled in switch [-Wswitch]"

Guido van Rossum added the comment: Sure, I'll fix it. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35955] difflib reports incorrect location of mismatch

Karthikeyan Singaravelan added the comment: I have tried with different places where only '-' and 'w' differ. They seemed to produce correct diff except for this once case where the diff was confusing. -- nosy: +tim.peters type: -> behavior versions: +Python 2.7, Python 3.7, Python

[issue35766] Merge typed_ast back into CPython

Guido van Rossum added the comment: New changeset 4b250fc1da9c893803cf724a4974450b5e10bd8a by Guido van Rossum in branch 'master': bpo-35766 follow-up: Add an error check to new_type_comment() (#11766) https://github.com/python/cpython/commit/4b250fc1da9c893803cf724a4974450b5e10bd8a

[issue35965] Behavior for unittest.assertRaisesRegex differs depending on whether it is used as a context manager

Karthikeyan Singaravelan added the comment: Is this something related to running under coverage? With the failure commit on Travis I built the binary and there are no failures with unittest but the tests fail with coverage. Running 'set.add(0)' under coverage and as normal file generates

[issue35918] multiprocessing's SyncManager.dict.has_key() method is broken

Antoine Pitrou added the comment: That sounds fine to me. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35955] difflib reports incorrect location of mismatch

Jason R. Coombs added the comment: I'm re-opening this issue as it does seem to apply stdlib (difflib.ndiff), which is why I encountered it both in unittest and pytest. Thanks xtreak for the distilled example. -- resolution: third party -> stage: resolved -> status: closed -> open

[issue35889] sqlite3.Row doesn't have useful repr

Change by Roundup Robot : -- keywords: +patch, patch, patch, patch pull_requests: +11844, 11845, 11846, 11847 stage: -> patch review ___ Python tracker ___

[issue35889] sqlite3.Row doesn't have useful repr

Change by Roundup Robot : -- keywords: +patch, patch pull_requests: +11844, 11845 stage: -> patch review ___ Python tracker ___

[issue35889] sqlite3.Row doesn't have useful repr

Change by Roundup Robot : -- keywords: +patch pull_requests: +11844 stage: -> patch review ___ Python tracker ___ ___

[issue35889] sqlite3.Row doesn't have useful repr

Change by Roundup Robot : -- keywords: +patch, patch, patch pull_requests: +11844, 11845, 11847 stage: -> patch review ___ Python tracker ___

[issue35918] multiprocessing's SyncManager.dict.has_key() method is broken

Rémi Lapeyre added the comment: has_key method has been removed in Python3 so I think we can remove it from the DictProxy as well as nobody should be relying on it anymore. -- ___ Python tracker

[issue35918] multiprocessing's SyncManager.dict.has_key() method is broken

Change by Rémi Lapeyre : -- keywords: +patch, patch, patch pull_requests: +11841, 11842, 11843 stage: needs patch -> patch review ___ Python tracker ___

[issue35918] multiprocessing's SyncManager.dict.has_key() method is broken

Change by Rémi Lapeyre : -- keywords: +patch pull_requests: +11841 stage: needs patch -> patch review ___ Python tracker ___ ___

[issue35918] multiprocessing's SyncManager.dict.has_key() method is broken

Change by Rémi Lapeyre : -- keywords: +patch, patch pull_requests: +11841, 11842 stage: needs patch -> patch review ___ Python tracker ___

[issue35959] math.prod(range(10)) caues segfault

Pablo Galindo Salgado added the comment: @Mark long x = i_result * b; is still on the PR but the check for overflow does not use x. I will update the PR to move that line inside the overflow-safe block to prevent UB from happening and affecting the check itself (or the rest of the

[issue7850] platform.system() should be "macosx" instead of "Darwin" on OSX

Ronald Oussoren added the comment: This issue can be closed. Status quo wins due to backward compatibility concerns. BTW. The primary reason for proposing "macosx" as the return value for platform.system() is that the platform name as used in egg files (at the time, now wheels) is

[issue26024] Non-ascii Windows locale names

Steve Dower added the comment: We should switch to _wsetlocale, or else come up with a more sensible mapping that makes sense between platforms (like we have for encodings already). I suspect the latter requires proper design and discussion, so it's worth doing the first part immediately.

[issue35959] math.prod(range(10)) caues segfault

Mark Dickinson added the comment: @Pablo: Thanks; I saw the PR. It looks as though the troublesome line long x = i_result * b; is still there in that PR, though. Or am I misreading? The difficulty here is that the check for overflow has to happen as a means of preventing invoking

[issue35959] math.prod(range(10)) caues segfault

Pablo Galindo Salgado added the comment: @Mark Dickinson Thanks for the links. I had opened yesterday PR11809 addressing the UB and adding more tests. Could you review the PR? -- ___ Python tracker

[issue18283] shutil.which() should support bytes

Change by Cheryl Sabella : -- pull_requests: +11840 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing

[issue35959] math.prod(range(10)) caues segfault

Karthikeyan Singaravelan added the comment: @pablogsal I am reopening this since this has an open PR though original issue was fixed. Feel free to close this if this can be discussed in a separate issue. -- resolution: fixed -> stage: resolved -> patch review status: closed -> open

[issue35959] math.prod(range(10)) caues segfault

Mark Dickinson added the comment: See below for a link to the Python 2.7 code for int * int multiplication (which needs to detect overflow so that it knows when to promote to long): https://github.com/python/cpython/blob/2f1a317d5fdc45b9d714b067906f612f636ba08e/Objects/intobject.c#L496-L518

[issue35918] multiprocessing's SyncManager.dict.has_key() method is broken

Rémi Lapeyre added the comment: Hi @giampaolo.rodola, I will post a PR for this issue. -- nosy: +remi.lapeyre ___ Python tracker ___

[issue35959] math.prod(range(10)) caues segfault

Mark Dickinson added the comment: This approach to overflow checking needs reworking; the current code, in lines like: long x = i_result * b; induces undefined behaviour on overflow. That's something we need to avoid. -- nosy: +mark.dickinson

[issue35967] Better platform.processor support

New submission from Jason R. Coombs : or: Unable to implement 'uname' on Python due to recursive call or: platform.uname() should avoid calling `uname` in a subprocess In [this issue](https://github.com/jaraco/cmdix/issues/1), I stumbled across a strange and somewhat unintuitive behavior.

[issue7850] platform.system() should be "macosx" instead of "Darwin" on OSX

STINNER Victor added the comment: I suggest to close this issue. @Ronald: Or do you think that something should still be done on macOS in the platform module? This issue looks like a duplicate of bpo-35516. It has been decided that platform.system_alias() doesn't replace Darwin with macOS

[issue7850] platform.system() should be "macosx" instead of "Darwin" on OSX

Jason R. Coombs added the comment: This issue now needs to consider that Mac OS X was renamed to macOS. -- nosy: +jaraco ___ Python tracker ___

[issue35964] shutil.make_archive (xxx, tar, root_dir) is adding './' entry to archive which is wrong

Change by Oskar Persson : -- nosy: +Oskar Persson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35966] Didn't raise "StopIteration" Error when I use "yield" in the function

SilentGhost added the comment: Within a generator function, StopIteration exception is a sign that generator is finished. This is why this exception is caught automatically, and closes generator. This is normal and documented behaviour of generators. -- nosy: +SilentGhost, sheiun

[issue35966] Didn't raise "StopIteration" Error when I use "yield" in the function

sheiun added the comment: But it still can catch by using try/except >>> def generate_loop_stopiteration(): ... for i in range(10): ... print(i) ... # should raise StopIteration when i > 5 ... try: ... k = next(j for j in range(5) if j == i) ...

[issue35966] Didn't raise "StopIteration" Error when I use "yield" in the function

Change by sheiun : -- nosy: -sheiun ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35966] Didn't raise "StopIteration" Error when I use "yield" in the function

New submission from sheiun : Python 3.6.7 |Anaconda custom (64-bit)| (default, Oct 28 2018, 19:44:12) [MSC v.1915 64 bit (AMD64)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> def generate_loop(): ... for i in range(10): ... print(i) ...

[issue35965] Behavior for unittest.assertRaisesRegex differs depending on whether it is used as a context manager

SylvainDe added the comment: That's the very weird thing. I've been unable to reproduce this locally but it can be seen on Travis runs. Here are the results so far (Versions numbers are retrieved with python -VV and python -c "import sys; print(sys._git)"): On some versions, both tests

  1   2   >