[issue37174] sched.py: run() is caught in delayfunc even if all events are cancelled.

Raymond Hettinger added the comment: Marking this as 3.9 because it is an API change. Also, you can already control the delayfunc through the current API, so I don't see the necessity of a changing the default which seems to work fine for most users. Tim, what do you think? --

[issue36422] tempfile.TemporaryDirectory() removes entire directory tree even if it's a mount-point

Jeffrey Kintscher added the comment: Another data point: On macOS 10.14.4, unlink() returns EBUSY when it tries to delete the mount point. tempfile.TemporaryDirectory() doesn't handle EBUSY and ends up skipping over the mount point and propagates the OSError exception up to the caller. It

[issue29505] Submit the re, json, & csv modules to oss-fuzz testing

Change by Ammar Askar : -- pull_requests: +13780 pull_request: https://github.com/python/cpython/pull/13907 ___ Python tracker ___

[issue37174] sched.py: run() is caught in delayfunc even if all events are cancelled.

Terry J. Reedy added the comment: 3.6 only gets security fixes. 3.7, 3.8 only get bugfixes. Something new should be a separate PR. -- nosy: +terry.reedy stage: -> test needed versions: -Python 3.6 ___ Python tracker

[issue37178] One argument form of math.perm()

Raymond Hettinger added the comment: It's possible the word permutations means something different to you than it does to me. The itertools.permutations() function is only one function, one that includes the default option to generate all permutations. It does the same as permute(n, r)

[issue37176] super() docs don't say what super() does

Steven D'Aprano added the comment: > > What matters is the __mro__ attribute of the first argument. It matters > because that is how the MRO actually is searched. > > By the way, if it was true (it is not), Yes, I see that now. > then what did you think was > the purpose of the second

[issue37173] inspect.getfile error names module instead of passed class

Terry J. Reedy added the comment: The correct message would be " is a built-in class" We do not backport exception message changes unless 'buggy enough'. I asked on core-mentorship whether this fix qualifies. -- nosy: +terry.reedy ___ Python

[issue37188] Creating a ctypes array of an element with size zero causes "Fatal Python error: Floating point exception"

Change by Eric Wieser : -- pull_requests: +13779 stage: backport needed -> patch review pull_request: https://github.com/python/cpython/pull/13906 ___ Python tracker ___

[issue37172] Odd error awaiting a Future

Terry J. Reedy added the comment: Dima, unless you want to make a specific doc change suggestion, I think this should be closed. The planned code changes will be on other issues. -- nosy: +terry.reedy ___ Python tracker

[issue37176] super() docs don't say what super() does

Change by Raymond Hettinger : -- assignee: docs@python -> rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue37178] One argument form of math.perm()

Change by Raymond Hettinger : -- keywords: +patch pull_requests: +13778 stage: -> patch review pull_request: https://github.com/python/cpython/pull/13905 ___ Python tracker

[issue37176] super() docs don't say what super() does

Steven D'Aprano added the comment: > I'm sorry to say that you're wrong here. I'm happy to be corrected. It is fair to say I failed to take the multiple inheritance case into account. Clearly super can't *only* look at the MRO of the first object since that will miss the multiple

[issue36924] Simplify implementation of classmethod_descriptor.__call__

Raymond Hettinger added the comment: > However, calling them is unlikely to happen in practice: the > only way to obtain such an object is to extract from the > class __dict__. Generally the experience of the PyPy team has been that every code that a user can take is in fact taken by some

[issue37200] PyType_GenericAlloc might over-allocate memory

Neil Schemenauer added the comment: Updated patch is attached. It appears that the extra item is only needed if Py_TPFLAGS_TYPE_SUBCLASS set. In all other cases, it seems we don't need the extra space for the sentinel. At least, the unit tests pass with this change. It could be that

[issue18355] Merge super() guide into documentation

Raymond Hettinger added the comment: I think for now I'll leave this as an external supplement to the documentation. My previous experience with moving a personal blog post into the main docs didn't go so well. -- resolution: -> rejected stage: -> resolved status: open -> closed

[issue37172] Odd error awaiting a Future

Change by Terry J. Reedy : -- title: Odd error awating a Future -> Odd error awaiting a Future versions: +Python 3.9 ___ Python tracker ___

[issue37161] Pre-populate user editable text in input()

Terry J. Reedy added the comment: I like the idea, but doubt this can be implemented. Python assumes a least-common-denominator dumb terminal. Program output is sent on stdout/err and displayed read-only. Used input is read from stdin. It is put there either key by key or after the

Re: SyntaxError: positional argument follows keyword argument

On Fri, 7 Jun 2019, Terry Reedy wrote: An additional error is the missing ()s. This would make input_var refer to the class, not an instance thereof. Oops! I completely missed that. Thanks, Terry, Rich -- https://mail.python.org/mailman/listinfo/python-list

[issue37150] Do not allow to pass FileType class object instead of instance in add_argument

Change by Andrew Svetlov : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: -Python 2.7, Python 3.7 ___ Python tracker ___

[issue37150] Do not allow to pass FileType class object instead of instance in add_argument

miss-islington added the comment: New changeset 606ac581e2451c420117c55632f0fe13d4cec2cd by Miss Islington (bot) in branch '3.8': bpo-37150: Throw ValueError if FileType class object was passed in add_argument (GH-13805)

[issue36964] `python3 -m venv NAME`: virtualenv is not portable

Change by Brett Cannon : -- nosy: -brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36964] `python3 -m venv NAME`: virtualenv is not portable

Brett Cannon added the comment: Please do not add me back to the nosy list as I stand by my thinking that this feature isn't worth pursuing. I understand you feel they are reasonable, Marco, but I don't like the idea of changing what VIRTUAL_ENV gets set to when I believe you should

Re: SyntaxError: positional argument follows keyword argument

On 6/7/2019 2:43 PM, Rich Shepard wrote: I understand positional and keyword arguments and the syntax for the ttk.Checkbutton as described on . $ python3 geochem.py   File "geochem.py", line 60     ttk.Checkbutton(text='Censored?',

[issue37162] new importlib dependencies csv, email and zipfile

Brett Cannon added the comment: @serhiy: mind opening a new issue for your zipfile.Path worry? -- ___ Python tracker ___ ___

[issue37201] fix test_distutils failures for Windows ARM64

Change by Paul Monson : -- keywords: +patch pull_requests: +13777 stage: -> patch review pull_request: https://github.com/python/cpython/pull/13902 ___ Python tracker ___

Re: SyntaxError: positional argument follows keyword argument

On Sat, 8 Jun 2019, Chris Angelico wrote: Right, but the problem was actually in the LabelInput call, not the Checkbutton itself. ChrisA, That's what I found and fixed. Now working on a slightly different issue with a ttk.Combobox. Carpe weekend, Rich --

Re: Python3-3.7.3: cannot run pdb

On 6/7/2019 12:26 PM, Rich Shepard wrote: Running python3-3.7.3 on Slackware-14.2. $ python3 geochem.py   File "geochem.py", line 35     boxchoices = ttk.Combobox(self, textvariable=med, ^ SyntaxError: invalid syntax An addendum to previous comments solving the issue. In

[issue37201] fix test_distutils failures for Windows ARM64

New submission from Paul Monson : There are a few places where ARM64 is not correctly specified in order for distutils to work for on-target builds using Visual Studio (32-bit x86 emulation). -- components: Tests, Windows messages: 345008 nosy: Paul Monson, paul.moore, steve.dower,

[issue37168] Decimal divisions sometimes 10x or 100x too large

STINNER Victor added the comment: Can you try to reproduce your workflow with Python compiled in debug mode (./configure --with-pydebug)? With Python 3.8, you can now use a debug Python without having to recompile your C extensions :-) -- ___

[issue37151] Calling code cleanup after PEP 590

Change by Evita Cano : -- nosy: +Evita Cano ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

Re: No option available for saving files

On 6/7/2019 10:51 AM, Calvin Spealman wrote: The python shell is good for experimenting and testing some things out, but you are right it isn't for writing programs you actually re-use and run later. You can use any text editor you want, Visual Studio Code and Sublime Text are both popular, but

[issue37196] Allowing arbitrary expressions in the @expression syntax

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37150] Do not allow to pass FileType class object instead of instance in add_argument

Change by miss-islington : -- pull_requests: +13776 pull_request: https://github.com/python/cpython/pull/13901 ___ Python tracker ___

[issue37150] Do not allow to pass FileType class object instead of instance in add_argument

miss-islington added the comment: New changeset 03d5831a2d62c68654ec223168e574cd546efbf6 by Miss Islington (bot) (zygocephalus) in branch 'master': bpo-37150: Throw ValueError if FileType class object was passed in add_argument (GH-13805)

Re: SyntaxError: positional argument follows keyword argument

On Sat, Jun 8, 2019 at 6:01 AM Rich Shepard wrote: > > On Sat, 8 Jun 2019, Chris Angelico wrote: > > > General principle: When you see a syntax error, look *before* that point > > (reading top-to-bottom, left-to-right, same as the parser does). Often, > > the problem is prior to the point where

[issue36964] `python3 -m venv NAME`: virtualenv is not portable

Marco Sulla added the comment: Please Mr. Cannon, can you read my last posts? I think they are not describing a mad idea, but something reasonable. -- nosy: +brett.cannon ___ Python tracker

Re: SyntaxError: positional argument follows keyword argument

On Sat, 8 Jun 2019, Chris Angelico wrote: General principle: When you see a syntax error, look *before* that point (reading top-to-bottom, left-to-right, same as the parser does). Often, the problem is prior to the point where it was actually discovered. Chris, This is why I commented out

[issue37149] link to official documentation tkinter failed !!!

Change by Terry J. Reedy : -- Removed message: https://bugs.python.org/msg344550 ___ Python tracker ___ ___ Python-bugs-list

Re: SyntaxError: positional argument follows keyword argument

On Fri, 7 Jun 2019, Rhodri James wrote: Now we can see that Python isn't complaining about the arguments to tth.Checkbutton. The call to ttk.Checkbutton() is itself a positional argument in the call to LabelInput, coming after the keyword argument "input_var = tk.IntVar". Thank you Rhodri.

[issue37144] tarfile.open: improper handling of path-like object

Terry J. Reedy added the comment: 3.6 only gets security patches. Thanks for testing with 3.7 also. -- nosy: +terry.reedy versions: +Python 3.9 -Python 3.6 ___ Python tracker

[issue37141] Allow multiple separators in Stream.readuntil

Change by Terry J. Reedy : -- stage: -> test needed versions: +Python 3.9 -Python 3.8 ___ Python tracker ___ ___ Python-bugs-list

Re: SyntaxError: positional argument follows keyword argument

On Fri, 7 Jun 2019, Alexandre Brault wrote: The positional argument in question is not one you passed to the ttk.Checkbutton call, but the ttk.Checkbutton itself that you're passing to LabelInput as a positional argument after the input_var keyword argument Alex, Got it, thanks. Now to

[issue37133] Erro "ffi.h: No such file" when build python 3.8 (branch master) on windows 10

Terry J. Reedy added the comment: In command prompt, I see the following, with comments added. f:\dev\3x>PCbuild\build.bat -e # -e should not be needed, but explicitly says to build externals Using py -3.7 (found 3.7 with py.exe) # You must have an installed python to build python.

[issue37200] PyType_GenericAlloc might over-allocate memory

New submission from Neil Schemenauer : In the process of working on some garbage collector/obmalloc experiments, I noticed what seems to be a quirk about PyType_GenericAlloc(). It calls: size = _PyObject_VAR_SIZE(type, nitems+1); Note the "+1" which is documented as "for the sentinel".

[issue37150] Do not allow to pass FileType class object instead of instance in add_argument

Change by Michele Angrisano : -- nosy: +bethard ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37130] pathlib.with_name() doesn't like unnamed files.

Terry J. Reedy added the comment: Welcome to Python. If you end up proposing a change to code or doc, this will end up being the right place. A change to a documented behavior be called an 'enhancement' and only applied to the next version. A doc change will likely be backported.

Re: SyntaxError: positional argument follows keyword argument

On Sat, Jun 8, 2019 at 4:45 AM Rich Shepard wrote: > I've provided only keyword arguments to the call to the ttk.Checkbutton > widget and am not seeing the positional argument that follows. Please show > me what I miss seeing here: > > self.inputs['nondetect'] = LabelInput( > self,

[issue37129] Add os.RWF_APPEND flag for os.pwritev

New submission from Terry J. Reedy : Issues need a more complete title and at least *some* explanation. -- nosy: +terry.reedy title: Add RWF_APPEND flag -> Add os.RWF_APPEND flag for os.pwritev versions: +Python 3.9 -Python 3.8 ___ Python tracker

Re: SyntaxError: positional argument follows keyword argument

On 2019-06-07 2:43 p.m., Rich Shepard wrote: > I understand positional and keyword arguments and the syntax for the > ttk.Checkbutton as described on > . > > $ python3 geochem.py >   File "geochem.py", line 60 >    

Re: SyntaxError: positional argument follows keyword argument

On 07/06/2019 19:43, Rich Shepard wrote: I understand positional and keyword arguments and the syntax for the ttk.Checkbutton as described on . $ python3 geochem.py   File "geochem.py", line 60     ttk.Checkbutton(text='Censored?',

SyntaxError: positional argument follows keyword argument

I understand positional and keyword arguments and the syntax for the ttk.Checkbutton as described on . $ python3 geochem.py File "geochem.py", line 60 ttk.Checkbutton(text='Censored?', variable=input_var), ^ SyntaxError: positional

[issue37195] test_utime fails on MacOS Mojave (Kernel Version 18.6.0:)

Pablo Galindo Salgado added the comment: > WHat kind of file system is @test_28886_tmp/f1 created on? Apple_APFS -- ___ Python tracker ___

[issue21492] email.header.decode_header sometimes returns bytes, sometimes str

Change by Terry J. Reedy : -- versions: +Python 3.7, Python 3.8, Python 3.9 -Python 3.3 ___ Python tracker ___ ___ Python-bugs-list

[issue37195] test_utime fails on MacOS Mojave (Kernel Version 18.6.0:)

Pablo Galindo Salgado added the comment: I will test this on other laptops to try to "bisect" configuration-wise, but for my investigation so far, it seems that the value in the (STRUCT_STAT) st->st_atime is directly wrong (is 1559932701 when the test fails and 1 when the test succeeds).

[issue37195] test_utime fails on MacOS Mojave (Kernel Version 18.6.0:)

Ned Deily added the comment: WHat kind of file system is @test_28886_tmp/f1 created on? -- ___ Python tracker ___ ___

[issue37176] super() docs don't say what super() does

Raymond Hettinger added the comment: Please make a concrete proposal (a PR or somesuch). That will make it much easier to determine whether a particular bit of word-smithing is a improvement. Of the issues discussed so far, these are the most promising: * Document how the zero argument form

[issue37138] PEP 590 method_vectorcall calls memcpy with NULL src

Gregory P. Smith added the comment: Thanks Jeroen! -- resolution: -> fixed stage: patch review -> commit review status: open -> closed ___ Python tracker ___

[issue37138] PEP 590 method_vectorcall calls memcpy with NULL src

miss-islington added the comment: New changeset 6e053079ac3fe50ffbe9128bcf766298168c31cb by Miss Islington (bot) in branch '3.8': bpo-37138: fix undefined behaviour with memcpy() on NULL array (GH-13867) https://github.com/python/cpython/commit/6e053079ac3fe50ffbe9128bcf766298168c31cb

[issue37189] PyRun_String not exported in python38.dll

Zachary Ware added the comment: A look through `git log -p` looks like bpo-34646 is likely to be related. -- nosy: +benjamin.peterson ___ Python tracker ___

[issue37181] fix test_regrtest failures on Windows arm64

miss-islington added the comment: New changeset 84d47bd8ad48f29ed5d333f4307408ad1e081f59 by Miss Islington (bot) in branch '3.8': bpo-37181: Fix test_regrtest failures on Windows arm64 (GH-13872) https://github.com/python/cpython/commit/84d47bd8ad48f29ed5d333f4307408ad1e081f59 --

[issue13501] Make libedit support more generic; port readline / libedit to FreeBSD

Gregory P. Smith added the comment: In PR it you refer to -ledit and to editline. libedit and libeditline appear to be two different libraries. I was under the impression that libedit is the desirable one (it's what *BSD uses - coming originally from NetBSD if I understand correctly -

[issue37195] test_utime fails on MacOS Mojave (Kernel Version 18.6.0:)

Carol Willing added the comment: @pablogsal My debug info looks similar to yours other than shell/terminal preferences. Similar specs on HW and OS. ./python.exe -m test test_os -R : -v Any other configs that you are frequently seeing the failures? --

[issue37189] PyRun_String not exported in python38.dll

Christoph Gohlke added the comment: `PyRun_String` was exported at least since `python23.dll`. Python.Net relies on it at -- ___ Python tracker

[issue37195] test_utime fails on MacOS Mojave (Kernel Version 18.6.0:)

Pablo Galindo Salgado added the comment: Ok, this is the failure once I investigated with pdb: (Pdb) filename '@test_28886_tmp/f1' (Pdb) atime_ns 1002003000 (Pdb) mtime_ns 4005006000 (Pdb) set_time(filename, (atime_ns, mtime_ns)) (Pdb) st = os.stat(filename) (Pdb) st.st_atime, st.st_mtime

[issue37168] Decimal divisions sometimes 10x or 100x too large

Phil Frost added the comment: I'm afraid that won't be of much use since the object is statically allocated. Besides, the trouble isn't finding what created the object, but what mutated an int object which should be immutable. -- ___ Python

[issue13501] Make libedit support more generic; port readline / libedit to FreeBSD

Change by Gregory P. Smith : -- nosy: +gregory.p.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37195] test_utime fails on MacOS Mojave (Kernel Version 18.6.0:)

Pablo Galindo Salgado added the comment: > For some reason, the files created for this test has a very weird inode > information. Ok, disregard what I am saying, that's actually part of the test. But I think this is related to the failure. I keep investigating. --

[issue37195] test_utime fails on MacOS Mojave (Kernel Version 18.6.0:)

Pablo Galindo Salgado added the comment: For some reason, the files created for this test has a very weird inode information: ❯ ll test_python_**/**/f* -rw-r--r-- 1 pgalindo3 staff 7B 1 Jan 1970 test_python_26370/@test_26370_tmp/f1 -- ___

[issue37195] test_utime fails on MacOS Mojave (Kernel Version 18.6.0:)

Change by Pablo Galindo Salgado : -- Removed message: https://bugs.python.org/msg344983 ___ Python tracker ___ ___ Python-bugs-list

[issue37138] PEP 590 method_vectorcall calls memcpy with NULL src

Gregory P. Smith added the comment: New changeset 1f9531764cc0f8dbca1d8f429d162dc28282f4b4 by Gregory P. Smith (Jeroen Demeyer) in branch 'master': bpo-37138: fix undefined behaviour with memcpy() on NULL array (GH-13867)

[issue36742] CVE-2019-10160: urlsplit NFKD normalization vulnerability in user:password@

Riccardo Schirone added the comment: The fix for python-2.7 (https://github.com/python/cpython/pull/13815/files#diff-b577545d73dd0cdb2c337a4c5f89e1d7R183) causes errors when netloc contains characters that can't be encoded by 'ascii' codec. You can see it by doing: >>> netloc =

[issue37181] fix test_regrtest failures on Windows arm64

Change by miss-islington : -- pull_requests: +13774 pull_request: https://github.com/python/cpython/pull/13899 ___ Python tracker ___

[issue37138] PEP 590 method_vectorcall calls memcpy with NULL src

Change by miss-islington : -- pull_requests: +13775 pull_request: https://github.com/python/cpython/pull/13900 ___ Python tracker ___

[issue37189] PyRun_String not exported in python38.dll

Steve Dower added the comment: Guessing Victor may have touched something in this area. Was it exported before? Or did we just have a macro for it? Maybe the macro was moved to an internal header by mistake? -- nosy: +vstinner ___ Python tracker

Re: Python3-3.7.3: cannot run pdb

On Fri, 7 Jun 2019, Danilo Coccia wrote:     self.inputs['medium'] = LabelInput(     self, 'Medium',     med = tk.StringVar() ^^^ Missing a comma here! Thanks, Danilo! When we write the code we too often see

[issue37195] test_utime fails on MacOS Mojave (Kernel Version 18.6.0:)

Pablo Galindo Salgado added the comment: The problem is that one of the filenames that the test creates has this inode information for some mysterious reason: ❯ ll @test_25508_tmp/f1 -rw-r--r-- 1 pgalindo3 staff 7B 1 Jan 1970 @test_25508_tmp/f1 --

[issue37181] fix test_regrtest failures on Windows arm64

New submission from Steve Dower : New changeset e7e5039d6940e41839dcef0433262ff363408dad by Steve Dower (Paul Monson) in branch 'master': bpo-37181: Fix test_regrtest failures on Windows arm64 (GH-13872) https://github.com/python/cpython/commit/e7e5039d6940e41839dcef0433262ff363408dad

Re: Python3-3.7.3: cannot run pdb

On 2019-06-07 18:31, Rich Shepard wrote: On Fri, 7 Jun 2019, MRAB wrote: It's possible that the error is actually on the previous line and that it thinks that what's on line 35 is a continuation of what's on line 34, but it isn't. MRAB, If that's the case I'm missing seeing the error. Here

Re: Python3-3.7.3: cannot run pdb

On Fri, 7 Jun 2019, Rhodri James wrote: The syntax error causes Python to halt before it has finished compiling your program into byte code. There is nothing to run pdb on! Okay. That certainly makes sense. It's been a very long time since I did any Python coding. Regards, Rich --

[issue37195] test_utime fails on MacOS Mojave (Kernel Version 18.6.0:)

Pablo Galindo Salgado added the comment: The failure tends to be very reliable when running with -R, running the test in isolation or only one time normally succeeds. I will try to investigate more. The hardware is a MacBook Pro with Mojave 10.14.5, 2.2 GHz Intel Core i7 and 16 GB 2400 MHz

[issue37195] test_utime fails on MacOS Mojave (Kernel Version 18.6.0:)

Pablo Galindo Salgado added the comment: Python debug information CC.version: Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 Py_DEBUG: Yes (sys.gettotalrefcount() present) _decimal.__libmpdec_version__:

Re: Python3-3.7.3: cannot run pdb

Il 07/06/2019 19:31, Rich Shepard ha scritto: > On Fri, 7 Jun 2019, MRAB wrote: > >> It's possible that the error is actually on the previous line and that it >> thinks that what's on line 35 is a continuation of what's on line 34, but >> it isn't. > > MRAB, > > If that's the case I'm missing

[issue37195] test_utime fails on MacOS Mojave (Kernel Version 18.6.0:)

Carol Willing added the comment: Confirming that they do pass on my Mojave system. test_utime (test.test_os.UtimeTests) ... ok test_utime_by_indexed (test.test_os.UtimeTests) ... ok ... test_utime_dir_fd (test.test_os.UtimeTests) ... ok Though I did have to go through some shenanigans

Re: Python3-3.7.3: cannot run pdb

On 07/06/2019 18:28, Rich Shepard wrote: On Fri, 7 Jun 2019, Peter Otten wrote: You need to fix all syntax errors before you can run the script, with or without pdb. Peter, I thought the debugger would show me the location of the syntax error. The syntax error causes Python to halt before

[issue37175] make install: make compileall optional

Ned Deily added the comment: In many installations, the user running Python would not have write access to the lib directory tree where the compiled byte files need to be created so we would not want to change the current default behavior. On the other hand, I could see some times when

Re: Python3-3.7.3: cannot run pdb

On Fri, 7 Jun 2019, MRAB wrote: It's possible that the error is actually on the previous line and that it thinks that what's on line 35 is a continuation of what's on line 34, but it isn't. MRAB, If that's the case I'm missing seeing the error. Here are the lines prior to and including line

[issue37186] Everyone uses GIL wrong! = DEADLOCK

Eric Snow added the comment: The situation with subinterpreters and the gilstate API is a known problem (see issues #10915 and #15751). We plan on fixing that in the near future for 3.9 (and probably for 3.8). Feel free to chime in on those earlier issues. Note that the subinterpreter

[issue18299] Change script_helper to use universal_newlines=True in _assert_python

STINNER Victor added the comment: I dislike script_helper API. I doesn't allow to pass arbitrary keyword parameters to subprocess.Popen. IMHO a new API should be added, but I didn't check if script_helper already contains such API or not. -- ___

Re: Python3-3.7.3: cannot run pdb

On Fri, 7 Jun 2019, Peter Otten wrote: You need to fix all syntax errors before you can run the script, with or without pdb. Peter, I thought the debugger would show me the location of the syntax error. The syntax error you are seeing is typically caused by unclosed parentheses in a line

[issue15751] Support subinterpreters in the GIL state API

Change by Eric Snow : -- versions: +Python 3.8, Python 3.9 -Python 3.6 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue10915] Make the PyGILState API compatible with multiple interpreters

Change by Eric Snow : -- versions: +Python 3.9 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36742] CVE-2019-10160: urlsplit NFKD normalization vulnerability in user:password@

STINNER Victor added the comment: CVE-2019-10160 has been assigned by Red Hat to this flaw. -- ___ Python tracker ___ ___

[issue36742] CVE-2019-10160: urlsplit NFKD normalization vulnerability in user:password@

Change by STINNER Victor : -- title: urlsplit doesn't accept a NFKD hostname with a port number -> CVE-2019-10160: urlsplit NFKD normalization vulnerability in user:password@ ___ Python tracker

[issue37199] Test suite fails when Ipv6 is unavailable

Change by STINNER Victor : -- nosy: +vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37180] Fix Persian KAF in mac_farsi.py

SilentGhost added the comment: Ramin, I agree with Victor, if you have any information contrary to what we posted, please feel free to post it here so that we can consider re-opening the issue. -- resolution: -> not a bug stage: patch review -> resolved status: open -> closed

[issue37195] test_utime fails on MacOS Mojave (Kernel Version 18.6.0:)

Ned Deily added the comment: Also, what utime* results show up in ./configure output? I see checking utime.h usability... yes checking utime.h presence... yes checking for utime.h... yes -- ___ Python tracker

[issue37199] Test suite fails when Ipv6 is unavailable

New submission from N.P. Khelili : The test suite does not handle an OS that does not have IPv6. When Linux kernel is started with argument: ipv6.disable=1 The test suite fails. ( See attached file ) 5 tests failed: test_asyncio test_imaplib test_importlib test_socket test_zipapp

[issue37195] test_utime fails on MacOS Mojave (Kernel Version 18.6.0:)

Ned Deily added the comment: FWIW, it doesn't fail for me and I don't recall ever seeing a failure like this on macOS. What hardware? ./python.exe -m test.pythoninfo please! -- nosy: +ned.deily ___ Python tracker

[issue15913] Add PyBuffer_SizeFromFormat() C helper for struct.calcsize()

Change by STINNER Victor : -- title: PyBuffer_SizeFromFormat is missing -> Add PyBuffer_SizeFromFormat() C helper for struct.calcsize() versions: +Python 3.9 -Python 3.6 ___ Python tracker

Re: Python3-3.7.3: cannot run pdb

On 2019-06-07 17:26, Rich Shepard wrote: Running python3-3.7.3 on Slackware-14.2. I'm trying to debug a module using pdb but failing with all attempts. For example, using breakpoint() at the line where I want to stop the running module and examine each line's execution, the program runs to

  1   2   3   >