[Python-Dev] Re: 1 PR, multiple issues

This was more of a core-mentorship question (tracker management) than a pydev question (Python development). But since we are here... On 6/10/2019 11:41 PM, Mariatta wrote: Hmm, I personally would still consider the additional issues as duplicates. So I would make note in each of the duplicate

[Python-Dev] Re: Using vectorcall for tp_new and tp_init

On 6/7/2019 6:41 AM, Jeroen Demeyer wrote: Hello, I'm starting this thread to brainstorm for using vectorcall to speed up creating instances of Python classes. Currently the following happens when creating an instance of a Python class X using X(.) and assuming that __new__ and __init__

Re: [Python-Dev] PEP 594: update 1

On 6/4/2019 8:21 PM, Victor Stinner wrote: So what is happening for this PEP since Python 3.8 beta1 has been released? Is it too late for Python 3.8 or not? The only action proposed for 3.8 was soft deprecation in the docs, which I presume can be done later in the beta process. It seems lik

Re: [Python-Dev] Expected stability of PyCode_New() and types.CodeType() signatures

On 5/31/2019 5:28 PM, Simon Cross wrote: As the maintainer of Genshi, one the libraries affected by the CodeType and similar changes, I thought I could add a users perspective to the discussion: Genshi is a templating engine that parses Python code from inside its templates. It supports Pytho

Re: [Python-Dev] Should I postpone PEP 558 (locals() semantics) to Python 3.9?

On 5/31/2019 6:20 AM, Nick Coghlan wrote: On Fri., 31 May 2019, 6:34 pm Nathaniel Smith, > wrote: I wouldn't mind having a little more breathing room. It's frustrating to miss the train, but these bugs are several decades old so I guess nothing terrible will ha

Re: [Python-Dev] Expected stability of PyCode_New() and types.CodeType() signatures

On 5/31/2019 4:46 AM, Petr Viktorin wrote: Hello, PEP 570 (Positional-Only Parameters) changed the signatures of PyCode_New() and types.CodeType(), adding a new argument for "posargcount". Our policy for such changes seems to be fragmented tribal knowledge. I'm writing to check if my understand

Re: [Python-Dev] Overloading comparison operator for lists

On 5/28/2019 11:35 PM, Montana Burr wrote: What is the justification for causing list == 3 to evaluate to False, besides the obvious "a list cannot equal a number"? That is completely sufficient. The default comparison is by id, and a class must override to get something different. The 'def

Re: [Python-Dev] PEP 558: Defined semantics for locals()

On 5/27/2019 9:52 AM, Richard Damon wrote: On 5/27/19 9:12 AM, Terry Reedy wrote: I believe that the situation is or can be thought of as this: there is exactly 1 function locals dict. per function invocation, or more generally, as Guido said, per stack frame. This part is obvious to me

Re: [Python-Dev] [SPAM?] Re: PEP 558: Defined semantics for locals()

On 5/27/2019 3:18 AM, Greg Ewing wrote: Chris Angelico wrote: Except that it does. After calling locals() a second time, the result of the *first* call will be updated to reflect changes. Yeow. That's *really* unintuitive. There had better be an extremely good reason for this behaviour. I be

Re: [Python-Dev] Accepting PEP 587 (Python Initialization Configuration)

On 5/26/2019 10:02 AM, Thomas Wouters wrote: As PEP-delegate, I'm accepting version 5 of PEP 587 (Python Initialization Configuration). ... Thanks, Victor, for pushing this massive amount of work through; And thanks to you for reviewing and approving. it won't affect most people using Py

Re: [Python-Dev] PEP 558: Defined semantics for locals()

On 5/25/2019 10:36 AM, Guido van Rossum wrote: This looks great. I agree. I understand and have tried to explain normal operation multiple times. The proposed new doc looks better than anything I ever wrote. (I never even thought about locals() with tracing on.) The improved clarity well

Re: [Python-Dev] Missing testcase for bpo-34125

On 5/22/2019 5:41 AM, Jeroen Demeyer wrote: Could somebody please merge https://github.com/python/cpython/pull/13461 It adds a missing testcase for bpo-34125. This is testing code which is affected by PEP 590, so missing this test might accidentally break CPython if we screw up with implementi

Re: [Python-Dev] PEP 594: update 1

On 5/21/2019 10:12 AM, Christian Heimes wrote: --- PEP: 594 Title: Removing dead batteries from the standard library 'dead' seems controversial. 'nearly useless' should be less so. I think 'after 2.7 end-of-life' is worth addin

Re: [Python-Dev] PEP 594: Removing dead batteries from the standard library

On 5/21/2019 9:01 AM, Steven D'Aprano wrote: ... Many Python users don't have the privilege of being able to install arbitrary, unvetted packages from PyPI. They get to use only packages from approved vendors, including the stdlib, what they write themselves, and nothing else. Please don't dismis

Re: [Python-Dev] PEP 594: Removing dead batteries from the standard library

On 5/20/2019 6:06 PM, Christian Heimes wrote: Removing the crypt module would remove support for system-standard password files. I don't understand the rationale. Applications *must* not access system-standard password files directly. On any sanely and securely configured systems, applicatio

Re: [Python-Dev] Parser module in the stdlib

On 5/20/2019 11:55 AM, Guido van Rossum wrote: On Thu, May 16, 2019 at 3:57 PM Steve Dower > wrote: [...] We still have the policy of not removing modules that exist in the Python 2 standard library. But 3.9 won't be covered by that :) I didn't even re

Re: [Python-Dev] Python Language Summit 2019 blog posts

On 5/15/2019 6:06 PM, Mariatta wrote: If you have FOMO (fear of missing out) of Python Language Summit 2019, worry no more. We invited A. Jesse Jiryu Davis to cover for the language summit, and the blog posts are starting to appear in The PSF's official blog. Starts here: http://pyfound.blo

[Python-Dev] Online Devguide mostly not working

https://devguide.python.org gives the intro page with TOC on sidebar and at end. Clicking anything, such as Getting Started, which tries to display https://devguide.python.org/setup/, returns a Read the Docs page "Sorry This page does not exist yet." 'Down for everyone' site also cannot acces

Re: [Python-Dev] Redoing failed PR checks

On 5/8/2019 10:23 AM, Eric V. Smith wrote: I think you can close and reopen the PR. That’s what I’m trying on my blocked PR. That works but reruns all the CI checks, including the ones already passed. Some bots allow individual reruns, but it is not as clear as it should be. -- Terry Jan

Re: [Python-Dev] "if __name__ == '__main__'" at the bottom of python unittest files

On 5/1/2019 9:30 AM, Chris Withers wrote: Agreed, but my focus here is to get to 100% for mock so that it's clear that all the code is there for a reason; mock is very complicated by necessity, and having examples of why code needs to be there is what I'm aiming for most of all. I agree that

Re: [Python-Dev] "if __name__ == '__main__'" at the bottom of python unittest files

On 5/1/2019 2:13 AM, Chris Withers wrote: On 01/05/2019 06:12, Terry Reedy wrote: Such blocks should be excluded from coverage by the default .coveragerc file.  Mine came with exclude_lines = # Don't complain if non-runnable code isn't run: if 0: if __name__ ==

Re: [Python-Dev] "if __name__ == '__main__'" at the bottom of python unittest files

On 4/30/2019 5:24 PM, Chris Withers wrote: Hi All, I have a crazy idea of getting unittest.mock up to 100% code coverage. I noticed at the bottom of all of the test files in testmock/, there's a: if __name__ == '__main__':     unittest.main() ...block. Such blocks should be excluded from c

Re: [Python-Dev] Python Documentation Translation in italian language

On 4/20/2019 4:14 AM, Alessandro Cucci wrote: Hello folks, I want to start a project for translating the Python Documentation in Italian. I'm reading the PEP545, trying to understand how it works. I founded a Python User Group in my city and I can work with them on the translations, plus next

Re: [Python-Dev] Fixing the ctypes implementation of the PEP3118 buffer interface

On 4/14/2019 2:54 AM, Eric Wieser wrote: I've recently been adding better support to Numpy 1.16 for interoperability with ctypes. In doing so, I came across two bugs in the implementation of the PEP3118 buffer interface within ctypes, affecting `Structure`s and arrays. Rather than repeating the

Re: [Python-Dev] No longer enable Py_TRACE_REFS by default in debug build

On 4/10/2019 2:45 PM, Steve Dower wrote: It's debug mode, and so you should expect less efficient memory and CPU usage. On my Windows machine, 'python -m test -ugui' takes about twice as long. That's why we have two modes - so that it's easier to debug issues. -- Terry Jan Reedy ___

Re: [Python-Dev] (no subject)

On 4/10/2019 7:24 AM, Robert Okadar wrote: Hi community, I have developed a tkinter GUI component, Python v3.7. It runs very well in Linux but seeing a huge performance impact in Windows 10. While in Linux an almost real-time performance is achieved, in Windows it is slow to an unusable level.

Re: [Python-Dev] BDFL-Delegate appointments for several PEPs

On 3/25/2019 12:27 AM, Cameron Simpson wrote: On 24Mar2019 23:22, Terry Reedy wrote: On 3/24/2019 10:01 PM, Terry Reedy wrote: On 3/24/2019 7:00 PM, Cameron Simpson wrote: Did you have a specific scenario in mind? I was thinking about IDLE and its tangled web of circular inports, but I am

Re: [Python-Dev] BDFL-Delegate appointments for several PEPs

On 3/24/2019 10:01 PM, Terry Reedy wrote: On 3/24/2019 7:00 PM, Cameron Simpson wrote: Did you have a specific scenario in mind? I was thinking about IDLE and its tangled web of circular inports, but I am now convinced that this change will not affect it.  Indeed, idlelib/pyshell.py

Re: [Python-Dev] BDFL-Delegate appointments for several PEPs

On 3/24/2019 7:00 PM, Cameron Simpson wrote: On 24Mar2019 17:02, Terry Reedy wrote: On 3/24/2019 8:21 AM, Nick Coghlan wrote: * PEP 499: Binding "-m" executed modules under their module name as well as `__main__` My brief response: +1 unless there is a good reason not. There t

Re: [Python-Dev] BDFL-Delegate appointments for several PEPs

On 3/24/2019 8:21 AM, Nick Coghlan wrote: We'll be announcing those appointments as we go, so I'm happy to report that I will be handling the BDFL-Delegate responsibilities for the following PEPs: Where do we discuss these? If a delegate has a provisional view, it might help focus discussion

Re: [Python-Dev] Is XML serialization output guaranteed to be bytewise identical forever?

On 3/21/2019 1:23 PM, Paul Moore wrote: On Thu, 21 Mar 2019 at 17:05, Steve Holden wrote: Especially as the standards specifically say that ordering has no semantic impact. Byte-by-byte comparison of XML is almost always inappropriate. Conversely, if ordering has no semantic impact, there

Re: [Python-Dev] Can I submit more support of standard library for VxWorks after 3.8.0 beta1?

One main purpose of the beta period is to discover and fix bugs and otherwise tweek behavior in the new features included in the first beta. This usually presupposes that the feature is thought to be 'ready-to-go' as-is, absent new discoveries. Interpretation and issuance of exceptions is usu

Re: [Python-Dev] Is XML serialization output guaranteed to be bytewise identical forever?

On 3/18/2019 6:41 PM, Raymond Hettinger wrote: We're having a super interesting discussion on https://bugs.python.org/issue34160 . It is now marked as a release blocker and warrants a broader discussion. Our problem is that at least two distinct and important users have written tests that de

Re: [Python-Dev] Tests for internal functionality

On 3/16/2019 3:10 AM, Ivan Pozdeev via Python-Dev wrote: In https://github.com/python/cpython/pull/6541 , I was requested to add tests for an internal C function. As I wrote in https://github.com/python/cpython/pull/6541#issuecomment-445514807 , it's not clear from the codebase 1) where tes

Re: [Python-Dev] (Licensing question) backport of shutil.copyfile() functionality

On 3/11/2019 10:54 PM, Inada Naoki wrote: Hello, some time ago I contributed a couple of patches to speedup shutil.copy*() functions: https://bugs.python.org/issue33671 https://bugs.python.org/issue33695 You retain copyright on the code you contributed. I would like to backport both functio

Re: [Python-Dev] [RELEASE] Python 2.7.16

On 3/3/2019 10:30 PM, Benjamin Peterson wrote: I'm pleased to announce the immediate availability of Python 2.7.16 for download at https://www.python.org/downloads/release/python-2716/. On Windows 10, this is an 'unrecognized app' and Windows Defender SmartScreen, now default, refuses to run

Re: [Python-Dev] Summary of Python tracker Issues

On 2/28/2019 6:54 PM, Glenn Linderman wrote: There seems to be enough evidence that something went wrong somewhere, though, and whoever maintains that process should start investigating, but it would still be nice to get confirmation from a non-Google email recipient whether they did or did no

Re: [Python-Dev] Summary of Python tracker Issues

On 2/28/2019 5:38 PM, Glenn Linderman wrote: On 2/28/2019 2:18 PM, Jonathan Goble wrote: On Thu, Feb 28, 2019, 5:11 PM Terry Reedy <mailto:tjre...@udel.edu>> wrote: On 2/28/2019 8:07 AM, Jonathan Goble wrote: > On Thu, Feb 28, 2019, 8:02 AM INADA Naoki mailto:songofaca.

Re: [Python-Dev] Summary of Python tracker Issues

On 2/28/2019 8:07 AM, Jonathan Goble wrote: On Thu, Feb 28, 2019, 8:02 AM INADA Naoki > wrote: No stats for last week? Been missing for two weeks actually. I did not receive a summary on either the 15th or 22nd. Ditto for me. I get pydev via gmane. Anyon

Re: [Python-Dev] datetime.timedelta total_microseconds

On 2/26/2019 7:03 PM, Chris Barker via Python-Dev wrote: So: it would be good to provide a correct, simple,  intuitive, and discoverable way to do that. timedelta.total_seconds() To me, total_x implies that there is a summation of multiple timedeltas, and there is not. So not intuitive to

Re: [Python-Dev] "Good first issues" on the bug tracker

On 2/23/2019 2:50 PM, Cheryl Sabella wrote: AM Karthikeyan wrote: I would also recommend waiting for a core dev or someone to provide some feedback or confirmation on even an easy issue's fix since it's easy to propose a fix to be later rejected due to various reasons resulting

Re: [Python-Dev] Another update for PEP 394 -- The "python" Command on Unix-Like Systems

On 2/13/2019 10:25 PM, Steven D'Aprano wrote: I haven't come across this FUD about Python 4, I have, on StackOverflow, induced by people reading something like "deprecated now, removed in 4.0" -- Terry Jan Reedy ___ Python-Dev mailing list Pytho

Re: [Python-Dev] Another update for PEP 394 -- The "python" Command on Unix-Like Systems

On 2/13/2019 3:26 PM, Barry Warsaw wrote: I personally would like for `python` to be the latest Python 3 version (or perhaps Brett’s launcher), `python2` to be Python 2.7 where installed (and not mandatory). `python3` would be an alias for the latest Python 3. It appears python is already p

Re: [Python-Dev] [bpo-35155] Requesting a review

On 2/12/2019 3:24 PM, Terry Reedy wrote: The problem is that the urllib.request doc has several 'placeholder-literal' and 'literal-placeholder' constructs where Correction: The result must be a legal function name, so that should be 'placeholder_literal' and &#

Re: [Python-Dev] [bpo-35155] Requesting a review

On 2/12/2019 5:14 AM, Denton Liu wrote: Hello all, A couple months back, I reported bpo-35155[1] and I submitted a PR for consideration[2]. After a couple of reviews, it seems like progress has stalled. Would it be possible for someone to review this? Thanks, Denton [1]: https://bugs.python.o

Re: [Python-Dev] CPython on Windows ARM32

On 2/5/2019 10:10 PM, Zachary Ware wrote: I'm all for the first two changes (especially the second), and if 10 years of pledged corporate support for a new platform is the price we have to pay for them, I'm ok with that :). I would expect that the main question should be the density of WinArm

Re: [Python-Dev] bpo-32972: Add unittest.AsyncioTestCase review (for 3.8?)

On 2/5/2019 11:44 AM, Antoine Pitrou wrote: I cannot comment on the PR, but since the functionality is asyncio-specific, I would suggest moving it to a dedicate `asyncio.testing` module, or something similar, rather than leaving it in `unittest` proper. That is one of the options discussed on

Re: [Python-Dev] Asking for reversion

On 2/3/2019 7:55 PM, Guido van Rossum wrote: Also, did anyone ask Davin directly to roll it back? Antoine posted on the issue, along with Robert O. Robert reviewed and make several suggestions. -- Terry Jan Reedy ___ Python-Dev mailing list Pytho

Re: [Python-Dev] Asking for reversion

On 2/3/2019 4:03 PM, Antoine Pitrou wrote: Hello, I'd like to ask for the reversion of the changes done in https://github.com/python/cpython/pull/11664 The reason is simple: [over 1000 lines not reviewed, no tests, no docs] Aside from the technical reasons Antoine gave, which I agree with, I

Re: [Python-Dev] Anyone else seeing a lack of caching in local docs builds?

On 1/27/2019 9:01 AM, Nick Coghlan wrote: Hi folks, I'm currently seeing a behaviour where every time I run "make html", all 474 source files get rebuilt. I just rebuilt, ditto, all 474. Caching only works when I rebuild 'soon' (at least within same day) after a complete rebuild. I just up

[Python-Dev] Add more SyntaxWarnings?

https://bugs.python.org/issue15248 is about situations like the following: >>> [(1,2,3) (4,5,6)] Traceback (most recent call last): File "", line 2, in (4,5,6)] TypeError: 'tuple' object is not callable The original poster requested that the error message be augmented with something

Re: [Python-Dev] Windows porting: request to review PR #880

On 12/21/2018 6:26 AM, Jeroen Demeyer wrote: Can somebody please review https://github.com/python/cpython/pull/880 That addresses a severe problem on Windows making it impossible to build any C++ extension module with some compilers. Issue is https://bugs.python.org/issue11566. Someone needs t

Re: [Python-Dev] 3.7.2rc1 and 3.6.8rc1 cutoffs ahead, last 3.6.x bugfix release!

On 12/19/2018 4:14 AM, Serhiy Storchaka wrote: I propose to allow backporting bugfixes to 3.6 if they do not need excessive work, but stop to fix 3.6 only bugs. I think this would need a PEP. After migrating to GitHab, backporting became less painful, Before GitHub, we forward ported. For

Re: [Python-Dev] I reverted "Add Windows App Store package" change

On 12/8/2018 11:32 AM, Nick Coghlan wrote: Whether the UX counts as "good" or not is open to debate (I consider it pretty good for the complexity of the task it handles), but if you ever want to revise the history of a complex patch series to make it easier for reviewers to follow: 1. Use "git

Re: [Python-Dev] I reverted "Add Windows App Store package" change

On 12/7/2018 11:31 AM, Victor Stinner wrote: I would be simpler if it would be possible to have a "patch serie": list of pull requests, One can make an 'index issue' with multiple dependencies, each with a PR. I do this for multiple independent changes to a module or related modules. or

Re: [Python-Dev] any way to subscribe to bugs and PRs on a particular topic?

On 12/4/2018 2:13 PM, Chris Withers wrote: Hello, Welcome back. unittest.mock is important for everyone writing non-trivial tests. I'd like to see if I can help with unittest.mock, but don't have a huge amount of bandwidth and can't even parse let alone process the whole firehose of bpo a

Re: [Python-Dev] Standardize error message for non-pickleable types

On 10/29/2018 5:17 PM, MRAB wrote: On 2018-10-29 19:38, Serhiy Storchaka wrote: When you try to to pickle or copy a non-pickleable object, you will get an error. In most cases this will be a TypeError with one of few similar, but different variants:     "can't pickle XXX objects" (default)    

Re: [Python-Dev] [RELEASE] Python 3.7.1 and 3.6.7 are now available

On 10/20/2018 1:37 PM, Ned Deily wrote: We are also happy to announce the availability of Python 3.6.7, the next maintenance release of Python 3.6: https://www.python.org/downloads/release/python-367/ Am I correct in thinking that there will be just one more maintenance release before go

Re: [Python-Dev] Servicing pypi.python.org

On 10/17/2018 8:32 PM, Facundo Batista wrote: Hola! tl;dr: can we have a (semi)permanent redirect from pypi.python.org to pypi.org? pypi is run by a different group from pydev core developers. Maybe someone here know what the current list is. -- Terry Jan Reedy __

Re: [Python-Dev] Arbitrary non-identifier string keys when using **kwargs

On 10/7/2018 1:34 PM, Chris Barker via Python-Dev wrote: On Fri, Oct 5, 2018 at 3:01 PM Brett Cannon > wrote: I'm also fine with saying that keys in **kwargs that are not proper identifiers is an implementation detail. It's not just **kwargs -- you can also use

Re: [Python-Dev] Petr Viktorin as BDFL-Delegate for PEP 580

On 10/3/2018 5:27 PM, Guido van Rossum wrote: On Wed, Oct 3, 2018 at 2:13 PM Terry Reedy <mailto:tjre...@udel.edu>> wrote: A language syntax-change proposal would be something else. IMO changes to the C API should be taken just as seriously -- the potential for breaking the worl

Re: [Python-Dev] Petr Viktorin as BDFL-Delegate for PEP 580

On 10/3/2018 8:12 AM, Jeroen Demeyer wrote: Hello, I would like to propose Petr Viktorin as BDFL-Delegate for PEP 580, titled "The C call protocol". He has co-authored several PEPs (PEP 394, PEP 489, PEP 534, PEP 547, PEP 573), several of which involve extension modules. Petr has agreed to

Re: [Python-Dev] dear core-devs

On 10/2/2018 7:16 PM, Michael Felt wrote: On 10/2/2018 11:34 PM, Terry Reedy wrote: On 10/2/2018 12:41 PM, Simon Cross wrote: Are there any core devs that Michael or Erik could collaborate with? Rather than rely on adhoc patch review from random core developers. You two might collaborate

Re: [Python-Dev] dear core-devs

On 10/2/2018 12:41 PM, Simon Cross wrote: Are there any core devs that Michael or Erik could collaborate with? Rather than rely on adhoc patch review from random core developers. You two might collaborate with each other to the extent of reviewing some of each other's PRs. That still leaves t

Re: [Python-Dev] Change in Python 3's "round" behavior

On 9/26/2018 7:26 AM, j...@math.brown.edu wrote: To paraphrase: 1. Where was the 3.0 change discussed? 2. What was the rationale? I think these have been answered as well as possible. 3. Can the change be reverted? It 'could be', but will not be reverted? 4. Should something be added to the d

Re: [Python-Dev] Store startup modules as C structures for 20%+ startup speed improvement?

On 9/18/2018 2:38 PM, Steve Dower wrote: The primary benefit of the importlib hook approach is that it would not require rebuilding CPython each time you make a change. If one edits a .c or .h file, one must rebuild to test. If one edits a .py module, one does not, and it would be a major nu

Re: [Python-Dev] Official citation for Python

, the Reference Manual, in the most common formats. On Sun, Sep 9, 2018 at 11:33 PM Terry Reedy <mailto:tjre...@udel.edu>> wrote: On 9/9/2018 3:43 PM, Jacqueline Kazil wrote: > The PSF has received a few inquiries asking the question — > “How do I cite Python?”So, I am reachi

Re: [Python-Dev] Official citation for Python

On 9/9/2018 3:43 PM, Jacqueline Kazil wrote: The PSF has received a few inquiries asking the question — “How do I cite Python?”So, I am reaching out to you all to figure this out. (For those that don’t know my background, I have been in academia for a bit as a Ph.D student and have worked at t

Re: [Python-Dev] Why does the Contributor Agreement need my address?

On 9/9/2018 1:49 PM, Antoine Pitrou wrote: On Sat, 8 Sep 2018 23:11:27 -0400 "Joseph C. Sible" wrote: I'm used to signing CLA's that require nothing beyond a name and a check box. When I went to sign the PSF Contributor Agreement so I can submit a PR for CPython, I was surprised to see that it

Re: [Python-Dev] We cannot fix all issues: let's close XML security issues (not fix them)

On 9/6/2018 11:05 AM, Ryan Gonzalez wrote: Thought: what if there's a label on the bug tracker meaning roughly "we're probably not going to fix this anytime soon, but we won't mind someone stepping up"? Not needed. Good patches are always welcome. And if there is no current PR or other infor

Re: [Python-Dev] Python 2.7 EOL date

On 8/23/2018 2:53 PM, Collin Anderson wrote: Hi All, Sorry if this has been mentioned before, but I noticed the Python 2.7 EOL date was recently set to Jan 1st, 2020. My understanding was Python releases get 5 years of support from their initial release, '5' is a rounded, rather than exact

Re: [Python-Dev] Python 2.7 EOL date

On 8/23/2018 8:14 PM, Barry Warsaw wrote: On Aug 23, 2018, at 15:23, Eric V. Smith wrote: On 8/23/2018 4:30 PM, Victor Stinner wrote: Hi, The reference is the PEP 373 "Python 2.7 Release Schedule". See the "Update" section: https://www.python.org/dev/peps/pep-0373/#update We could probably

Re: [Python-Dev] Problem in importing python packages under python 3.6 environment

On 8/9/2018 8:45 AM, Poornima .D. wrote: I have limited knowledge on python development.  I am trying to write a test application which needs to import from many packages across mutliple directories. I tried using an environment variable and appending to sys.path variable so that import Cla

Re: [Python-Dev] [PEP 576/580] Comparing PEP 576 and 580

On 8/1/2018 6:17 AM, Jeroen Demeyer wrote: On 2018-07-31 11:12, INADA Naoki wrote: Any PEP won't be accepted in few month, because we don't have flow to accept PEPs for now. Is that certain? I haven't been following the process discussions, so I'm just asking the question. For example, given

Re: [Python-Dev] Using Python on a fork-less POSIX-like OS

On 7/30/2018 4:26 AM, Barath Aron wrote: On 07/30/2018 10:23 AM, Victor Stinner wrote: Python 3.8 will support os.posix_spawn(). I would like to see it used whenever possible instead of fork+exec, since it's faster and it can be safer on some platforms. Pablo Salgado is your guy for that. Vic

Re: [Python-Dev] [issue34221] Any plans to combine collections.OrderedDict with dict

On 7/26/2018 2:15 AM, Raymond Hettinger wrote: On Jul 25, 2018, at 8:23 PM, INADA Naoki wrote: On Thu, Jul 26, 2018 at 12:04 PM Zhao Lee wrote: Since Python 3.7，dicts remember the order that items were inserted, so any plans to combine collections.OrderedDict with dict? https://docs.pytho

Re: [Python-Dev] PEP 572: Assignment Expressions -- intention to accept, near-final draft

On 7/9/2018 9:00 PM, Guido van Rossum wrote: We strongly prefer feedback in the form of Pull Requests to the peps repo (the file is at https://github.com/python/peps/blob/master/pep-0572.rst ). I couple of people have said they don't kn

Re: [Python-Dev] Time for 3.4.9 and 3.5.6

On 7/8/2018 1:05 PM, Ivan Pozdeev via Python-Dev wrote: I'll use this opportunity to remind you that 3.4 build is broken -- it can't be built from start to installer with the instructions given because of outside factors (CPython has migrated from Hg to Git). https://bugs.python.org/issue31623

Re: [Python-Dev] Call for prudence about PEP-572

On 7/7/2018 12:53 PM, Tim Peters wrote: [Guido] ... As to why you might want to use := in a function call, I could imagine writing     if validate(name := re.search(pattern, line).group(1)):     return name If name has to be non-blank to pass validate, one can avoid

Re: [Python-Dev] Naming comprehension syntax [was Re: Informal educator feedback on PEP 572 ...]

On 7/6/2018 7:31 PM, Guido van Rossum wrote: On Fri, Jul 6, 2018 at 4:19 PM Terry Reedy <mailto:tjre...@udel.edu>> wrote: Since Guido, the first respondent, did not immediately shoot the idea down, I intend to flesh it out and make it more concrete. Maybe I should have sho

Re: [Python-Dev] Naming comprehension syntax [was Re: Informal educator feedback on PEP 572 ...]

In response to Guido's reply to my post fleshing out my idea to use 'generator|list|set|dict builder', On 7/6/2018 7:58 PM, Ivan Pozdeev via Python-Dev wrote: According to https://en.wikipedia.org/wiki/List_comprehension#History, the term's known from at least 1977 and comes from such influenti

Re: [Python-Dev] Naming comprehension syntax [was Re: Informal educator feedback on PEP 572 ...]

On 7/6/2018 11:51 AM, Chris Barker - NOAA Federal via Python-Dev wrote: via phone... Are we just having fun here? I floated the idea as a trial balloon to see what response it got. Or might we actually start using a new naming convention for the-syntax-formerly-known-as-generator-expressions?

Re: [Python-Dev] Examples for PEP 572

On 7/4/2018 3:34 PM, Steven D'Aprano wrote: On Wed, Jul 04, 2018 at 03:24:08PM -0400, Terry Reedy wrote: On 7/4/2018 9:35 AM, Steven D'Aprano wrote: On Wed, Jul 04, 2018 at 05:02:07PM +1000, Chris Angelico wrote: On Wed, Jul 4, 2018 at 4:07 PM, Serhiy Storchaka wrote: "

Re: [Python-Dev] Examples for PEP 572

On 7/4/2018 2:32 PM, Sven R. Kunze wrote: Sorry for adding yet another mail. :-( On 04.07.2018 10:54, Serhiy Storchaka wrote: Sorry, this PEP was rewritten so many times that I missed your Appendix. while total != (total := total + term):     term *= mx2 / (i*(i+1))     i += 2 return total

Re: [Python-Dev] Examples for PEP 572

On 7/4/2018 1:50 PM, Yury Selivanov wrote: On Wed, Jul 4, 2018 at 1:35 PM Ivan Pozdeev via Python-Dev wrote: On 04.07.2018 11:54, Serhiy Storchaka wrote: while total != (total := total + term): term *= mx2 / (i*(i+1)) i += 2 return total This code looks clever that the original

Re: [Python-Dev] Examples for PEP 572

On 7/4/2018 9:35 AM, Steven D'Aprano wrote: On Wed, Jul 04, 2018 at 05:02:07PM +1000, Chris Angelico wrote: On Wed, Jul 4, 2018 at 4:07 PM, Serhiy Storchaka wrote: "Assignment is a statement" -- that's exactly the point under discussion. I believe that this is Chris quoting and commenting

Re: [Python-Dev] Examples for PEP 572

On 7/3/2018 5:37 PM, Serhiy Storchaka wrote: I like programming languages in which all are expressions (including function declarations, branching and loops) and you can use an assignment at any point, but Python is built on other ways, and I like Python too. PEP 572 looks violating several Pyt

Re: [Python-Dev] Informal educator feedback on PEP 572 (was Re: 2018 Python Language Summit coverage, last part)

On 7/3/2018 2:42 AM, Tim Peters wrote: So if we had it to do over again I'd sigh and accept "generator comprehensions" anyway.  It's been an eternal PITA - and especially in the PEP 572 threads! - to keep typing "comprehensions or generator expressions".  Then again, if I had the power of Guid

Re: [Python-Dev] Failing tests (on a Linux distro)

On 7/2/2018 3:38 AM, Petr Viktorin wrote: And while I'm responding here, a bit of reflection and a heads-up: What Fedora as a distro should do better next time is re-build the entire ecosystem with a new Python version. For 3.7 we started doing that too late, and there are way too many project

Re: [Python-Dev] Informal educator feedback on PEP 572 (was Re: 2018 Python Language Summit coverage, last part)

On 6/30/2018 5:35 AM, Steven D'Aprano wrote: I've given reasons why I believe that people will expect assignments in comprehensions to occur in the local scope. Aside from the special case of loop variables, people don't think of comprehensions as a separate scope. I think this is because comp

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

On 6/29/2018 9:25 AM, Brett Cannon wrote: On Thu, Jun 28, 2018, 21:28 Terry Reedy, <mailto:tjre...@udel.edu>> wrote: [question about our coverage bot] Everything is either covered by the Travis or codecov configuration files which are both checked into the cpython repo. (I'm

Re: [Python-Dev] Informal educator feedback on PEP 572 (was Re: 2018 Python Language Summit coverage, last part)

On 6/28/2018 11:21 PM, Tim Peters wrote: [somewhere below] this is the last time I'm going to repeat it all again ;-) For me, this is your most convincing exposition and summary of why the proposal is at least ok. Thank you. [Chris] > yes, it was a contrived example, but the simplest one

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

On 6/24/2018 5:03 AM, Ammar Askar wrote: Is it possible, given that we are not paying for those reports, to customize the 'exclude_lines' definitions? Do you want to exclude python code or C code? Python code. For Python code, coverage.py also has some comments you can put down to exclude l

Re: [Python-Dev] Informal educator feedback on PEP 572 (was Re: 2018 Python Language Summit coverage, last part)

On 6/28/2018 8:05 AM, Baptiste Carvello wrote: Le 28/06/2018 à 01:31, Greg Ewing a écrit : Well, I remain profoundly unconvinced that writing comprehensions with side effects is ever a good idea, and Tim's examples did nothing to change that. Comprehensions with side effects feel scary indeed.

Re: [Python-Dev] Informal educator feedback on PEP 572 (was Re: 2018 Python Language Summit coverage, last part)

[\0 * \0 for \0 in iterable] with \1, \2, ... used as needed. (I am using the regex back-reference notation in a way similar to the use of str.format forward reference notation.) I will stop here for now, as it is 1:30 am for me. Terry On Mon, Jun 25, 2018 at 12:40 PM Terry Reedy &l

Re: [Python-Dev] Informal educator feedback on PEP 572 (was Re: 2018 Python Language Summit coverage, last part)

On 6/25/2018 8:25 AM, Paul Moore wrote: On 25 June 2018 at 12:44, Nick Coghlan wrote: Unfortunately, I think the key rationale for (b) is that if you *don't* do something along those lines, then there's a different strange scoping discrepancy that arises between the non-comprehension forms of c

Re: [Python-Dev] Informal educator feedback on PEP 572 (was Re: 2018 Python Language Summit coverage, last part)

On 6/24/2018 7:25 PM, Guido van Rossum wrote: I'd wager that the people who might be most horrified about it the (b) scoping rule change would be people who feel strongly that the change to the comprehension scope rules in Python 3 is a big improvement, I might not be one of those 'most hor

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

On 6/23/2018 5:48 PM, Zachary Ware wrote: On Sat, Jun 23, 2018 at 2:20 PM, Terry Reedy wrote: Rechecking now, on Gentoo test_idle appears and passed on these 3.6 and 3.7 pages http://buildbot.python.org/all/#/builders/82/builds/414/steps/5/logs/stdio Neither Firefox nor Edge can find

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

On 6/23/2018 1:09 PM, Zachary Ware wrote: On Sat, Jun 23, 2018 at 11:31 AM, Terry Reedy wrote: I have suggested that, and before that, the same for buildbots. The reality is that tkinter, IDLE, or turtle could be disabled on *nix by regressions and the official testing would not notice. I&#

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

On 6/22/2018 9:40 PM, Nathaniel Smith wrote: On Fri, Jun 22, 2018 at 6:16 PM, Terry Reedy wrote: I discovered the answer to 2. by shift-clicking on a text_x file to see their coverage report for the file. The colors actually do reflect the test lines executed. codecov.io excludes gui tests

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