Re: [Python-Dev] About [].append == [].append

On 6/23/2018 4:54 AM, Serhiy Storchaka wrote: 23.06.18 10:27, Jeroen Demeyer пише: On 2018-06-23 03:50, Steven D'Aprano wrote: I think it is more important that builtin methods and Python methods behave the same. +1 This inconsistency is the *real* problem here. It's one little extra

Re: [Python-Dev] We now have C code coverage!

On 6/22/2018 8:43 PM, Terry Reedy wrote: On 6/22/2018 6:21 PM, Brett Cannon wrote: Thanks to a PR from Ammar Askar we now run Python under lcov as part of the code coverage build. And thanks to codecov.io <http://codecov.io> automatically merging code coverage reports we get a complete

Re: [Python-Dev] We now have C code coverage!

On 6/22/2018 6:21 PM, Brett Cannon wrote: Thanks to a PR from Ammar Askar we now run Python under lcov as part of the code coverage build. And thanks to codecov.io automatically merging code coverage reports we get a complete report of our coverage (the first results of

Re: [Python-Dev] PySequence_Check but no __len__

On 6/22/2018 7:57 PM, Greg Ewing wrote: Terry Reedy wrote: I am surprised that a C-API function calls something a 'sequence' without it having __len__. It's a bit strange that PySequence_Check exists at all. The principle of duck typing would suggest that one should be checking

Re: [Python-Dev] PySequence_Check but no __len__

On 6/22/2018 7:17 AM, Christian Tismer wrote: My problem is to find out how to deal with a class which has __getitem__ but no __len__. The documentation suggests that the length of a sequence can always be obtained by len(). https://docs.python.org/3/reference/datamodel.html It says that

Re: [Python-Dev] Reminder: Please elaborate commit messages

On 5/22/2018 2:26 PM, Yury Selivanov wrote: On Tue, May 22, 2018 at 8:52 AM Victor Stinner wrote: Usually, I don't open a new bug to fix or enhance a test. So I wouldn't say that it's mandatory. It's really on a case by case basis. It seems like test_asyncio failures

Re: [Python-Dev] Reminder: Please elaborate commit messages

On 5/22/2018 8:37 AM, Andrew Svetlov wrote: Sorry for that. I thought that the bpo issue can be skipped because it is tests-only change, no asyncio code was affected. Will be more accurate next time. A new issue was not needed. Adding 'bpo-33531' would have been fine, automatically linking

Re: [Python-Dev] please help triage VSTS failures

On 5/18/2018 4:13 PM, Steve Dower wrote: Close/reopen PR is the best way to trigger a rebuild right now. It may be the way to retrigger VSTS, but if one want to merge, and either of Travis or AppVeyor pass, tossing the success is a foolish thing to do. Either may fail on a rebuild. --

Re: [Python-Dev] What is the rationale behind source only releases?

On 5/16/2018 11:46 PM, Alex Walters wrote: This is actually the heart of the reason I asked the question. CI tools are fairly good now. If the CI tools could be used in such a way to make the building of binary artifacts less of a burden on the release managers, would there be interest in

Re: [Python-Dev] bpo-33257: seeking advice & approval on the course of action

On 5/14/2018 12:20 PM, Chris Barker via Python-Dev wrote: On Wed, May 2, 2018 at 8:21 PM, Terry Reedy <tjre...@udel.edu <mailto:tjre...@udel.edu>> wrote: On 5/2/2018 4:38 PM, Ivan Pozdeev via Python-Dev wrote: The bottom line is: Tkinter is currently broken This

Re: [Python-Dev] Dealing with tone in an email

On 5/6/2018 10:03 AM, Chris Angelico wrote: On Sun, May 6, 2018 at 6:54 PM, Terry Reedy <tjre...@udel.edu> wrote: Is it ALL of Tkinter that fails in threaded mode? No. It is non-threaded tcl that fails in threaded mode, along with tkinter's attempt to make non-thread tcl work

Re: [Python-Dev] Use a queue in Tkinter (was: Dealing with tone in an email)

On 5/6/2018 8:51 AM, Stefan Krah wrote: Steven D'Aprano wrote: What exactly didn't work? I don't understand. https://bugs.python.org/issue33412 Isn't the standard solution to use a queue for updating the GUI? At least I didn't have any problems at all with my one TKinter app, I think the

Re: [Python-Dev] Dealing with tone in an email

On 5/5/2018 9:45 PM, Chris Angelico wrote: On Sun, May 6, 2018 at 11:39 AM, Steven D'Aprano wrote: On Sun, May 06, 2018 at 11:09:21AM +1000, Chris Angelico wrote: What exactly didn't work? I don't understand. https://bugs.python.org/issue33412 I've read it and I

Re: [Python-Dev] A fast startup patch (was: Python startup time)

On 5/5/2018 2:33 PM, Toshio Kuratomi wrote: On Sat, May 5, 2018, 10:40 AM Eric Fahlgren > wrote: On Sat, May 5, 2018 at 10:30 AM, Toshio Kuratomi >wrote: On Fri, May 4,

Re: [Python-Dev] Process to remove a Python feature

On 5/4/2018 6:18 PM, Victor Stinner wrote: 2018-05-04 23:59 GMT+02:00 Terry Reedy <tjre...@udel.edu>: Would it be possible (and sensible) to use the 2to3 machinery to produce 36to37.py, etc., to do mechanical replacements when possible and flag other things when necessary? I sugge

Re: [Python-Dev] Dealing with tone in an email

On 5/4/2018 10:07 PM, Steven D'Aprano wrote: Terry, please, to persist in attacking Ivan's past behaviour when he has not repeated it is not open, considerate or respectful. I did not do that. My first sentence was background for a *discussion* about a partial disagreement with what you

Re: [Python-Dev] Process to remove a Python feature

On 5/2/2018 5:11 AM, Victor Stinner wrote: As a follow-up to the "[Python-Dev] (Looking for) A Retrospective on the Move to Python 3" thread, I will like to clarify how a feature should be removed from Python. Would it be possible (and sensible) to use the 2to3 machinery to produce

Re: [Python-Dev] Dealing with tone in an email

On 5/4/2018 12:04 PM, Guido van Rossum wrote: Thank you Steven! I'd like to use your email (nearly) verbatim to start off the discussion about civility we're going to have at the Language Summit. I won't be there but sounds like a good idea. I hope you consider that bad content as well as

Re: [Python-Dev] Dealing with tone in an email

On 5/4/2018 11:43 AM, Steven D'Aprano wrote: I'm not defending Ivan's initial email. His tantrum *was* annoying, unreasonable, and unfair to those who do care about tkinter. Ivan's email was a disinformation troll intended to jump the attention queue of core developers. He is proud of its

Re: [Python-Dev] Dealing with tone in an email

On 5/3/2018 2:45 PM, Ivan Pozdeev via Python-Dev wrote: Let me express things right from the horse's mouth. Ditto, as the only person who responded on the tracker before you posted here and the only person other that Guido to respond on the tracker since and the only person to collect data

Re: [Python-Dev] Python startup time

On 5/2/2018 12:42 PM, Gregory Szorc wrote: I know this kinda/sorta exists with zipimporter. But zipimporter uses zlib (slow) and only allows .py/.pyc files. And I think some Python application distribution tools have also solved this problem. I'd *really* like to see a proper/robust solution

Re: [Python-Dev] Drop/deprecate Tkinter?

On 5/2/2018 6:01 PM, Antoine Pitrou wrote: On Wed, 2 May 2018 22:54:04 +0100 Paul Moore wrote: His *other* email seems reasonable, and warrants a response, yes. But are we to take the suggestion made here (to drop tkinter) seriously, based on the fact that there's a

Re: [Python-Dev] Drop/deprecate Tkinter?

On 5/2/2018 4:51 PM, Ivan Pozdeev via Python-Dev wrote: As https://bugs.python.org/issue33257 As I report there, the 'crasher' does not crash on my Win 10 with either installed 3.7 or built 3.8. https://bugs.python.org/issue33316 showed, nothing about tkinter Tkinter is broken, for both

Re: [Python-Dev] bpo-33257: seeking advice & approval on the course of action

On 5/2/2018 4:38 PM, Ivan Pozdeev via Python-Dev wrote: The bottom line is: Tkinter is currently broken This is way over-stated. Many modules have bugs, somethings in features more central to their main purpose. -- as in, it's not thread-safe (in both Py2 and Py3) Meaning that tkinter

Re: [Python-Dev] Every Release Can Be a Mini "Python 4000", Within Reason (was (name := expression) doesn't fit the narrative of PEP 20)

On 4/30/2018 4:00 PM, Jeff Allen wrote: They were not "statements", but "formulas" while '=' was assignment (sec 8) *and* comparison (sec 10B). So conversely to our worry, they actually wanted users to think of assignment initially as a mathematical formula (page 2) in order to exploit the

Re: [Python-Dev] Every Release Can Be a Mini "Python 4000", Within Reason (was (name := expression) doesn't fit the narrative of PEP 20)

On 4/29/2018 11:51 PM, Guido van Rossum wrote: On Sun, Apr 29, 2018 at 10:45 AM, Eitan Adler > wrote: On 29 April 2018 at 01:34, Jeff Allen > wrote: > On 27/04/2018 08:38, Greg Ewing

Re: [Python-Dev] PEP 572: Why not := as standard assignment operator?

On 4/26/2018 11:38 AM, Gustavo Carneiro wrote: On Thu, Apr 26, 2018 at 11:13 PM, Martin Teichmann > wrote: > when reading PEP 572 I actually liked it a lot - I think it's actually > a cool idea. I think it's actually that

Re: [Python-Dev] (name := expression) doesn't fit the narrative of PEP 20

On 4/26/2018 6:34 AM, Greg Ewing wrote: Antoine Pitrou wrote: Well, how do languages where assignment is an expression returning the assigned value make their REPLs work?  I'm sure they don't inflict that on their users, so it's certainly a solvable problem. I can't think of any such language

Re: [Python-Dev] (name := expression) doesn't fit the narrative of PEP 20

On 4/26/2018 6:20 AM, Steve Holden wrote: On Thu, Apr 26, 2018 at 8:56 AM, Steven D'Aprano <st...@pearwood.info <mailto:st...@pearwood.info>> wrote: On Thu, Apr 26, 2018 at 03:31:13AM -0400, Terry Reedy wrote: > On 4/25/2018 8:20 PM, Chris Angelico wrote: > >

Re: [Python-Dev] (name := expression) doesn't fit the narrative of PEP 20

On 4/25/2018 8:20 PM, Chris Angelico wrote: On Thu, Apr 26, 2018 at 10:11 AM, Yury Selivanov wrote: Just yesterday this snippet was used on python-dev to show how great the new syntax is: my_func(arg, buffer=(buf := [None]*get_size()), size=len(buf)) What

Re: [Python-Dev] PEP 572: Write vs Read, Understand and Control Flow

On 4/25/2018 6:10 AM, Steve Holden wrote: On Wed, Apr 25, 2018 at 4:56 AM, Tim Peters > wrote: [Tim] >> Binding expressions are debugger-friendly in that they _don't_ just >> vanish without a trace.  It's their purpose to _capture_

Re: [Python-Dev] PEP 572: Assignment Expressions

On 4/17/2018 1:03 PM, Yury Selivanov wrote: Using inline assignments in "while" statements is neat, but how often do we use "while" statements? Beginners commonly write game and entry loops and commonly stumble over the need to write an infinite loop and a half. The evidence is on both

Re: [Python-Dev] PEP 572: Assignment Expressions

On 4/17/2018 3:46 AM, Chris Angelico wrote: Abstract This is a proposal for creating a way to assign to names within an expression. I started at -something as this is nice but not necessary. I migrated to +something for the specific, limited proposal you wrote above: expressions

Re: [Python-Dev] Basic test to validate win10 install?

On 4/16/2018 6:00 PM, Martin Gainty wrote: I was told the python -m test are for devs only to test "auxiliary functions" People say all sorts of nonsense. I don't know what 'auxiliary function' would mean in this context. The Windows installer optionally installs the tests so that users

Re: [Python-Dev] gdb support could use some love

On 4/5/2018 5:47 AM, Skip Montanaro wrote: There are a bunch of open issues regarding gdb support including one with a PR in need of review for 3.6+. I rejected one (which assumed everyone now uses a python-aware gdb), commented on another (ceval.c-related name changes in several commands),

Re: [Python-Dev] IDLE colorizer

On 4/1/2018 10:20 PM, Tim Peters wrote: [MRAB [ A thread on python-ideas is talking about the prefixes of string literals, and the regex used in IDLE. Line 25 of Lib\idlelib\colorizer.py is: stringprefix = r"(?i:\br|u|f|fr|rf|b|br|rb)?" which looks slightly

Re: [Python-Dev] Subtle difference between f-strings and str.format()

On 3/30/2018 6:29 AM, Serhiy Storchaka wrote: 29.03.18 18:06, Terry Reedy пише: On 3/28/2018 11:27 AM, Serhiy Storchaka wrote: The optimizer already changes semantic. Non-optimized "if a and True:" would call bool(a) twice, but optimized code calls it only once. Perhaps Ref 3.

Re: [Python-Dev] Subtle difference between f-strings and str.format()

On 3/28/2018 11:27 AM, Serhiy Storchaka wrote: The optimizer already changes semantic. Non-optimized "if a and True:" would call bool(a) twice, but optimized code calls it only once. Perhaps Ref 3.3.1 object.__bool__ entry, after " should return False or True.", should say something like

Re: [Python-Dev] PEP 574 -- Pickle protocol 5 with out-of-band data

On 3/28/2018 9:15 PM, Nathaniel Smith wrote: There's obviously some tension here between pickle's use as a persistent storage format, and its use as a transient wire format. For the former, you definitely can't store code objects because there's no forwards- or backwards-compatibility guarantee

Re: [Python-Dev] ttk.Treeview.insert() does not allow to insert item with iid=0

On 3/16/2018 6:54 AM, Игорь Яковченко wrote: This might fit python-list better, and may become a bugs.python.org issue, but I will answer now, having just investigated. I found a possible bug with ttk.Treeview widget. See below. I'm working on program that uses tkinter UI. I use

Re: [Python-Dev] Python 2.7 -- bugfix or security before EOL?

On 3/14/2018 9:16 AM, Michael Scott Cuthbert wrote: I’m guessing my first message was unclear or able to be misunderstood in some part — I’m one of the frequent contributors to python3statement.org and have moved my own Python projects to Py3 only (the main one,

Re: [Python-Dev] Git hub : CLA Not Signed label

On 3/11/2018 3:34 AM, Matěj Cepl wrote: On 2018-03-11, 03:45 GMT, Terry Reedy wrote: When processed properly, a day to a week, usually, a * will appear after your name on any tracker (bpo) post. So, I got my start after the name, where is the list of maintainers of individual packages, so I

Re: [Python-Dev] Git hub : CLA Not Signed label

On 3/10/2018 9:58 PM, Anthony Flury via Python-Dev wrote: All, I submitted two Pull Requests last Sunday, only a few hours after I signed the CLA. When processed properly, a day to a week, usually, a * will appear after your name on any tracker (bpo) post. I understand why the 'Knights who

Re: [Python-Dev] Python 2.7 -- bugfix or security before EOL?

On 3/10/2018 8:54 PM, Guido van Rossum wrote: Let's not play games with semantics. The way I see the situation for 2.7 is that EOL is January 1st, 2020, and there will be no updates, not even source-only security patches, after that date. Support (from the core devs, the PSF, and python.org

Re: [Python-Dev] Python 2.7 -- bugfix or security before EOL?

On 3/10/2018 4:59 PM, Michael Scott Cuthbert wrote: I notice on https://devguide.python.org that Python 3.5 is in “security” status with an EOL of 2020-09-13 but Python 2.7 is in “bugfix” and has a likely earlier EOL. There is no relation between the two, or between 2.7 and any other

Re: [Python-Dev] Backward incompatible change about docstring AST

On 2/27/2018 9:32 AM, Serhiy Storchaka wrote: 27.02.18 15:37, INADA Naoki пише: Of course, this change was backward incompatible. Tools reading/writing docstring via AST will be broken by this change. For example, it broke PyFlakes, and PyFlakes solved it already.

Re: [Python-Dev] How is the GitHub workflow working for people?

On 2/20/2018 8:58 PM, Brett Cannon wrote: It's been a year and 10 days since we moved to GitHub, so I figured now is as good a time as any to ask people if they are generally happy with the workflow ***The nearly automatic backporting!!! A responsible human *should* check backport PRs, as

Re: [Python-Dev] Update tcl/tk to 8.6.latest on Windows?

On 2/21/2018 5:22 AM, Serhiy Storchaka wrote: 21.02.18 12:12, Terry Reedy пише: 3.7.0b1 Windows installer installs tcl/tk 8.6.6, which is a couple of years old.  Same for Windows repository builds.  I believe the MacOS installer shipped with something later.  Can we update Windows

[Python-Dev] Update tcl/tk to 8.6.latest on Windows?

3.7.0b1 Windows installer installs tcl/tk 8.6.6, which is a couple of years old. Same for Windows repository builds. I believe the MacOS installer shipped with something later. Can we update Windows to the current 8.6.8? -- Terry Jan Reedy ___

Re: [Python-Dev] Dataclasses and correct hashability

On 2/5/2018 2:28 AM, Glenn Linderman wrote: This is an interesting use case. I haven't got the internals knowledge to know just how just different mutable and immutable classes and objects are under the hood. I believe there is no internal difference. An object is immutable if there is not

Re: [Python-Dev] Is 4.0 a major breaking changes release?

On 2/3/2018 5:50 PM, Zachary Ware wrote: On Sat, Feb 3, 2018 at 4:40 PM, Alex Walters wrote: I am still working on porting code from 2.x to 3.x. As of late on the lists I've seen comments about making somewhat major changes in 4.0 - now I'm concerned that I should

Re: [Python-Dev] A minimal Python interpreter written in Python for experimenting with language changes

On 2/2/2018 7:01 PM, asrp asrp wrote: I don't know if this is the right place to post this. Please redirect as needed. This list is for development *of* cpython. Development *with* python in general belongs on python-list. -- Terry Jan Reedy

Re: [Python-Dev] Is object the most base type? (bpo-20285)

On 2/2/2018 1:53 AM, Terry Reedy wrote: >>> object.__doc__ 'The most base type' I and several people on python-list thread "interactive help on the base object" (Dec   2013) thought this could be improved.  On https://bugs.python.org/issue20285 and https://github.com/pytho

[Python-Dev] Is object the most base type? (bpo-20285)

>>> object.__doc__ 'The most base type' I and several people on python-list thread "interactive help on the base object" (Dec 2013) thought this could be improved. On https://bugs.python.org/issue20285 and https://github.com/python/cpython/pull/4759 After some research, I believe the

Re: [Python-Dev] OS-X builds for 3.7.0

On 1/31/2018 6:23 PM, Chris Barker wrote: On Wed, Jan 31, 2018 at 4:20 AM, INADA Naoki > wrote: > Against the official CPython 3.6 (probably .3 or .4) release I see: > 1 that is 2.01x faster (python-startup, 24.6ms down to 12.2ms)

Re: [Python-Dev] Why is Python for Windows compiled with MSVC?

On 1/31/2018 10:04 AM, Oleg Sivokon wrote: Why did you choose to use non-free compiler, which also makes cross-compilation impossible? There wasn't really a reason not to choose MinGW as Python was ported to DOS years before the initial 1998 release of the mingw32 predecessor. There has

Re: [Python-Dev] Making "-j0" the default setting for the test suite?

On 1/28/2018 11:30 PM, Nick Coghlan wrote: On my current system, "make test" runs in around 3 minutes, while "./python -m test" runs in around 16 minutes. And that's with "make test" actually running more tests (since it enables several of the "-u" options). Did you test with current 3.7.0a+,

Re: [Python-Dev] Making "-j0" the default setting for the test suite?

On 1/28/2018 11:43 PM, Guido van Rossum wrote: So why can't you just run "make test" if that's faster? Not a standard option on Windows ;-). On Sun, Jan 28, 2018 at 8:30 PM, Nick Coghlan > wrote: On my current system, "make test" runs in

Re: [Python-Dev] GH-NNNN vs #NNNN in merge commit

On 1/25/2018 10:38 PM, Brett Cannon wrote: On Thu, 25 Jan 2018 at 17:33 Eric V. Smith <e...@trueblade.com <mailto:e...@trueblade.com>> wrote: On 1/25/2018 8:13 PM, Terry Reedy wrote: > On 1/25/2018 7:47 PM, Mariatta Wijaya wrote: >> I think we're sta

Re: [Python-Dev] GH-NNNN vs #NNNN in merge commit

On 1/25/2018 7:47 PM, Mariatta Wijaya wrote: I think we're starting to deviate from the original topic here which is: please replace # with GH- when you click Squash & Merge button. I will try to remember to do this, although it seems pointless if most people do not. The idea of the

Re: [Python-Dev] GH-NNNN vs #NNNN in merge commit

On 1/25/2018 4:34 PM, Berker Peksağ wrote: On Fri, Jan 26, 2018 at 12:09 AM, Terry Reedy <tjre...@udel.edu> wrote: On 1/25/2018 1:53 PM, Brett Cannon wrote: I would assume it would just go into miss-islington, but before we get ahead of ourselves and design this we need to get con

Re: [Python-Dev] GH-NNNN vs #NNNN in merge commit

On 1/25/2018 4:22 PM, Berker Peksağ wrote: On Thu, Jan 25, 2018 at 11:50 PM, Terry Reedy <tjre...@udel.edu> wrote: On 1/25/2018 1:03 PM, Mariatta Wijaya wrote: One idea is maybe have a bot to do the squash commit, for example by commenting on GitHub: @merge-bot merge So core devs

Re: [Python-Dev] GH-NNNN vs #NNNN in merge commit

On 1/25/2018 1:53 PM, Brett Cannon wrote: I would assume it would just go into miss-islington, but before we get ahead of ourselves and design this we need to get consensus that people like the overall idea of using a bot to do a main commits as well. I strongly dislike any idea of making me

Re: [Python-Dev] GH-NNNN vs #NNNN in merge commit

On 1/25/2018 1:03 PM, Mariatta Wijaya wrote: One idea is maybe have a bot to do the squash commit, for example by commenting on GitHub: @merge-bot merge So core devs can do the above instead of pressing the commit button. Any thoughts on this? I can hardly believe that you are seriously

Re: [Python-Dev] Exposing different versions of a system call in Python

On 1/19/2018 11:06 PM, Nick Coghlan wrote: On 20 January 2018 at 02:32, Random832 wrote: On Fri, Jan 19, 2018, at 04:28, Pablo Galindo Salgado wrote: On the other side, we have pipe and pipe2 as an example of exposing two versions when this situation happens. The

Re: [Python-Dev] Positional-only parameters in Python

On 1/19/2018 4:49 PM, Mario Corchero wrote: I am happy to put some work into this (and Pablo Galindo in CC offered to pair on it) but it is not clear for me whether the next step is drafting a new PEP or this is just blocked on "re-evaluating" the current one. If someone can clarify we can

Re: [Python-Dev] Drop support for old unsupported FreeBSD and Linux kernels?

On 1/19/2018 1:04 AM, Nathaniel Smith wrote: On Thu, Jan 18, 2018 at 12:27 PM, Victor Stinner wrote: CPython still has compatibility code for Linux 2.6, whereas the support of Linux 2.6.x ended in August 2011, longer than 6 years ago. Should we also drop support for

Re: [Python-Dev] Python 3.7: Require OpenSSL >=1.0.2 / LibreSSL >= 2.5.3

On 1/13/2018 3:02 PM, Brett Cannon wrote: On Sat, Jan 13, 2018, 05:24 Antoine Pitrou, > wrote: On Sat, 13 Jan 2018 13:54:33 +0100 Christian Heimes > wrote: > > If we

Re: [Python-Dev] Is static typing still optional?

On 12/21/2017 9:23 AM, Eric V. Smith wrote: On 12/21/17 6:25 AM, Sven R. Kunze wrote: On 21.12.2017 11:22, Terry Reedy wrote: @dataclass class C: a: int # integer field with no default b: float = 0.0 # float field with a default And the types will be recognized by type checkers

Re: [Python-Dev] Is static typing still optional?

On 12/21/2017 4:22 AM, Eric V. Smith wrote: On 12/21/2017 1:46 AM, Chris Barker wrote: I suggest that it be clear in the docs, and ideally in the PEP, that the dataclass decorator is using the *annotation" syntax, and that the the only relevant part it uses is that an annotation exists, but

Re: [Python-Dev] Revisiting old enhancement requests

On 12/20/2017 12:36 AM, Steven D'Aprano wrote: What is the best practice for revisiting old enhancement requests on the tracker, if I believe that the time is right to revisit a rejected issue from many years ago? (Nearly a decade.) I have been thinking about the opposite: revisit old

Re: [Python-Dev] PEP 432 progress: Python initalization

On 12/14/2017 10:16 AM, Victor Stinner wrote: Hi, Serhiy Storchaka seems to be worried by the high numbers of commits in https://bugs.python.org/issue32030 "PEP 432: Rewrite Py_Main()", so let me explain the context of this work :-) You could have (and still could) made that a master issue

Re: [Python-Dev] "CPython loves your Pull Requests" talk by Stéphane Wirtel

On 12/5/2017 10:25 AM, Mariatta Wijaya wrote: * Time to merge a PR: 3 days in average, good! Slide said 2.98 days, another said 4.4% by developers. Regarding the average time to merge PR, I'm interested to know the average time to merge for PRs not made by Python Core Devs. Trivially

Re: [Python-Dev] Zero-width matching in regexes

On 12/4/2017 6:21 PM, MRAB wrote: I've finally come to a conclusion as to what the "correct" behaviour of zero-width matches should be: """always return the first match, but never a zero-width match that is joined to a previous zero-width match""". Is this different from current re or regex?

Re: [Python-Dev] Using async/await in place of yield expression

On 11/27/2017 5:05 PM, Guido van Rossum wrote: On Mon, Nov 27, 2017 at 1:58 PM, Greg Ewing > wrote: Guido van Rossum wrote: The source for sleep() isn't very helpful -- e.g. @coroutine is mostly a backwards

Re: [Python-Dev] Allow tuple unpacking in return and yield statements

On 11/25/2017 1:55 AM, David Cuthbert wrote: First time contributing back -- if I should be filing a PEP or something like that for this, please let me know. I don't think a PEP is needed. Coming from https://bugs.python.org/issue32117, unparenthesized tuple unpacking is allowed in

Re: [Python-Dev] PEP 560

On 11/14/2017 3:26 PM, Ivan Levkivskyi wrote: After some discussion on python-ideas, see https://mail.python.org/pipermail/python-ideas/2017-September/047220.html, this PEP received positive comments. The updated version that takes into account the comments that appeared in the discussion so

Re: [Python-Dev] PEP 563: Postponed Evaluation of Annotations

On 11/9/2017 9:11 PM, Nick Coghlan wrote: On 10 November 2017 at 05:51, Guido van Rossum wrote: If we have to change the name I'd vote for string_annotations -- "lazy" has too many other connotations (e.g. it might cause people to think it's the thunks). I find

Re: [Python-Dev] [python-committers] Enabling depreciation warnings feature code cutoff

On 11/6/2017 9:47 PM, Nick Coghlan wrote: On 7 November 2017 at 05:00, Alex Gaynor wrote: I also feel this decision was a mistake. If there's a consensus to revert, I'm happy to draft a PEP. Even without consensus to revert, I think it would be great to have a PEP

Re: [Python-Dev] Reminder: 12 weeks to 3.7 feature code cutoff

On 11/2/2017 4:54 AM, Lele Gaifax wrote: I'm not sure if the rebase should have been done on the original branch instead of creating a new one, or instead if I should open a new PR (and close the original one?). It is normal to 'git merge upstream/master' after updating the master branch and

Re: [Python-Dev] Migrate python-dev to Mailman 3?

On 11/1/2017 11:06 PM, Guido van Rossum wrote: Another one is core-mentorship, which satisfies the same criteria; and in my view this has the added and useful property that its beneficiaries are non-core members. After that I'd do core-workflow. Honestly I'd leave python-committers alone for a

Re: [Python-Dev] PEP 530

On 10/27/2017 4:43 PM, London wrote: can you help me get idol for my computer Post questions about using python on python-list and include information about what OS you are running and what version of Python you want. -- Terry Jan Reedy ___

Re: [Python-Dev] PEP 553

On 10/2/2017 10:45 AM, Guido van Rossum wrote: On Sun, Oct 1, 2017 at 11:15 PM, Terry Reedy <tjre...@udel.edu <mailto:tjre...@udel.edu>> wrote: On 10/2/2017 12:44 AM, Guido van Rossum wrote: - There's no rationale for the *args, **kwds part of the breakpoint

Re: [Python-Dev] Investigating time for `import requests`

On 10/2/2017 4:57 AM, Paul Moore wrote: In practice, I don't think the fact that re.search() et al cache the compiled expressions is that well known (it's mentioned in the re.compile docs, but not in the re.search docs) We could add redundant mentions in the functions ;-). and so people

Re: [Python-Dev] PEP 553

On 10/2/2017 12:44 AM, Guido van Rossum wrote: - There's no rationale for the *args, **kwds part of the breakpoint() signature. (I vaguely recall someone on the mailing list asking for it but it seemed far-fetched at best.) If IDLE's event-driven GUI debugger were rewritten to run in the

Re: [Python-Dev] PEP 553, v3

On 9/13/2017 10:12 PM, Barry Warsaw wrote: Here’s an update to PEP 553, which makes $PYTHONBREAKPOINT a first class feature. I’ve also updated PR #3355 with the implementation to match. Looks pretty good to me. Reading the PR eliminated my remaining uncertainties. -- Terry Jan Reedy

Re: [Python-Dev] PEP 553: Built-in debug()

On 9/7/2017 10:45 PM, Barry Warsaw wrote: On Sep 7, 2017, at 16:19, Terry Reedy <tjre...@udel.edu> wrote: I think breakpoint() should have a db= parameter so one can select a debugger in one removable line. The sys interface is more useful for IDEs to change the default, possible with

Re: [Python-Dev] PEP 553: Built-in debug()

On 9/7/2017 12:52 PM, Barry Warsaw wrote: On Sep 7, 2017, at 07:46, Guido van Rossum wrote: Without following all this (or the PEP, yet) super exactly, does this mean you are satisfied with what the PEP currently proposes or would you like changes? It's a little unclear

Re: [Python-Dev] PEP 553: Built-in debug()

On 9/7/2017 12:50 PM, Barry Warsaw wrote: On Sep 6, 2017, at 23:10, Terry Reedy <tjre...@udel.edu> wrote: Environmental variables are set to strings, not objects. It is not clear how you intend to handle the conversion. The environment variable names a module import path. W

Re: [Python-Dev] PEP 553: Built-in debug()

On 9/6/2017 6:45 PM, Barry Warsaw wrote: On Sep 6, 2017, at 14:59, Terry Reedy <tjre...@udel.edu> wrote: Currently, the debugger is started in response to a menu seletion in the IDLE process while the python process is idle. One reason for the 'idle' requirement' is because whe

Re: [Python-Dev] PEP 553: Built-in debug()

On 9/6/2017 6:24 PM, Barry Warsaw wrote: On Sep 6, 2017, at 10:14, Fabio Zadrozny wrote: I think it's a nice idea. Great! Related to the name, on the windows c++ there's "DebugBreak": https://msdn.microsoft.com/en-us/library/windows/desktop/ms679297(v=vs.85).aspx,

Re: [Python-Dev] PEP 553: Built-in debug()

On 9/6/2017 10:42 AM, Barry Warsaw wrote: I don’t think that’s a good idea. pdb is a thing, and that thing is the standard library debugger. I don’t think ‘pdb’ should be the term we use to describe a generic Python debugger interface. That to me is one of the advantages of PEP 553; it

Re: [Python-Dev] [RFC] Removing pure Python implementation of OrderedDict

On 9/5/2017 2:20 PM, INADA Naoki wrote: On Wed, Sep 6, 2017 at 2:13 AM, Eric Snow wrote: Like Antoine, I consider the pure Python implementation to be valuable. Furthermore, the pure Python implementation is the reference, so its behavior is idiomatic. To this

Re: [Python-Dev] [RFC] Removing pure Python implementation of OrderedDict

On 9/5/2017 10:40 AM, Guido van Rossum wrote: On Tue, Sep 5, 2017 at 5:58 AM, Simon Cross > wrote: I thought the decision a few years ago was that all modules that have a C library for performance reasons should also

Re: [Python-Dev] To reduce Python "application" startup time

On 9/5/2017 9:02 AM, INADA Naoki wrote: But application startup time is more important. And we can improve them with optimize importing common stdlib. Current `python -v` is not useful to optimize import. So I use this patch to profile import time.

Re: [Python-Dev] HTTPS on bugs.python.org

On 9/1/2017 11:31 AM, Oleg Broytman wrote: On Fri, Sep 01, 2017 at 05:27:59PM +0200, Antoine Pitrou wrote: On Fri, 1 Sep 2017 17:03:59 +0200 Victor Stinner wrote: And by the way the problem goes away if you use the "HTTPS Everywhere" plugin

Re: [Python-Dev] HTTPS on bugs.python.org

On 9/1/2017 9:36 AM, Antoine Pitrou wrote: And by the way the problem goes away if you use the "HTTPS Everywhere" plugin for Firefox. Firefox has both 'extension' and 'plugin' add-ons. "HTTPS Everywhere" is found under 'extensions'. Works great. On Fri, 1 Sep 2017 15:29:58 +0200 Antoine

Re: [Python-Dev] bpo-5001: More-informative multiprocessing error messages (#3079)

On 8/31/2017 3:27 PM, Brett Cannon wrote: On Wed, 30 Aug 2017 at 02:56 Paul Moore

Re: [Python-Dev] Inplace operations for PyLong objects

On 8/31/2017 2:40 PM, Manciu, Catalin Gabriel wrote: Hi everyone, While looking over the PyLong source code in Objects/longobject.c I came across the fact that the PyLong object doesnt't include implementation for basic inplace operations such as adding or multiplication: [...] long_long,

Re: [Python-Dev] [bpo-30421]: Pull request review

On 8/28/2017 4:43 PM, Mark Lawrence via Python-Dev wrote: The bulk of the work on argparse in recent years has been done by paul.j3.  I have no idea whether or not he is classed as a core developer. 'He' is a CLA-signed contributor, but not a committer, with no GitHub name registered with

<    1   2   3   4   5   6   7   8   9   10   >