[Python-Dev] Re: Require a C compiler supporting C99 to build Python 3.11

On Mon, Feb 7, 2022 at 9:12 AM Victor Stinner wrote: > Hi, > > I made a change to require C99 "NAN" constant and I'm was > asked to update the PEP 7 to clarify the C subset is needed to build > Python 3.11. > > Python 3.6 requires a subset of the C99 standard to build defined by the > PEP 7: > h

[Python-Dev] Re: RFC on PEP 675: Arbitrary Literal Strings

On Mon, Feb 7, 2022 at 4:59 PM S Pradeep Kumar wrote: > On Mon, Feb 7, 2022 at 3:55 PM Brett Cannon wrote: > >> Can I suggest adding a "Specification" section (see >> https://www.python.org/dev/peps/pep-0012/#suggested-sections for the >> suggested sections to

[Python-Dev] Re: Steering Council reply to PEP 670 -- Convert macros to functions in the Python C API

On Tue, Feb 8, 2022 at 8:30 AM Victor Stinner wrote: > Hi Petr, > > Thanks for the SC review, it's very helpful! I know that it's a big PEP :-) > > On Tue, Feb 8, 2022 at 11:33 AM Petr Viktorin wrote: > > *All other things being equal, static inline functions are better than > > macros.* > > Spe

[Python-Dev] Re: It's now time to deprecate the stdlib urllib module

On Mon, Feb 7, 2022 at 5:51 PM Jim J. Jewett wrote: > There are problems with urllib. With hindsight, it would have been nice > to do a few things differently. But that doesn't make migrating away from > it any easier. > > This thread has mentioned several "better" alternatives -- but with the

[Python-Dev] Re: Require a C compiler supporting C99 to build Python 3.11

On Wed, Feb 9, 2022 at 4:19 AM Petr Viktorin wrote: > > > On 09. 02. 22 4:39, h.vetin...@gmx.com wrote: > >> Maybe a more practical approach would be to use C99 "except of > > features not supported by MSVC of Visual Studio 2019"? > > > > This could be formulated in a more neutral way by saying >

[Python-Dev] Re: Should we require IEEE 754 floating-point for CPython?

On Tue, Feb 8, 2022 at 10:20 PM Steven D'Aprano wrote: > On Tue, Feb 08, 2022 at 05:48:46PM -0800, Gregory P. Smith wrote: > > On Tue, Feb 8, 2022 at 2:41 PM Steven D'Aprano > wrote: > > > > If the answer to those questions are Yes, that rules out using Unums, > > > posits, sigmoid numbers etc a

[Python-Dev] Re: Request for feedback: pathlib.AbstractPath prototype

One thing to discuss (and which has been brought up on the PR), is whether this should be an ABC to force people to explicitly raise `NotImplementedError`? The next question is whether any of this should be a (very wide) protocol instead of an ABC? On Wed, Feb 9, 2022 at 7:05 AM Barney Gale wrot

[Python-Dev] Re: Request for feedback: pathlib.AbstractPath prototype

implement. -Brett > > On Wed, 9 Feb 2022 at 19:02, Brett Cannon wrote: > >> One thing to discuss (and which has been brought up on the PR), is >> whether this should be an ABC to force people to explicitly raise >> `NotImplementedError`? >> >> The next que

[Python-Dev] Re: Request for feedback: pathlib.AbstractPath prototype

On Thu, Feb 10, 2022 at 2:15 PM Ethan Furman wrote: > On 2/10/22 1:45 PM, Brett Cannon wrote: > > > Protocols would let folks rely on a common Path object API w/o having > to require the object > > come from pathlib itself or explicitly subclass something (which I >

[Python-Dev] Re: PEP 683: "Immortal Objects, Using a Fixed Refcount" (round 2)

On Wed, Feb 23, 2022 at 8:19 AM Petr Viktorin wrote: > On 23. 02. 22 2:46, Eric Snow wrote: > > [SNIP] > > > So it seems like the bar should be pretty low for this one (assuming > > we get the performance penalty low enough). If it were some massive > > or broadly impactful (or even clearly pu

[Python-Dev] Re: October/November/December Steering Council update

On Tue, Mar 1, 2022 at 9:00 AM Joannah Nanjekye wrote: > > Steering Council did a one hour Q&A recorded session with Visionary > sponsor, Bloomberg. > > Is it possible to access this recording for transparency purposes or is > it confidential? > We can ask, but I vaguely remember the folks at Bl

[Python-Dev] Re: Test error

You might want to try asking your question at https://mail.python.org/mailman3/lists/core-mentorship.python.org/ which is specifically set up to help people. But in general, all the tests are passing for folks. You will need to run those tests individually to see why they are failing for you. On

[Python-Dev] Defining tiered platform support

Do we officially support NetBSD? Do you know how to find out if we do? You might think to look at https://www.python.org/dev/peps/pep-0011/#supporting-platforms , but that just loosely defines the criteria and it still doesn't list the actual platforms we support. (BTW I don't know if we do officia

[Python-Dev] Re: Defining tiered platform support

On Fri, Mar 4, 2022 at 12:48 AM Christian Heimes wrote: > Hi Brett, > > thanks for starting the discussion! Much appreciated. > > On 04/03/2022 00.30, Brett Cannon wrote: > > Tier 1 is the stuff we run CI against: latest Windows, latest macOS, > > Linux w/ the late

[Python-Dev] Re: Defining tiered platform support

On Fri, Mar 4, 2022 at 1:32 AM Ronald Oussoren wrote: > > > On 4 Mar 2022, at 00:30, Brett Cannon wrote: > > Do we officially support NetBSD? Do you know how to find out if we do? You > might think to look at > https://www.python.org/dev/peps/pep-0011/#supporting-platfo

[Python-Dev] Re: Defining tiered platform support

On Fri, Mar 4, 2022 at 1:44 AM Petr Viktorin wrote: > On 04. 03. 22 0:30, Brett Cannon wrote: > > Do we officially support NetBSD? Do you know how to find out if we do? > > You might think to look at > > https://www.python.org/dev/peps/pep-0011/#supporting-platforms > &

[Python-Dev] Re: Defining tiered platform support

On Mon, Mar 7, 2022 at 11:01 AM Christian Heimes wrote: > On 04/03/2022 21.41, Brett Cannon wrote: > > Therefore I propose that we target the oldest manylinux standard > > accepted by PyPI, for which the operating system has not reached its > > EOL.

[Python-Dev] Re: Defining tiered platform support

On Mon, Mar 7, 2022 at 11:05 AM Christian Heimes wrote: > On 07/03/2022 18.02, Petr Viktorin wrote: > >> Why the devguide? I view the list of platforms as important for public > >> consumption as for the core dev team to know what to (not) accept PRs > >> for. > > > > So, let's put it in the main

[Python-Dev] Re: Defining tiered platform support

On Fri, Mar 11, 2022 at 5:17 PM Victor Stinner wrote: > It would be great to have the list of supported platforms per Python > version! > I could see the table in PEP 11 being copied into the release PEPs. > > Maybe supporting new platforms and dropping support for a platform > should be docum

[Python-Dev] Re: Defining tiered platform support

On Mon, Mar 14, 2022 at 11:18 PM Larry Hastings wrote: > > On 3/14/22 20:31, Brett Cannon wrote: > > > > On Fri, Mar 11, 2022 at 5:17 PM Victor Stinner > wrote: > >> It would be great to have the list of supported platforms per Python >> version! >>

[Python-Dev] Gathering edge cases around type annotation PEPs

I created https://discuss.python.org/t/finding-edge-cases-for-peps-484-463-and-649-type-annotations/14314 on behalf of the SC to help gather edge cases where the various approaches that PEPs have proposed will fail. Our hope is to get an overall picture of the trade-offs the various PEPs ask us to

[Python-Dev] Re: C API: Move PEP 523 "Adding a frame evaluation API to CPython" private C API to the internal C API

On Wed, Mar 23, 2022 at 2:48 AM Petr Viktorin wrote: > On 22. 03. 22 19:07, Victor Stinner wrote: > > Hi, > > > > I proposed two PRs to move the private C API (Include/cpython/) of PEP > > 523 "Adding a frame evaluation API to CPython" to the internal C API > > (Include/internals/): > > > > * htt

[Python-Dev] Re: Enhancing generic type documentation in the standard library

On Wed, Mar 23, 2022 at 11:03 AM Luciano Ramalho wrote: > Hello, everyone! > > I believe our documentation about types needs another overhaul. > The SC somewhat agrees! 😉 See https://mail.python.org/archives/list/typing-...@python.org/thread/TVMQJXOJFOYFPDMQDFG6G4B6J3MLRYKB/ where we have asked

[Python-Dev] Re: Are "Batteries Included" still a Good Thing? [was: It's now time to deprecate the stdlib urllib module]

On Mon, Mar 28, 2022 at 11:52 AM Christopher Barker wrote: > On Mon, Mar 28, 2022 at 11:29 AM Paul Moore wrote: > >> To be honest, I feel like I'm just reiterating stuff I've said before >> here, and I think the same is true of the points I'm responding to > > ... > >> (I'm not *against* going

[Python-Dev] Re: Enhancing generic type documentation in the standard library

On Mon, Mar 28, 2022 at 3:58 PM Luciano Ramalho wrote: > On Wed, Mar 23, 2022 at 5:01 PM Brett Cannon wrote: > > The SC somewhat agrees! 😉 See > https://mail.python.org/archives/list/typing-...@python.org/thread/TVMQJXOJFOYFPDMQDFG6G4B6J3MLRYKB/ > where we have asked for at lea

[Python-Dev] Re: Are "Batteries Included" still a Good Thing? [was: It's now time to deprecate the stdlib urllib module]

On Tue, Mar 29, 2022 at 8:58 AM Ronald Oussoren wrote: > > > On 29 Mar 2022, at 00:34, Brett Cannon wrote: > > > > On Mon, Mar 28, 2022 at 11:52 AM Christopher Barker > wrote: > >> On Mon, Mar 28, 2022 at 11:29 AM Paul Moore wrote: >> >>> To b

[Python-Dev] Re: Are "Batteries Included" still a Good Thing? [was: It's now time to deprecate the stdlib urllib module]

On Wed, Mar 30, 2022 at 4:53 AM Barney Gale wrote: > On Wed, 30 Mar 2022 at 12:20, Antoine Pitrou wrote: > >> On Wed, 30 Mar 2022 12:03:58 +0100 >> Steve Dower wrote: >> > On 30Mar2022 1124, Barney Gale wrote: >> > > I'd like to become a maintainer for the pathlib module, if possible. >> I >> >

[Python-Dev] Re: About PEPs being discussed on Discourse

On Thu, Apr 7, 2022 at 7:33 PM Stephen J. Turnbull < stephenjturnb...@gmail.com> wrote: > Gregory P. Smith writes: > > > We feel it too. We've been finding Discourse more useful from a > community > > moderation and thread management point of view as well as offering > markdown > > text and cod

[Python-Dev] Re: Importing a submodule doesn't always set an attribute on its parent

On Fri, Apr 8, 2022 at 4:38 PM dfremont--- via Python-Dev < python-dev@python.org> wrote: > Hello, > > I came across what seems like either a bug in the import system or a gap > in its documentation, so I'd like to run it by folks here to see if I > should submit a bug report. If there's somewhere

[Python-Dev] Re: Importing a submodule doesn't always set an attribute on its parent

On Sat, Apr 9, 2022 at 1:53 PM dfremont--- via Python-Dev < python-dev@python.org> wrote: > Thanks, Brett. I understand why the behavior happens, I just don't > understand the decision to implement imports this way. Since there's no > warning in the documentation that removing items from sys.modul

[Python-Dev] Re: Declarative imports

On Sun, Apr 10, 2022 at 2:39 AM Daniel Pope wrote: > On Fri, 8 Apr 2022, 17:44 Guido van Rossum, wrote: > >> The interesting idea here seems to make "lazy imports" easier to >> implement by making them explicit in the code. So far, most lazy import >> frameworks for Python have done hacks with `

[Python-Dev] Proposal to deprecate mailcap

A CVE has been opened against mailcap (see https://github.com/python/cpython/issues/68966 for details). I'm not aware of anyone trying to maintain the module and Victor did a search online and didn't find any use of the module in the top 5000 projects on PyPI (see the issue). The module is also und

[Python-Dev] Re: GSOC

On Tue, Apr 19, 2022 at 7:14 AM Jean Abou Samra wrote: > Hi, > > Le 19/04/2022 à 01:56, faresbaso...@gmail.com a écrit : > > i want to contribute in mailman which is a sub-org under python software > > > Where do you see this? I can't find it under github.com/python. > The repository seems to be

[Python-Dev] Re: Python multithreading without the GIL

On Sat, Apr 23, 2022 at 8:31 AM wrote: > Hello all, > > I am very excited about a future multithreaded Python. I managed to > postpone some rewrites in the company I work for Rust/Go, precisely because > of the potential to have a Python solution in the medium term. > > I was wondering. Is Sam Gr

[Python-Dev] Re: Proto-PEP part 1: Forward declaration of classes

On Sat, Apr 23, 2022 at 2:39 PM Rob Cliffe via Python-Dev < python-dev@python.org> wrote: > UGH! > I understand you don't like the proposal, but do please try to keep it civil. It's totally okay to say you don't like something, but I don't think anyone would take kindly to someone coming up to th

[Python-Dev] Re: Proposal to deprecate mailcap

After talking about this in the SC today, we agreed to deprecate mailcap under the auspices of PEP 594: https://github.com/python/peps/commit/701999a91dc5f976c00d5bde1510226ebd9c7822 . On Thu, Apr 14, 2022 at 11:44 AM Brett Cannon wrote: > A CVE has been opened against mailcap (see >

[Python-Dev] Re: Add -P command line option to not add sys.path[0]

On Tue, Apr 26, 2022 at 2:50 AM Victor Stinner wrote: > Hi, > > There are 4 main ways to run Python: > > (1) python -m module [...] > (2) python script.py [...] > (3) python -c code [...] > (4) python [...] > > (1) and (2) insert the directory of the module/script at sys.path[0]. > (3) and (4) in

[Python-Dev] Re: Can I ask a real dumb procedural question about GitHub email?

On Wed, May 4, 2022 at 11:26 AM Skip Montanaro wrote: > I subscribe to the python/cpython stuff on GitHub. I find it basically > impossible to follow because of the volume. I realize there are > probably plenty of extra changes going in based on the recent language > summit (and maybe some sprint

[Python-Dev] Re: Migration plan for the distutils removal in Python 3.12

On Tue, May 10, 2022 at 12:59 AM Victor Stinner wrote: > Hi, > > Two years ago, PEP 632 "Deprecate distutils module" was accepted: the > distutils package was deprecated in Python 3.10 and scheduled for > removal in Python 3.12. Questions. > > * Is the Python ecosystem ready for the distutils rem

[Python-Dev] Re: Migration plan for the distutils removal in Python 3.12

On Tue, May 10, 2022 at 10:23 AM Guido van Rossum wrote: > Shouldn't we wean our internal tools off this obsolete version of > distutils too, rather than just move it around? > I think so. We technically have a year to get this done, so if we can't do that then I'm afraid we have much bigger iss

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

Can we shut this down or unsubscribe the weekly email? On Fri, May 13, 2022 at 11:13 AM Python tracker wrote: > > ACTIVITY SUMMARY (2022-05-06 - 2022-05-13) > Python tracker at https://bugs.python.org/ > > To view or respond to any of the issues listed below, click on the issue. > Do NOT respond

[Python-Dev] Re: PEP 689 – Unstable C API tier (was: Semi-stable C API tier)

We discussed having leading underscores for this API tier, and it was decided that a leading underscore was preferred. This did start a discussion, though, about whether we should control API access/opt-in via `#include` by having `.h` files that convey what API the user is opting into, or use

[Python-Dev] Re: PEP 689 – Unstable C API tier (was: Semi-stable C API tier)

much instability risk they were willing to take by having CI have an allowlist/blocklist of Python header files. -Brett > > Modifying preprocessor definitions for different Python versions, or > having to set them before knowing what version is being used, seems more > complicated.

[Python-Dev] Re: Method __func__ objects are unpicklable

I believe a lot of people use https://pypi.org/project/cloudpickle/ thanks to its support for pickling functions. On Fri, Jun 10, 2022 at 4:56 AM haael wrote: > > > During some sophisticated pickling I noticed that method `__func__` > objects are unpicklable, because they share the name with the

[Python-Dev] Re: New `python` Organization Repository Policy

On Fri, Jul 15, 2022 at 4:54 AM Joannah Nanjekye wrote: > I understand that the steering council decides new repositories that can > be added to the Python organization but as a committer, it is good courtesy > that public decisions are discussed first on committer channels because > this impacts

[Python-Dev] Re: compiling errors, SSL

On Tue, Jul 19, 2022 at 2:17 PM Kevin T via Python-Dev < python-dev@python.org> wrote: > I have built this on systems at work, that are populated by CAD guys who > have developed a good set of libraries to maintain in a linux > distribution. Went without a hitch. > > I am trying to build this at

[Python-Dev] Do not harass other mailing list subscribers privately

The SC has been notified of at least one instance of someone subscribed to this list harassing another subscriber privately. We wanted to remind folks that we expect people to behave reasonably towards each other, else people risk losing access to this mailing list and other places where Python is

[Python-Dev] Re: Switching to Discourse

On Thu, Jul 21, 2022 at 10:34 AM Skip Montanaro wrote: > > No, Discord is a different thing; it does text and voice communication > > channels in real-time. If you're familiar with Slack, it's broadly > > similar in purpose. > > Thanks (and to the others who replied). FYI this multiple response

[Python-Dev] Re: Switching to Discourse

On Fri, Jul 22, 2022 at 3:45 AM Samuel Colvin wrote: > Reading this thread and thinking about discuss.python.org/Discourse - I'm > surprised no one is advocating github discussions > . > I think it's because discuss.python.org is what we decided to try yea

[Python-Dev] Re: Moving to Discourse

On Thu, Sep 22, 2022 at 12:41 AM Baptiste Carvello < devel2...@baptiste-carvello.net> wrote: > Hello, > > Le 21/09/2022 à 13:14, Petr Viktorin a écrit : > > On 21. 09. 22 10:17, Baptiste Carvello wrote: > >> > >> * mailing-list mode: there needs to be a *standardized* set of filters > >> to access

[Python-Dev] Re: problem with Distributed File System Replication and Namespacing and different versions of Python 3

Import is implementing in Python itself via importlib, so you could try walking through the code with a debugger to see where the difference may be (I personally can't think of anything obvious that changed in importlib between 3.9 and 3.10 that would affect this). On Thu, Oct 20, 2022 at 11:36 AM

[Python-Dev] Re: problem with Distributed File System Replication and Namespacing and different versions of Python 3

On Fri, Oct 21, 2022 at 11:11 AM Juan Cristóbal Quesada < rainonthescarecrowhumanwhe...@gmail.com> wrote: > I guess my simplified question would be: > > ¿how does Python 3 versions manage Distributed File Systems and in > particular Windows' DFS? > In no specific way. We typically ask the OS to h

[Python-Dev] Re: A proposal to modify `None` so that it hashes to a constant

On Sun, Nov 27, 2022 at 11:36 AM Yoni Lavi wrote: > I wrote a doc stating my case here: > > https://docs.google.com/document/d/1et5x5HckTJhUQsz2lcC1avQrgDufXFnHMin7GlI5XPI/edit# > > Briefly, > > 1. The main motivation for it is to allow users to get a predictable > result on a given input (for pr

[Python-Dev] Re: A proposal to modify `None` so that it hashes to a constant

On Mon, Nov 28, 2022 at 5:38 PM Steven D'Aprano wrote: > On Mon, Nov 28, 2022 at 11:13:34PM +, Oscar Benjamin wrote: > > On Mon, 28 Nov 2022 at 22:56, Brett Cannon wrote: > > > > That's actually by design. Sets are not meant to be deterministic > > >

[Python-Dev] Re: A proposal to modify `None` so that it hashes to a constant

On Tue, Nov 29, 2022 at 12:58 PM Yoni Lavi wrote: > It does make your argument invalid though, It makes that single sentence invalid, but the rest of my points still hold, e.g. the language makes no guarantee about hash consistency between executions, set order is not guaranteed, etc. are all s

[Python-Dev] Re: Switching to Discourse

On Fri, Dec 2, 2022 at 8:17 AM Baptiste Carvello < devel2...@baptiste-carvello.net> wrote: > Le 02/12/2022 à 10:09, Gregory P. Smith a écrit : > > > > On Thu, Dec 1, 2022 at 8:37 AM Victor Stinner > > wrote: > > > > > > Should we *close* the python-dev mailing list

[Python-Dev] Re: Python Launcher not Installed on Windows Machine

How did you install Python? If you got it from the Microsoft Store I believe the Python Launcher is not included. On Tue, Dec 13, 2022 at 7:20 PM Margo Hoover wrote: > Dear Jonathan and Brian, > > I have python and pip installed on my Windows machine. However, I do not > seem to have the python

[Python-Dev] Re: Contributing the Pyston jit?

On Thu, Feb 23, 2023, 11:34 Wes Turner wrote: > Please consider colesbury/nogil in rebasing? > https://github.com/colesbury/nogil > It's very premature for anyone to concern themselves with Sam's nogil work when it comes to their own work as PEP 703 has not been sent to the SC (let alone been ac

[Python-Dev] Re: Contributing the Pyston jit?

FYI you will probably get more engagement if you posted this to discuss.python.org . On Thu, Feb 23, 2023, 10:18 Kevin Modzelewski wrote: > Hello all, we on the Pyston team would like to propose the contribution of > our JIT >

[Python-Dev] Re: please consider changing --enable-unicode default to ucs4

Python no longer has `--enable-unicode` as part of `./configure`. On Tue, Mar 14, 2023 at 9:26 AM Jonathan Benson via Python-Dev < python-dev@python.org> wrote: > > > Sent from my iPhone > ___ > Python-Dev mailing list -- python-dev@python.org > To unsu

[Python-Dev] Re: PEP 448 review

Wow, we are now getting Canadian-specific spam! Since the volume on this mailing list is so low, should we change everyone to be moderated to start and then remove that after they have posted appropriately? Or did this get through by accident? On Wed, Mar 29, 2023 at 12:19 PM wrote: > It seems

[Python-Dev] Re: Can someone please finish merging GH-13482?

Tim Peters wrote: > [Brett Cannon br...@python.org] > > We probably need to update https://devguide.python.org/committing/ > > to > > have a step-by-step list of how to make a merge works and how to > > handle backports instead of the wall of text that we have. (It&#x

[Python-Dev] Re: PEP 572 TargetScopeError

I agree that it should be a SyntaxError as it's a semantic issue regarded to syntax. For instance, we already use SyntaxError for when a `return` statement is outside of a function and I view this as the same sort of error. And I think with an appropriately descriptive message like Ivan pointed

[Python-Dev] Re: Missing license for file Modules/ossaudiodev.c

I've opened https://github.com/python/cpython/pull/15346 to remove the dead comment. ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python

[Python-Dev] Re: Announcing the new Python triage team on GitHub

Abhilash Raj wrote: > On Thu, Aug 22, 2019, at 6:06 AM, Victor Stinner wrote: > > Hi, > > Oh, I just wrote a similar email to python-committers, I didn't notice > > that Mariatta wrote to python-dev and python-committers. > > https://mail.python.org/archives/list/python-committ...@python.org/messa

[Python-Dev] Re: Python library maintainers: PEP 602 needs your feedback

At the Python core dev sprints we created a new "PEPs" category for PEP discussions to go and that's open to the public. ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.

[Python-Dev] Re: The Python 2 death march

Kyle Stanley wrote: > Benjamin, what are you thoughts on usage of the "needs backport to 2.7" > label? For most of the PRs I've reviewed I tend to avoid adding it myself, > but I've seen it used periodically. It seems to be used rather infrequently > ( > https://github.com/python/cpython/pulls?q=is

[Python-Dev] Re: The Python 2 death march

Chris Barker wrote: > On Tue, Sep 17, 2019 at 10:39 PM Terry Reedy tjre...@udel.edu wrote: > > I agree. The thread title is a bit extreme. There > > will be a long > > twilight. > > Metaphorically that is correct, but at > > the same time there are > > things like https://pythonclock.org

[Python-Dev] When writing a PEP, please use the template from PEP 12

https://www.python.org/dev/peps/pep-0012/#suggested-sections This applies even to folks who have written a PEP before as that template gets updated on occasion. For instance, there's a new copyright notice and the last couple proposed PEPs didn't catch it because they copy and pasted from old PEPs

[Python-Dev] Re: The Python 2 death march

Stefan Behnel wrote: > Ned Batchelder schrieb am 10.09.19 um 16:54: > > this seems confusing to me > > What does the "official EOL date" mean if there's a release in April? It means we should all consider Python 2.7 EOL'ed come January 1 and Benjamin will make a release when it's convenient, and

[Python-Dev] Re: static variables in CPython - duplicated _Py_IDENTIFIERs?

Vinay Sajip wrote: > > Right, I'm > > pretty sure that right now Python doesn't have any way to > > share symbols between .c files without also exposing them in the C > > API. > > On other C projects I've worked on, the public API is expressed in one set > of header files, and internal APIs that ne

[Python-Dev] Bug in Bedevere related to detecting edited titles that add in the bpo number post-open

https://github.com/python/bedevere/issues/192 It should get fixed sometime today or at worst tomorrow. Until then, if someone edits a title after creating a PR to add an issue number, just add the `skip issue` label and then remove it again and it will run the check.

[Python-Dev] Bug in Bedevere related to detecting edited titles that add in the bpo number post-open

https://github.com/python/bedevere/issues/192 It should get fixed sometime today or at worst tomorrow. Until then, if someone edits a title after creating a PR to add an issue number, just add the `skip issue` label and then remove it again and it will run the check.

[Python-Dev] Re: Adding GitHub usernames to the developer log

I'm personally fine listing GItHub usernames in the devguide's developer list, but I'm also not trying to be anonymous on GitHub. But I will say that listing our GitHub usernames with our real names is not required to tell who is a core developer. In GitHub's UI there are multiple places it wil

[Python-Dev] Re: The Python 2 death march

Steve Dower wrote: > On 25Sep2019 2140, Benjamin Peterson wrote: > > On Wed, Sep 25, 2019, at 17:25, Rob Cliffe via > > Python-Dev wrote: > > I > > additionally share the bemusement of some other commentators on this thread > > to the idea of > > Python 2 "support", which is not something ever pro

[Python-Dev] Re: PEP 587 (Python Initialization Configuration) updated to be future proof again

Victor Stinner wrote: > Hi Nick, > Le dim. 29 sept. 2019 à 08:47, Nick Coghlan ncogh...@gmail.com a écrit : > > I don't quite understand the purpose of this change, > > as there's no > > stable ABI for applications embedding CPython. > > Well, I would like to prepare Python to provide a stable ABI

[Python-Dev] The PSF's new Code of Conduct and how it applies to Python's development

[this is being emailed out to python-committer and python-dev separately, so apologies for those who get a duplicate email] The steering council wanted to let everyone know that the PSF released a new Code of Conduct which was announced at https://pyfound.blogspot.com/2019/09/the-python-software-

[Python-Dev] Re: Awareness creation of a new IDE

If you want to use a modified version of the logo you will need to clear it with the PSF trademark WG: https://www.python.org/psf/committees/#trademarks-work-group. ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to pyt

[Python-Dev] Re: Adding GitHub usernames to the developer log

Since Victor and I came out in support of listing everyone's GitHub usernames in the devguide and no one objected, I will assume people are okay with this idea. And so at some point I will update the code to generate the table for the devguide to include everyone's GitHub username. _

[Python-Dev] Accepting PEP 602 -- Annual Release Cycle for Python

On behalf of the steering council I am happy to announce that as BDFL-Delegate I am accepting PEP 602 to move us to an annual release schedule (gated on a planned update; see below). The steering council thinks that having a consistent schedule every year when we hit beta, RC, and final it will

[Python-Dev] Re: Accepting PEP 602 -- Annual Release Cycle for Python

This PEP was mentioned on python-dev at least at https://mail.python.org/archives/list/python-dev@python.org/message/WQ64ZGBECFDIRO6DS7JN3NALYDJGPAAE/ and https://mail.python.org/archives/list/python-dev@python.org/message/YVSOOFLCBHPIA3HBL4L2BFBJENVHZDJC/. This was also covered by the PEP 596

[Python-Dev] Re: Cleaning the stable ABI [was Accepting PEP 602 -- Annual Release Cycle for Python]

Steve Dower wrote: > On 30Oct2019 1226, Brett Cannon wrote: > > > > Now that the stable ABI has been cleaned, extension modules should feel more > > comfortable targeting the stable ABI which should make supporting newer > > versions of Python > > much easi

[Python-Dev] Re: Accepting PEP 602 -- Annual Release Cycle for Python

Barry Warsaw wrote: > On Oct 30, 2019, at 14:31, Łukasz Langa luk...@langa.pl > wrote: > > Yes. This allows for synchronizing the schedule of > > Python release management with Fedora. They've been historically very > > helpful in early > > finding regressions not only in core Python but also in t

[Python-Dev] Rejecting PEP 497

Thanks to Ed for writing the PEP, but the steering council decided to reject PEP 497. The website has not caught up to the rejection notice as I type this, but we rejected https://www.python.org/dev/peps/pep-0497/ due to the `__past__` concept being too much work for what would be gained (we seem t

[Python-Dev] Re: Compiling Python with SQLite when SQLite is in an arbitrary place

Lele Gaifax wrote: > "Coirier, Emmanuel" emmanuel.coir...@caissedesdepots.fr > writes: > > To sum up, when the SQLite binaries are not in a > > standard place, it seemed > > for me to be impossible to include sqlite into Python. In the end, I noticed > > I missed the CPPFLAGS env variable, that I t

[Python-Dev] Re: Exposing Tools/parser/unparse.py in the stdlib?

Victor Stinner wrote: > Le mar. 19 nov. 2019 à 22:12, Pablo Galindo Salgado > pablog...@gmail.com a écrit : > > Float infinity > > is replaced with 1e309. Again, maybe someone wants > > to render this differently? It sounds like an arbitrary choice (which > > "works" as expected). > > That is not t

[Python-Dev] Stalemate on bringing back PEP 523 support into Python 3.8

An unfortunate side-effect of making PyInterpreterState in Python 3.8 opaque is it removed [PEP 523](https://www.python.org/dev/peps/pep-0523/) support. https://www.python.org/dev/peps/pep-0523/ was opened to try and fix this, but there seems to be a stalemate in the issue. A key question is at

[Python-Dev] Re: Stalemate on bringing back PEP 523 support into Python 3.8

ver) if they want to > > use it. > > Accessor functions seem like overkill in that case since they would > > require the same Py_BUILD_CORE_MODULE that the PyInterpreterState > > field now requires. > > -eric > > On Thu, Nov 21, 2019 at 1:06 PM Brett Cannon br...@p

[Python-Dev] Re: Travis CI for backports not working.

I have turned Travis off as a required check on the 3.7, 3.8, and master branches until someone is able to get a fix in. ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.

[Python-Dev] Are we ready to start cleaning up deprecated stuff?

Python 3.9 is going to be the first release which will exist without any Python 2.7 overlap. Does this mean we are ready to start removing things that have been deprecated since at least Python 3.7? PEP 4 says [we are in the clear for modules](https://www.python.org/dev/peps/pep-0004/#for-module

[Python-Dev] Re: Are we ready to start cleaning up deprecated stuff?

Gregory P. Smith wrote: > On Tue, Nov 26, 2019 at 12:00 PM Brett Cannon br...@python.org wrote: > > Python 3.9 is going to be the first release which > > will exist without any > > Python 2.7 overlap. Does this mean we are ready to start removing things > > that have bee

[Python-Dev] Should we require all deprecations to have a removal version that we follow through on?

What do people think of the idea of requiring all deprecations specifying a version that the feature will be removed in (which under our annual release cadence would be at least the third release from the start of the deprecation, hence the deprecation being public for 2 years)? And that we also

[Python-Dev] Re: Are we ready to start cleaning up deprecated stuff?

Gregory P. Smith wrote: > On Wed, Nov 27, 2019 at 10:15 AM Brett Cannon br...@python.org wrote: > > Gregory P. Smith wrote: > > On Tue, Nov 26, 2019 at 12:00 PM Brett Cannon > > br...@python.org wrote: > > Python 3.9 is going to be the first release > > which >

[Python-Dev] Re: Should we require all deprecations to have a removal version that we follow through on?

Ethan Furman wrote: > On 11/27/2019 10:38 AM, Brett Cannon wrote: > > What do people think of the idea of requiring all > > deprecations specifying a version that the feature will be removed in > > (which under our > > annual release cadence would be at least the t

[Python-Dev] Re: Should we require all deprecations to have a removal version that we follow through on?

Nick Coghlan wrote: > On Thu., 28 Nov. 2019, 4:43 am Brett Cannon, br...@python.org wrote: > > What do people think of the idea of requiring all > > deprecations specifying > > a version that the feature will be removed in (which under our annual > > release cadence

[Python-Dev] Re: PEP proposal to limit various aspects of a Python program to one million.

Steven D'Aprano wrote: > I'm going to second Chris' comment about efficiency. The purposes of > this PEP (as I read it) are: > (1) Security (less chance of code intentionally or accidentally > exceeding low-level machine limits that allow a security exploit); > (2) Improved memory use; > (3) And

[Python-Dev] Re: Deprecating the "u" string literal prefix

Greg Ewing wrote: > On 4/12/19 8:41 am, Christian Heimes wrote: > > I'm strongly against removing it from Python 3 or > > even > > raising a deprecation warning. > > I agree. I know there is a maintenance cost to keeping > things like this around, but in this case it's pretty > minor. We've probabl

[Python-Dev] Re: Travis CI for backports not working.

Victor Stinner wrote: > Hello, > Le mar. 26 nov. 2019 à 20:40, Brett Cannon br...@python.org a écrit : > > I have turned Travis off as a required check on the > > 3.7, 3.8, and master branches until someone is able to get a fix in. > > That makes me sad :-( Is there an iss

[Python-Dev] Re: PEP 587

This mailing list is for discussing making _of_ Python, not _with_ it. You are better to ask this over on python-list. ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.or

[Python-Dev] Re: Should we require all deprecations to have a removal version that we follow through on?

Victor Stinner wrote: > Hi, > Le mer. 27 nov. 2019 à 19:40, Brett Cannon br...@python.org a écrit : > > What do people think of the idea of requiring all > > deprecations specifying a version that the feature will be removed in > > (which under our > > annual release

<    9   10   11   12   13   14   15   16   17   18   >