Re: [Python-Dev] Python version numbers

On Tue, 3 Apr 2018 at 11:18 Barry Warsaw wrote: > On Apr 3, 2018, at 05:51, Paul G wrote: > > > Switching to CalVer is a pretty clear sign that there is now a "rolling > backwards compatibility window", and it allows Python to skip right over > the mythical

Re: [Python-Dev] Why is pickle.DEFAULT_PROTOCOL still 3?

On Tue, 3 Apr 2018 at 01:19 Serhiy Storchaka wrote: > 03.04.18 01:57, Lukasz Langa пише: > >> On Apr 2, 2018, at 2:13 PM, Antoine Pitrou wrote: > >> On Mon, 2 Apr 2018 13:48:46 -0700 > >> Lukasz Langa wrote: > >>> Pickle protocol

Re: [Python-Dev] Python version numbers

On Tue, 3 Apr 2018 at 07:39 Paul G wrote: > > When programs use calendar-based versioning, I'm left with no > > information as to whether it's breaking changes or not. In fact, it > > might as well have no version numbers whatsoever. If I care about > > backward compatibility, I

Re: [Python-Dev] Python Test suite hangining

On Sun, 4 Mar 2018 at 11:38 TonyFlury via Python-Dev wrote: > All, > Sorry to trouble you all - but I am trying to get the Python 3.8 test > suite running on Ubuntu 16.0.4. > > As per the dev guide - having cloned the repo and run the build I am > running the test suite

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

On Tue, 27 Feb 2018 at 05:38 INADA Naoki wrote: > Hi, all. > > There is design discussion which is deferred blocker of 3.7. > https://bugs.python.org/issue32911 > > ## Background > > An year ago, I moved docstring in AST from statements list to field of > module, class

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

On Wed, 21 Feb 2018 at 14:21 Barry Warsaw wrote: > On Feb 21, 2018, at 13:22, Guido van Rossum wrote: > > > > I'm willing to reconsider if there's a good enough tool. Ditto for C > code (or do we already do it for C?). > > For Python code, flake8 --possibly

Re: [Python-Dev] Backfilling 'awaiting' labels

FYI I am now done backfilling issues. On Tue, 30 Jan 2018 at 19:35 Brett Cannon <br...@snarky.ca> wrote: > I have written a script that will go through and backfill the 'awaiting' > label on older pull requests based on the review state as it stands today. > A comme

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

regression (I understand that this is a hard to > implement feature...) > Possibly. This is starting to dive into Bors/Zuul-level regression management which is more infrastructure to run, so we would have to decide we seriously want this maintenance overhead. -Brett > > Huge thanks to the cor

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

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 and if there is a particular sticking point to please bring it up on the core-workflow mailing list so we can potentially address it.

[Python-Dev] Backfilling 'awaiting' labels

I have written a script that will go through and backfill the 'awaiting' label on older pull requests based on the review state as it stands today. A comment will be left if an "awaiting changes" label is set explaining that we're backfilling and if you're ready for a change review then leave the

Re: [Python-Dev] Friendly reminder: be kind to one another

On Tue, Jan 30, 2018, 17:30 Steven D'Aprano, wrote: > On Tue, Jan 30, 2018 at 06:00:36PM +, Paul Moore wrote: > > On 30 January 2018 at 17:10, Antoine Pitrou wrote: > > > > > > This is missing a bit of context. Is this about python-dev? Some > > >

Re: [Python-Dev] Friendly reminder: be kind to one another

On Tue, 30 Jan 2018 at 10:01 Paul Moore wrote: > On 30 January 2018 at 17:10, Antoine Pitrou wrote: > > > > This is missing a bit of context. Is this about python-dev? Some > > other ML? > > While I'll admit to being curious about what prompted this,

[Python-Dev] Friendly reminder: be kind to one another

Over the last 3 days I have had two situations come up where I was asked for my opinion in regards to possible CoC violations. I just wanted to take this opportunity to remind everyone that open source does not work if we are not open, considerate, and respectful to one another (which also happens

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

On Thu, 25 Jan 2018 at 17:33 Eric V. Smith 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 starting to deviate from the original topic here which > >> is: please replace # with GH- when you click Squash &

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

On Thu, 25 Jan 2018 at 10:51 Berker Peksağ wrote: > On Thu, Jan 25, 2018 at 9:38 PM, Mariatta Wijaya > wrote: > >> That would be best solution (I think it would solve > >> https://github.com/python/miss-islington/issues/16 too) but it's more >

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

On Thu, 25 Jan 2018 at 10:14 Zachary Ware wrote: > On Thu, Jan 25, 2018 at 12:03 PM, Mariatta Wijaya > wrote: > >> Of course, we would still need to convince people to install it :) > > > > > > Right, that's the challenge :) > > I

Re: [Python-Dev] Support of the Android platform

On Mon, 22 Jan 2018 at 09:29 Victor Stinner wrote: > Hi, > > I'm still talking with Paul Peny (pmpp on IRC) who is trying to build > the master branch of Python on Android, using cross-compilation or > directly on an Android device. I started to took notes since Android

Re: [Python-Dev] Slipping Python 3.5.5rc1 and 3.4.8rc1 because of a Travis CI issue--can someone make Travis CI happy?

I can switch off the requirement that holds admins to having to pass the same status checks as everyone else (there's still a big warning when you exercise this power), that way you can override the merge if you want. Not sure if you want to ignore the CI in that case as well. On Mon, 22 Jan 2018

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

On Thu, 18 Jan 2018 at 21:39 Benjamin Peterson wrote: > +1 to both of your specific proposals. > > More generally, I think it makes good sense to allow dropping support for > a platform in the next major Python release after vendor support for the > platform stops. Even we

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

On Fri, 19 Jan 2018 at 01:30 Pablo Galindo Salgado wrote: > Hello everyone, > > In today's episode of exposing useful Linux system calls I am exposing > preadv2 in this PR: > > https://github.com/python/cpython/pull/5239 > > as requested in this issue: > >

Re: [Python-Dev] python exe installer is broken

This seems like a bug report and is best reported on bugs.python.org. On Wed, 17 Jan 2018 at 08:05 Joshua Yeow wrote: > Dear Python Developers > I hope to be able to use the latest version Python on my Windows 7 PC > soon. The installer is very buggy and as I have

Re: [Python-Dev] Deprecate PEP 370 Per user site-packages directory?

On Sat, Jan 13, 2018, 17:27 Alex Walters, wrote: > I would suggest throwing this to -ideas, rather than just keeping it in > -dev > as there is a much wider community of users and usecases in -ideas. > > ... and -ideas will shoot it down because user installs are too

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

On Sat, Jan 13, 2018, 14:45 Christian Heimes, <christ...@python.org> wrote: > On 2018-01-13 21:02, Brett Cannon wrote: > > +1 from me as well for the improved security. > > Thanks, Brett! > > How should we handle CPython's Travis CI tests? The 14.04 boxes have > Op

Re: [Python-Dev] Deprecate PEP 370 Per user site-packages directory?

On Sat, Jan 13, 2018, 11:13 Miro Hrončok, wrote: > On 13.1.2018 18:06, Christian Heimes wrote: > > Nowadays Python has venv in the standard library. The user-specific > > site-packages directory is no longer that useful. I would even say it's > > causing more trouble than

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

On Sat, Jan 13, 2018, 05:24 Antoine Pitrou, wrote: > On Sat, 13 Jan 2018 13:54:33 +0100 > Christian Heimes wrote: > > > > If we agree to drop support for OpenSSL 0.9.8 and 1.0.1, then I can land > > bunch of useful goodies like proper hostname

Re: [Python-Dev] Best Python API for exposing posix_spawn

On Tue, 9 Jan 2018 at 02:42 Nick Coghlan wrote: > On 9 January 2018 at 20:01, Antoine Pitrou wrote: > > On Mon, 08 Jan 2018 09:11:38 + > > Pablo Galindo Salgado wrote: > >> Hi, > >> > >> I'm currently working on exposing

Re: [Python-Dev] Best Python API for exposing posix_spawn

On Mon, 8 Jan 2018 at 15:06 Gregory P. Smith wrote: > On Mon, Jan 8, 2018 at 12:36 PM Serhiy Storchaka > wrote: > >> 08.01.18 11:11, Pablo Galindo Salgado пише: >> > Following Gregory's comment on the PR I understand that he is proposing >> > to have three

Re: [Python-Dev] Best Python API for exposing posix_spawn

On Mon, 8 Jan 2018 at 07:57 Pablo Galindo Salgado wrote: > Hi, > > I'm currently working on exposing posix_spawn in the posix module (and by > extension in the os module). You can find the initial implementation in > this PR: > > https://github.com/python/cpython/pull/5109 >

Re: [Python-Dev] Unique loader per module

Barry and I had a meeting at work today and we decided to go with Nick's idea of using a get_resource_reader(fullname) method on loaders. We aren't going to go with an ABC and simply depend on the method existing as implementing the API (and then returning None if the loader can't handle the

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

On Tue, 26 Dec 2017 at 21:00 Ned Batchelder wrote: > On 12/26/17 1:49 PM, Chris Barker wrote: > > On Sat, Dec 23, 2017 at 5:54 PM, Nick Coghlan wrote: > >> >> I still wonder about the "fields *must* be annotated" constraint though. >> I can understand

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

On Fri, Dec 22, 2017, 11:38 Chris Barker, <chris.bar...@noaa.gov> wrote: > On Fri, Dec 22, 2017 at 8:49 AM, Brett Cannon <br...@python.org> wrote: > >> I think it's worth reminding people that if they don't like the fact >>> dataclasses (ab)use type hints for t

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

On Thu, Dec 21, 2017, 03:37 Ivan Levkivskyi, wrote: > On 21 December 2017 at 11:22, Terry Reedy wrote: > >> 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

Re: [Python-Dev] Decision of having a deprecation period or not for changing csv.DictReader returning type.

On Mon, 18 Dec 2017 at 07:30 Steve Holden wrote: > I submitted the 3.6 patch that Raymond committed. The purpose of the > change was to allow access to the ordering of the columns. > > It doesn't use any of the OrderedDict-only methods, and I'd be very > surprised if a

Re: [Python-Dev] Support of the Android platform

While the note from a technical standpoint is interest, Xavier, I don't quite see what needs to be done to support Android at this point. Are you simply asking we add Android API 24 as an official platform? Or permission to add your note to the Misc/ directory? Basically what are you wanting to

Re: [Python-Dev] PEP 540: Add a new UTF-8 mode (v2)

On Wed, 6 Dec 2017 at 06:10 INADA Naoki wrote: > >> And I have one worrying point. > >> With UTF-8 mode, open()'s default encoding/error handler is > >> UTF-8/surrogateescape. > > > > The Strict UTF-8 Mode is for you if you prioritize correctness over > usability. > >

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

On Tue, 5 Dec 2017 at 08:31 Senthil Kumaran wrote: > On Tue, Dec 5, 2017 at 6:25 AM, Victor Stinner > wrote: > >> Stéphane Wirtel gave a talk last month at Pycon CA about CPython pull >> requests. His slides: >> >>

Re: [Python-Dev] Third and hopefully final post: PEP 557, Data Classes

On Thu, 30 Nov 2017 at 05:00 Eric V. Smith wrote: > On 11/30/2017 6:59 AM, Antoine Pitrou wrote: > > > > Or, simply, is_dataclass_instance(), which is even longer, but far more > > readable thanks to explicit word boundaries :-) > > That actually doesn't bother me. I think

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

On Thu, 30 Nov 2017 at 05:01 David Cuthbert wrote: > Henk-Jaap noted that the grammar section of the language ref for yield and > return should also be updated from expression_list to starred_list with > this change. As noted elsewhere, this isn't in-sync with the Grammar file >

Re: [Python-Dev] Can Python guarantee the order of keyword-only parameters?

On Tue, 28 Nov 2017 at 03:33 Nick Coghlan wrote: > On 28 November 2017 at 15:42, Larry Hastings wrote: > > On 11/27/2017 03:58 PM, Yury Selivanov wrote: > >> We can't say anything about the order if someone passes a partial > >> object > > > > Sure we

Re: [Python-Dev] Second post: PEP 557, Data Classes

On Sat, Nov 25, 2017, 14:00 Eric V. Smith, wrote: > The updated version should show up at > https://www.python.org/dev/peps/pep-0557/ shortly. > > The major changes from the previous version are: > > - Add InitVar to specify initialize-only fields. > - Renamed

Re: [Python-Dev] Tricky way of of creating a generator via a comprehension expression

On Fri, Nov 24, 2017, 19:32 Guido van Rossum, wrote: > On Fri, Nov 24, 2017 at 4:22 PM, Guido van Rossum > wrote: > >> The more I hear about this topic, the more I think that `await`, `yield` >> and `yield from` should all be banned from occurring in all

Re: [Python-Dev] Tricky way of of creating a generator via a comprehension expression

I've now ended up in Guido's boat of needing a summary since I think this thread has grown to cover whether yield should be allowed in comprehensions, something about await in comprehensions, and now about leaking the loop variable (or some implementation detail). IOW there seems to be 3 separate

Re: [Python-Dev] Show DeprecationWarning in debug mode?

+1 from me as well. On Sat, Nov 18, 2017, 02:36 Serhiy Storchaka, wrote: > 18.11.17 03:22, Victor Stinner пише: > > I noticed that Python not only hides DeprecationWarning, but also > > PendingDeprecationWarning and ImportWarning by default. While I > > understand why we

Re: [Python-Dev] unittest isolation and warnings

Tests are not isolated from the warnings system, so things will leak out. Your best option is to use the context manager in the warnings module to temporarily make all warnings raise exceptions and test for the exception (I'm at the airport, hence why I don't know the name of the context manager;

Re: [Python-Dev] module customization

On Wed, 15 Nov 2017 at 16:27 Ethan Furman wrote: > So there are currently two ways to customize a module, with PEP 562 > proposing a third. > > The first method involves creating a standard class object, instantiating > it, and replacing the sys.modules entry with it. > > The

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

On Sun, Nov 12, 2017, 10:22 Koos Zevenhoven, wrote: > On Nov 12, 2017 19:10, "Guido van Rossum" wrote: > > On Sun, Nov 12, 2017 at 4:14 AM, Koos Zevenhoven > wrote: > >> So actually my question is: What should happen when the annotation

Re: [Python-Dev] Standardise the AST (Re: PEP 563: Postponed Evaluation of Annotations)

On Mon, Nov 13, 2017, 13:37 Greg Ewing, wrote: > Guido van Rossum wrote: > > But Python's syntax changes in nearly every release. > > The changes are almost always additions, so there's no > reason why the AST can't remain backwards compatible. > > > the AST level

Re: [Python-Dev] Python 3.6.3 venv FAILURE

Please file bugs at bugs.python.org. On Fri, Nov 10, 2017, 16:40 Larry Chen, wrote: > Upgraded from 3.6.1 to 3.6.3; but got an error when trying to create my > virtual environment. > > > > [larrchen@rslab239 Larry]$ /opt/python3.6.3/bin/python3.6 -m venv >

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

On Thu, Nov 9, 2017, 17:33 Nathaniel Smith, wrote: > On Nov 8, 2017 16:12, "Nick Coghlan" wrote: > > On 9 November 2017 at 07:46, Antoine Pitrou wrote: > > > > Le 08/11/2017 à 22:43, Nick Coghlan a écrit : > >> > >> However, between them,

Re: [Python-Dev] Remove typing from the stdlib

On Tue, 7 Nov 2017 at 03:34 Paul Moore wrote: > On 7 November 2017 at 10:18, Steve Holden wrote: > > On Tue, Nov 7, 2017 at 12:35 AM, Donald Stufft wrote: > > [..] > > > >> > >> Maybe we just need to fully flesh out the idea of a

Re: [Python-Dev] Guarantee ordered dict literals in v3.7?

On Mon, 6 Nov 2017 at 11:08 Paul Sokolovsky <pmis...@gmail.com> wrote: > Hello, > > On Mon, 06 Nov 2017 17:58:47 + > Brett Cannon <br...@python.org> wrote: > > [] > > > > Why suddenly once in 25 years there's a need to do something to > > > d

Re: [Python-Dev] Allow annotations using basic types in the stdlib?

On Mon, Nov 6, 2017, 10:27 R. David Murray, wrote: > I agree with Steve. There is *cognitive* overhead to type annotations. > I find that they make Python code harder to read and understand. So I > object to them in the documentation and docstrings as well. (Note: >

Re: [Python-Dev] Proposal: go back to enabling DeprecationWarning by default

On Mon, 6 Nov 2017 at 00:30 Victor Stinner wrote: > 2017-11-06 8:47 GMT+01:00 Serhiy Storchaka : > > 06.11.17 09:09, Guido van Rossum пише: > >> > >> I still find this unfriendly to users of Python scripts and small apps > who > >> are not the

Re: [Python-Dev] Guarantee ordered dict literals in v3.7?

On Mon, 6 Nov 2017 at 08:36 Paul Sokolovsky wrote: > Hello, > > On Mon, 6 Nov 2017 14:30:45 +0100 > Antoine Pitrou wrote: > > > On Tue, 7 Nov 2017 00:14:35 +1100 > > Steven D'Aprano wrote: > > > On Mon, Nov 06, 2017 at 12:27:54PM

Re: [Python-Dev] Remove typing from the stdlib

On Fri, 3 Nov 2017 at 17:59 Lukasz Langa wrote: > > > On 3 Nov, 2017, at 4:01 PM, Victor Stinner > wrote: > > > > The question is if you would only need or > pip install typing>. > > > > If typing is removed from the stdlib, you can still use it in

Re: [Python-Dev] [edk2] Official port of Python on EDK2

Since the initial email got cross-posted, would it be possible to drop python-dev from any discussing that doesn't directly involve Python itself (e.g. we don't need to be involved in a discussion about whether you all have threading on UEFI)? On Fri, 3 Nov 2017 at 07:57 Michael Zimmermann

Re: [Python-Dev] Remove typing from the stdlib (was: Reminder: 12 weeks to 3.7 feature code cutoff)

On Fri, 3 Nov 2017 at 08:09 Paul Moore wrote: > On 3 November 2017 at 14:50, Serhiy Storchaka wrote: > > 03.11.17 16:36, Guido van Rossum пише: > >> Maybe we should remove typing from the stdlib? > >> https://github.com/python/typing/issues/495 > > > >

Re: [Python-Dev] PEP 511 (code transformers) rejected

On Wed, 1 Nov 2017 at 16:17 Lukasz Langa wrote: > I find this sad. In the JavaScript community the existence of Babel is > very important for the long-term evolution of the language independently > from the runtime. With Babel, JavaScript programmers can utilize new > language

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

On Thu, 2 Nov 2017 at 08:46 Steven D'Aprano wrote: > On Wed, Nov 01, 2017 at 03:48:00PM -0700, Lukasz Langa wrote: > > > PEP: 563 > > Title: Postponed Evaluation of Annotations > > > This PEP proposes changing function annotations and variable annotations > > so that they

Re: [Python-Dev] [edk2] Official port of Python on EDK2

The official guidelines on what it takes to add official support for a platform is https://www.python.org/dev/peps/pep-0011/#supporting-platforms. Basically it's a core dev willing to sponsor and maintain the work, a buildbot, and implicitly at least a 5 year commitment. On Wed, 1 Nov 2017 at

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

On Mon, 30 Oct 2017 at 09:36 Mariatta Wijaya wrote: > > Except of Antoine Pitrou, does everybody else like the new UI? :-) > > I love the new UI. +1000 for migrating. > I personally prefer MM3 + HyperKitty compared to MM2 + pipermail. -Brett > > > > Mariatta Wijaya

Re: [Python-Dev] The type of the result of the copy() method

It probably should be more consistent and I have a vague recollection that this has been brought up before. On Sun, Oct 29, 2017, 08:21 Serhiy Storchaka, wrote: > The copy() methods of list, dict, bytearray, set, frozenset, > WeakValueDictionary, WeakKeyDictionary return an

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

On Fri, 20 Oct 2017 at 06:42 Ronald Oussoren <ronaldousso...@mac.com> wrote: > Op 10 okt. 2017 om 01:48 heeft Brett Cannon <br...@python.org> het > volgende geschreven: > > > > On Mon, Oct 2, 2017, 17:49 Ronald Oussoren, <ronaldousso...@mac.com> > wrote: &

Re: [Python-Dev] Intention to accept PEP 552 soon (deterministic pyc files)

On Wed, Oct 4, 2017, 09:00 Antoine Pitrou, wrote: > On Wed, 4 Oct 2017 10:14:22 -0400 > Barry Warsaw wrote: > > On Oct 3, 2017, at 13:29, Benjamin Peterson wrote: > > > > > I'm not sure turning the implementation details of our

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

On Mon, Oct 2, 2017, 17:49 Ronald Oussoren, <ronaldousso...@mac.com> wrote: > Op 3 okt. 2017 om 04:29 heeft Barry Warsaw <ba...@python.org> het > volgende geschreven: > > > On Oct 2, 2017, at 14:56, Brett Cannon <br...@python.org> wrote: > > > >>

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

On Mon, Oct 2, 2017, 13:56 Antoine Pitrou, <solip...@pitrou.net> wrote: > On Mon, 02 Oct 2017 18:56:15 +0000 > Brett Cannon <br...@python.org> wrote: > > > > So Mercurial specifically is an odd duck because they already do lazy > > importing (in fact they are

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

On Mon, Oct 2, 2017, 12:30 Barry Warsaw, <ba...@python.org> wrote: > On Oct 2, 2017, at 14:56, Brett Cannon <br...@python.org> wrote: > > > So Mercurial specifically is an odd duck because they already do lazy > importing (in fact they are using the lazy loa

Re: [Python-Dev] Intention to accept PEP 552 soon (deterministic pyc files)

On Sat, 30 Sep 2017 at 18:46 Benjamin Peterson <benja...@python.org> wrote: > What do you mean by bytecode-specific APIs? The internal importlib ones? > There's that, but more specifically py_compile and compileall. -Brett > > On Fri, Sep 29, 2017, at 09:38, Brett Can

Re: [Python-Dev] Python startup optimization: script vs. service

On Mon, 2 Oct 2017 at 11:19 Christian Heimes <christ...@python.org> wrote: > On 2017-10-02 19:29, Brett Cannon wrote: > > My current design for an opt-in lazy importing setup includes an > > explicit function for importlib that's mainly targeted for the stdlib > > an

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

On Mon, 2 Oct 2017 at 02:43 Raymond Hettinger wrote: > > > On Oct 2, 2017, at 12:39 AM, Nick Coghlan wrote: > > > > "What requests uses" can identify a useful set of > > avoidable imports. A Flask "Hello world" app could likely provide > >

Re: [Python-Dev] Python startup optimization: script vs. service

On Mon, 2 Oct 2017 at 08:00 Christian Heimes wrote: > On 2017-10-02 15:26, Victor Stinner wrote: > > 2017-10-02 13:10 GMT+02:00 INADA Naoki : > >> https://github.com/python/cpython/pull/3796 > >> In this PR, lazy loading only happens when uuid1 is

Re: [Python-Dev] Intention to accept PEP 552 soon (deterministic pyc files)

BTW, if you find the bytecode-specific APIs are sub-par while trying to update them, let me know as I have been toying with cleaning them up and centralizing them under importlib for a while and just never gotten around to sitting down and coming up with a better design that warranted putting the

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

I should mention that I have a prototype design for improving importlib's lazy loading to be easier to turn on and use. See https://notebooks.azure.com/Brett/libraries/di2Btqj7zSI/html/Lazy%20importing.ipynb for my current notes. Part of it includes an explicit lazy_import() function which would

Re: [Python-Dev] PEP 549: Instance Properties (aka: module properties)

On Thu, 14 Sep 2017 at 12:09 Ivan Levkivskyi wrote: > On 14 September 2017 at 01:13, Guido van Rossum wrote: > >> >> That last sentence is a key observation. Do we even know whether there >> are (non-toy) things that you can do *in principle* with

Re: [Python-Dev] PEP 552: deterministic pycs

On Fri, 8 Sep 2017 at 10:53 Benjamin Peterson wrote: > Thank you all for the feedback. I've now updated the PEP to specify a > 4-word pyc header with a bit field in every case. > > On Fri, Sep 8, 2017, at 09:43, Nick Coghlan wrote: > > On 8 September 2017 at 07:55, Antoine

Re: [Python-Dev] pythonhosted.org doc upload no longer works

This is actually a question for distutils-sig since they manage PyPI. On Mon, 4 Sep 2017 at 03:50 Giampaolo Rodola' wrote: > I know pythonhosted.org was deprecated long ago in favor of readthedocs > but I kept postponing it and my doc for psutil is still hosted on >

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

On Wed, 30 Aug 2017 at 02:56 Paul Moore wrote: > On 30 August 2017 at 10:48, Nick Coghlan wrote: > > On 30 August 2017 at 19:39, Antoine Pitrou wrote: > >> On Wed, 30 Aug 2017 08:48:56 +0300 > >> Serhiy Storchaka

Re: [Python-Dev] PEP 550 v3

On Sun, Aug 20, 2017, 03:08 Antoine Pitrou wrote: > On Sat, 19 Aug 2017 17:21:03 -0700 > Guido van Rossum wrote: > > The way we came to "logical context" was via "logical thread (of > control)", > > which is distinct from OS thread. But I think we

Re: [Python-Dev] Buildbot report, August 2017

Thanks for all of this, Victor! On Fri, Aug 18, 2017, 09:38 Victor Stinner wrote: > Hi, > > Here is a quick report of what changed recently on buildbots. > > > == pythoninfo == > > I added a new "python3 -m test.pythoninfo" command which is now run on > Travis CI,

Re: [Python-Dev] PEP 550 v3

On Sat, Aug 19, 2017, 01:43 Antoine Pitrou wrote: > On Fri, 18 Aug 2017 16:33:27 -0400 > Yury Selivanov wrote: > > > > There are a few open questions left, namely the terminology > > and design of ContextKey API. On the former topic, I'm quite > >

Re: [Python-Dev] __signature__ for PySide ready

On Fri, 18 Aug 2017 at 02:05 Christian Tismer wrote: > Hi friends, > > in the last months, I have developed signature support for > PySide. The module creates the same signatures as are known > for plain Python functions. > > As a non-trivial addition, the module also

Re: [Python-Dev] python issue27584 AF_VSOCK support

Since everyone is a volunteer, Cathy, there are unfortunately no real timelines. It really comes down to someone who feels they have the knowledge necessary to review the PR having the spare time to do so. So emailing here and saying, "my PR has addressed all the comments and has been ready to go

[Python-Dev] Pull requests now have labels specifying what stage they are at

I just pushed a change to Bedevere to help track what stage a pull request is in. The stages are: - awaiting review - awaiting core review - awaiting changes - awaiting change review - awaiting merge The "review" stage is for when a pull request has no reviews either approving or

Re: [Python-Dev] Appending a link back to bugs.python.org in GitHub PRs

ett > > On Fri, Jul 21, 2017 at 5:28 PM, Brett Cannon <br...@python.org> wrote: > >> Thanks to Kushal Das we now have one of the most requested features since >> the transition: a link in PRs back to bugs.python.org (in a more >> discoverable way since we have had them

Re: [Python-Dev] Python startup time

On Sun, Jul 23, 2017, 10:52 Michel Desmoulin, <desmoulinmic...@gmail.com> wrote: > > > Le 23/07/2017 à 19:36, Brett Cannon a écrit : > > > > > > On Sun, Jul 23, 2017, 00:53 Michel Desmoulin, <desmoulinmic...@gmail.com > > <mailto:desmoulinmic...@gmail.

Re: [Python-Dev] Python startup time

On Sun, Jul 23, 2017, 00:53 Michel Desmoulin, wrote: > > > > Optimizing startup time is incredibly valuable, > > I've been reading that from the beginning of this thread but I've been > using python since the 2.4 and I never felt the burden of the startup time. > > I'm

Re: [Python-Dev] Python startup time

On Sat, Jul 22, 2017, 07:22 Steve Dower, wrote: > I believe the trend is due to language like Python and Node.js, most of > which aggressively discourage threading (more from the broader community > than the core languages, but I see a lot of apps using these now), and

[Python-Dev] Appending a link back to bugs.python.org in GitHub PRs

Thanks to Kushal Das we now have one of the most requested features since the transition: a link in PRs back to bugs.python.org (in a more discoverable way since we have had them since Bedevere launched :) . When a pull request comes in with an issue number in the title (or one gets added), a link

Re: [Python-Dev] startup time repeated? why not daemon

On Thu, 20 Jul 2017 at 22:11 Chris Jerdonek wrote: > On Thu, Jul 20, 2017 at 8:49 PM, Nick Coghlan wrote: > > ... > > * Lazy loading can have a significant impact on startup time, as it > > means you don't have to pay for the cost of finding and

Re: [Python-Dev] Design Philosophy: Performance vs Robustness/Maintainability

On Tue, 18 Jul 2017 at 09:07 Ethan Furman wrote: > Raymond Hettinger: > - > > One minor grumble: I think we need to give careful cost/benefit > considerations to > > optimizations that complicate the implementation. Over the last > several years, the > >

Re: [Python-Dev] Impact of Namedtuple on startup time

On Mon, 17 Jul 2017 at 19:26 Nathaniel Smith <n...@pobox.com> wrote: > On Jul 17, 2017 5:28 PM, "Steven D'Aprano" <st...@pearwood.info> wrote: > > On Mon, Jul 17, 2017 at 09:31:20PM +, Brett Cannon wrote: > > > As for removing exec() as a goal, I'll b

Re: [Python-Dev] Impact of Namedtuple on startup time

On Mon, 17 Jul 2017 at 13:28 Raymond Hettinger wrote: > > > On Jul 17, 2017, at 8:49 AM, Guido van Rossum wrote: > > > > One of the reasons to be wary of exec()/eval() other than the usual > security concerns is that in some Python implementations

Re: [Python-Dev] [python-committers] Python 3.3.7 release schedule and end-of-life

A quick thanks from me, Ned, for stepping forward to help 3.3 pine for the fjords. On Sat, Jul 15, 2017, 14:51 Ned Deily, wrote: > Python 3.3 is fast approaching its end-of-life date, 2017-09-29. Per our > release policy, that date is five years after the initial release of

Re: [Python-Dev] Improve test coverage for standard library

In general the answer to helping with code coverage is "whatever module motivates you to help". :) So unless a core dev has a specific module that they want to help you write tests for then it's whatever you want to work on. And for easy reference, the code coverage report can be found at

Re: [Python-Dev] New work-in-progress bisection tool for the Python test suite (in regrtest)

On Mon, 26 Jun 2017 at 13:38 Victor Stinner <victor.stin...@gmail.com> wrote: > 2017-06-26 21:58 GMT+02:00 Brett Cannon <br...@python.org>: > > I don't see why regrtest isn't the right place for this. > > The current regrest CLI isn't designed for subcommands, and

Re: [Python-Dev] Helping contributors with chores (do we have to?)

[It seems to me most of this thread has gone off-topic since it now includes what I consider a sexist comment, complaining about git, and discussing people's credentials in terms of being able to comment on something, I'm basically ignoring everything that came after this email as none of that has

Re: [Python-Dev] New workflow change: Welcome to blurb

On Mon, 26 Jun 2017 at 14:28 Terry Reedy <tjre...@udel.edu> wrote: > On 6/25/2017 4:09 PM, Guido van Rossum wrote: > > On Sun, Jun 25, 2017 at 12:23 PM, Brett Cannon <br...@python.org > > <mailto:br...@python.org>> wrote: > > > > > > >

Re: [Python-Dev] New work-in-progress bisection tool for the Python test suite (in regrtest)

On Mon, 26 Jun 2017 at 09:38 Victor Stinner wrote: > Hi, > > I updated my bisect_test.py script to simplify its command line: > >https://github.com/haypo/misc/blob/master/python/bisect_test.py > > To debug a reference leak in test_os, now just type: > >$

Re: [Python-Dev] New workflow change: Welcome to blurb

On Sun, 25 Jun 2017 at 20:56 Nick Coghlan <ncogh...@gmail.com> wrote: > On 26 June 2017 at 02:39, Brett Cannon <br...@python.org> wrote: > > On Sat, Jun 24, 2017, 23:45 Nick Coghlan, <ncogh...@gmail.com> wrote: > >> I was mainly referring to

Re: [Python-Dev] New workflow change: Welcome to blurb

On Sun, Jun 25, 2017, 11:24 Terry Reedy, <tjre...@udel.edu> wrote: > On 6/25/2017 12:39 PM, Brett Cannon wrote: > > > The entire reason I want to have this check is I don't want or have to > > ask another PR submitter to include a draft of a news item. It's much > &

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