Re: [Python-Dev] PEP 581: Using GitHub Issues for CPython

> clearly we couldn’t continue running infra off of their systems. > > 10/2005 - we move to Subversion > > 9/2006 - we begin to discuss moving off of the SF bug tracker. I believe > that Thomas Wouters, Martin von Loewis, Brett Cannon (big surprise! :), and > myself were involved in

Re: [Python-Dev] Loading modules from a folder

This mailing list is actually for the development *of* Python, not *with* Python. You can try asking your question on Stack Overflow, python tutor, or python-list. On Thu, Mar 7, 2019 at 9:28 AM Mani Sarkar wrote: > Hi, > > I have seen multiple ways to load modules from a folder. > > Say I have

Re: [Python-Dev] PEPs from non-core devs now need a sponsor

to be explicitly rejected either. I personally am happy to sponsor such PEPs as I'm sure several other core devs are as well. On Mon, Mar 4, 2019 at 5:43 PM Brett Cannon wrote: > The steering council has implemented a new idea called sponsors to the PEP > process (added in > https://github.com/py

Re: [Python-Dev] PEPs from non-core devs now need a sponsor

On Tue, Mar 5, 2019 at 11:59 AM Jeroen Demeyer wrote: > On 2019-03-05 18:14, Steve Dower wrote: > > However, if you don't have > > *a single* core developer on board from python-ideas, chances are the > > whole team is going to reject the proposal. > > Sure, I couldn't agree more. But this is

Re: [Python-Dev] PEPs from non-core devs now need a sponsor

On Tue, Mar 5, 2019 at 3:36 AM Victor Stinner wrote: > Hi, > > Le mar. 5 mars 2019 à 02:53, Brett Cannon a écrit : > > The steering council has implemented a new idea called sponsors to the > PEP process (...). The thinking is that to help make sure PEPs from > non-co

Re: [Python-Dev] PEPs from non-core devs now need a sponsor

On Tue, Mar 5, 2019 at 5:33 AM Jeroen Demeyer wrote: > On 2019-03-05 14:05, Calvin Spealman wrote: > > I'm worried this creates a gatekeeping perception that will scare away > > contributors. > It might, but if people are not prepared properly for the PEP process then it's best to spare them

Re: [Python-Dev] PEPs from non-core devs now need a sponsor

On Mon, Mar 4, 2019 at 10:13 PM Jeroen Demeyer wrote: > Does this apply to existing draft PEPs or only new ones? > Only new ones; this is not retroactive. -Brett > ___ > Python-Dev mailing list > Python-Dev@python.org >

[Python-Dev] PEPs from non-core devs now need a sponsor

The steering council has implemented a new idea called sponsors to the PEP process (added in https://github.com/python/peps/commit/c58d32c33bd06eb386d3f33963a1434510528f68). The thinking is that to help make sure PEPs from non-core developers receive appropriate guidance through the PEP process, a

Re: [Python-Dev] Addendum to PEP 530

Open an issue at https://github.com/python/steering-council/issues if you want the steering council to consider something. On Mon, Mar 4, 2019 at 9:38 AM Serhiy Storchaka wrote: > PEP 530 introduced support for asynchronous comprehensions. > > Comprehensions are implemented as local functions.

Re: [Python-Dev] Can I get a review for PR 10437?

While more reviewers never hurt, Victor has left at least one comment on the PR. On Thu, Feb 28, 2019 at 7:59 AM Kevin Adler wrote: > This PR has been open for nearly 3 months without any comment. Can I > please get someone to review it? > > PR link: https://github.com/python/cpython/pull/10437

Re: [Python-Dev] Making PyInterpreterState an opaque type

On Thu, Feb 21, 2019 at 6:01 AM Armin Rigo wrote: > Hi, > > On Tue, 19 Feb 2019 at 13:12, Victor Stinner wrote: > > Please don't use _GET_ITEM() or _PyTuple_ITEMS(). It prevents > > to use a more efficient storage for tuple. Something like: > > >

Re: [Python-Dev] Making PyInterpreterState an opaque type

On Tue, Feb 19, 2019 at 12:45 PM Steve Dower wrote: > On 19Feb2019 1141, Barry Warsaw wrote: > > Steve Dower wrote on 2/16/19 14:34:> > >> This is mostly about being able to assign blame when things break, so > >> I'm totally okay with extension modules that want to play with internals > >>

Re: [Python-Dev] new binary wheels PEP idea

Unfortunately you're still posted to the wrong list, Alexander. You want to mail distutils-...@python.org where packaging discussions occur. On Tue, Feb 19, 2019 at 8:19 AM Alexander Revin wrote: > Hi all, > > I have an idea regarding Python binary wheels on non-glibc platforms, > and it seems

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

On Thu, Feb 14, 2019 at 10:21 AM Gustavo Carneiro wrote: > > > On Thu, 14 Feb 2019 at 15:52, Victor Stinner wrote: > >> Le jeu. 14 févr. 2019 à 14:38, Matthias Klose a écrit : >> > Debian's concern about pointing python to python3 is that it will break >> software >> > after an upgrade. The

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

On Thu, Feb 14, 2019 at 7:50 AM Victor Stinner wrote: > Le jeu. 14 févr. 2019 à 14:38, Matthias Klose a écrit : > > Debian's concern about pointing python to python3 is that it will break > software > > after an upgrade. The current state seems is still the same that Debian > doesn't > > want

Re: [Python-Dev] Adding test.support.safe_rmpath()

On Thu, Feb 14, 2019 at 7:26 AM Giampaolo Rodola' wrote: > > > On Thu, Feb 14, 2019 at 4:03 PM Tim Golden wrote: > >> On 14/02/2019 14:56, Giampaolo Rodola' wrote: >> > >> > >> > On Thu, Feb 14, 2019 at 3:25 PM Eric Snow > > > wrote: >> > >> > On Thu, Feb

Re: [Python-Dev] Return type of datetime subclasses added to timedelta

On Sun, 6 Jan 2019 at 11:00, Paul Ganssle wrote: > I did address this in the original post - the assumption that the subclass > constructor will have the same arguments as the base constructor is baked > into many alternate constructors of datetime. I acknowledge that this is a > breaking

Re: [Python-Dev] Compilation of "except FooExc as var" adds useless store

On Sun, 6 Jan 2019 at 10:26, Guido van Rossum wrote: > On Sun, Jan 6, 2019 at 9:40 AM Paul G wrote: > >> I am not familiar enough with the compiler logic, but would it be >> possible to optimize this away by detecting whether the bound name has >> already been deleted during the body of the

Re: [Python-Dev] [PyPI] Email verification

I've reported this to infrastructure@. On Wed., Dec. 5, 2018, 12:05 PyPI Someone, perhaps you, has added this email address (Python-dev@python.org) > to their PyPI account. > > If you wish to proceed with this request, click this link to verify your > email address >

Re: [Python-Dev] getting merge rights back on github

This is being dealt with. On Sun, 2 Dec 2018 at 08:28, Chris Withers wrote: > Hi All, > > It's been quite a long time since I last used my python commit rights, > and it appears they've evaporated in the move to GitHub. > > I'd like to get back into helping out, particularly with unittest.mock

Re: [Python-Dev] Inclusion of lz4 bindings in stdlib?

On Thu, 29 Nov 2018 at 14:12, Andrew Svetlov wrote: > Neither http.client nor http.server doesn't support compression > (gzip/compress/deflate) at all. > I doubt if we want to add this feature: for client better to use requests > or, well, aiohttp. > The same for servers: almost any production

Re: [Python-Dev] Inclusion of lz4 bindings in stdlib?

On Wed, 28 Nov 2018 at 13:29, Steven D'Aprano wrote: > On Wed, Nov 28, 2018 at 10:43:04AM -0800, Gregory P. Smith wrote: > > > PyPI makes getting more algorithms easy. > > Can we please stop over-generalising like this? PyPI makes getting > more algorithms easy for *SOME* people. (Sorry for

Re: [Python-Dev] Inclusion of lz4 bindings in stdlib?

Are we getting to the point that we want a compresslib like hashlib if we are going to be adding more compression algorithms? On Wed, 28 Nov 2018 at 08:44, Antoine Pitrou wrote: > On Wed, 28 Nov 2018 10:28:19 + > Jonathan Underwood wrote: > > Hi, > > > > I have for sometime maintained the

Re: [Python-Dev] bpo-34532 status

To provide context, https://bugs.python.org/issue34532 is about making the Python launcher on Windows not return an error condition when using `py -0` (and probably `py --list` and `py --list-paths`). On Tue, 20 Nov 2018 at 08:29, Brendan Gerrity wrote: > Just wanted to check on

Re: [Python-Dev] Experiment an opt-in new C API for Python? (leave current API unchanged)

On Mon., Nov. 19, 2018, 14:04 Neil Schemenauer On 2018-11-19, Antoine Pitrou wrote: > > There are important use cases for the C API where it is desired to have > > fast type-specific access to Python objects such as tuples, ints, > > strings, etc. This is relied upon by modules such as _json and

Re: [Python-Dev] Experiment an opt-in new C API for Python? (leave current API unchanged)

On Fri, 16 Nov 2018 at 10:11, Paul Moore wrote: > On Fri, 16 Nov 2018 at 17:49, Brett Cannon wrote: > > And Just to be clear, I totally support coming up with a totally > stripped-down C API as I have outlined above as that shouldn't be > controversial for any VM that wants to

Re: [Python-Dev] Experiment an opt-in new C API for Python? (leave current API unchanged)

On Wed, 14 Nov 2018 at 16:09, Gregory P. Smith wrote: > It seems like the discussion so far is: >> >> Victor: "I know people when people hear 'new API' they get scared and >> think we're going to do a Python-3-like breaking transition, but don't >> worry, we're never going to do that." >>

Re: [Python-Dev] Get a running instance of the doc for a PR.

On Sun, 4 Nov 2018 at 14:49, Steven D'Aprano wrote: > On Sun, Nov 04, 2018 at 05:05:07PM +0100, Stephane Wirtel wrote: > > > >If I am making doc patches, shouldn't I be doing that *before* I > > >submit the PR? How else will I know that my changes haven't broken the > > >docs? > > > > You can

Re: [Python-Dev] PEP 543-conform TLS library

In case you never received a reply, you can try emailing Christian and Cory directly for an answer. On Fri, 26 Oct 2018 at 13:20, Mathias Laurin wrote: > Hello Python Dev, > > > I posted the following to python-ideas but here may be > a more suitable place. I apologize if cross posting >

Re: [Python-Dev] Python Language Governance Proposals

On Tue, 23 Oct 2018 at 13:20, Jeroen Demeyer wrote: > What is the timeframe for the installation of the new governance? In > other words, when will it be possible to review PEPs? > PEP 8001 outlines the voting for the governance models which includes a planned schedule for that vote. After that

Re: [Python-Dev] Some PRs to merge?

Of those 49 PRs, 18 are by core developers themselves, so 31 PRs are by external contributors that seem ready to be merged. There was a discussion at one point on core-workflow about changing the default "needs" label for PRs by core devs which in this instance would help with providing a search

Re: [Python-Dev] Should assert continue to do a LOAD_GLOBAL on AssertionError?

On Wed, 3 Oct 2018 at 19:39, Benjamin Peterson wrote: > > > On Wed, Oct 3, 2018, at 08:59, Steven D'Aprano wrote: > > On the bug tracker, there's a discussion about the current behaviour of > > the assert statement, where shadowing AssertionError will change the > > behaviour of the assertion. >

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

I'm also fine with saying that keys in **kwargs that are not proper identifiers is an implementation detail. On Thu, 4 Oct 2018 at 02:20, Serhiy Storchaka wrote: > 04.10.18 11:56, Steven D'Aprano пише: > > While keyword arguments have to be identifiers, using **kwargs allows > > arbitrary

Re: [Python-Dev] PEP 544 status (forked off "Petr Viktorin as BDFL-Delegate for PEP 580")

I think whatever governance we end up with would have named you BDFL-delegate anyway, Guido, so I think you're just taking the time machine for a spin again. ;) On Wed, 3 Oct 2018 at 09:40, Guido van Rossum wrote: > The process for PEP 544 is off-topic for that thread so I'm starting a new >

Re: [Python-Dev] Communication channels

lopers are also active on Twitter. Some ideas were first > > discussed on Twitter. You may want to follow some of them. Incomplete > > list of core devs that I follow: > > > > * Barry Warsaw: https://twitter.com/pumpichank > > * Brett Cannon: https://twitter.com/brettsky

Re: [Python-Dev] Official citation for Python

On Sun, 16 Sep 2018 at 15:23 Jacqueline Kazil wrote: > RE: Why cite Python…. > > I would say that in this paper — > http://conference.scipy.org/proceedings/scipy2015/pdfs/jacqueline_kazil.pdf, > where we introduced a new library, we should have cited Python, because the > library was based in

Re: [Python-Dev] Official citation for Python

On Sun, 9 Sep 2018 at 20:55 Terry Reedy wrote: > On 9/9/2018 11:39 PM, Jacqueline Kazil wrote: > > Terry -- For clarification, the format question was not a style > > question. It was a reference to the one versus many that I wrote in the > > explainer. > > I don't know what you mean by this. >

Re: [Python-Dev] Workflow blocked on the 3.6 because of AppVeyor; who owns the AppVeyor project?

On Wed, 5 Sep 2018 at 04:56 Paul Moore wrote: > On Wed, 5 Sep 2018 at 12:24, Antoine Pitrou wrote: > > For some reason it seems to be located in a hidden directory > > (".github/appveyor.yml"). Not the most intuitive decision IMHO. > > Travis' own config file ".travis.yml" is still at

Re: [Python-Dev] New Subscriber

ent from my iPhone > > On Sep 1, 2018, at 1:48 PM, Brett Cannon wrote: > > Hi, Kevin! This mailing list is actually about the development *of* > Python, not *with* it. To have a discussion about GUI programming with > Python is probably python-list is a better place to discuss t

Re: [Python-Dev] New Subscriber

Hi, Kevin! This mailing list is actually about the development *of* Python, not *with* it. To have a discussion about GUI programming with Python is probably python-list is a better place to discuss this. On Sat, 1 Sep 2018 at 10:37 Kevin Kowitski via Python-Dev < python-dev@python.org> wrote: >

Re: [Python-Dev] Starting to use gcc-8 on upstream Python project CI

So is the request simply to use gcc 8 instead of what Travis uses as the default gcc? IOW change https://github.com/python/cpython/blob/28853a249b1d0c890b7e9ca345290bb8c1756446/.travis.yml#L71 somehow to use gcc8 specifically? Since it's only used for the code coverage build I don't think anyone

Re: [Python-Dev] unsolicited removal request

Chances are, Andrew click the unsubscribe link from an email reply that Abdur-Rahmaan made (this happens to me semi-regularly). On Mon, 20 Aug 2018 at 09:34 Abdur-Rahmaan Janhangeer wrote: > no idea, a mail popped up in my inbox ... > > > Abdur-Rahmaan Janhangeer >

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

This mailing list is for the discussion of the development *of* Python, not its use. Your best bet for help is either a site like Stack Overflow or another mailing list like python-tutor or python-list. On Thu, 9 Aug 2018 at 08:30 Poornima .D. wrote: > Hi All, > > > I have limited knowledge on

[Python-Dev] Using Cython for the stdlib (was: Let's change to C API!)

[new thread as this no longer has anything to do with Victor's proposal] On Tue, 31 Jul 2018 at 13:42 Stefan Behnel wrote: > Antoine Pitrou schrieb am 31.07.2018 um 09:45: > > On Tue, 31 Jul 2018 09:27:03 +0200 > > Jeroen Demeyer wrote: > >> On 2018-07-31 08:58, Antoine Pitrou wrote: > >>> I

Re: [Python-Dev] New _Py_InitializeFromConfig() function (PEP 432)

On Tue, 31 Jul 2018 at 15:16 Victor Stinner wrote: > Hi, > > I finished my work on the _PyCoreConfig structure: it's a C structure > in Include/pystate.h which has many fields used to configure Python > initialization. In Python 3.6 and older, these parameters were scatted > around the code, and

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

On Wed, 1 Aug 2018 at 07:47 Terry Reedy wrote: > 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

Re: [Python-Dev] test_zlib.py suggestion

Open an issue as this will surely get forgotten otherwise, then people can discuss on the issue how to handle this. On Wed, 1 Aug 2018 at 08:40 Michael wrote: > I have a build_bot running (yeah me!), and was surprised to see > test_zlib fail on AIX. > > There is not an issue with test_zlib, but

Re: [Python-Dev] Let's change to C API!

On Tue, 31 Jul 2018 at 10:32 Antoine Pitrou wrote: > > Well, I tried to subscribe to capi-sig, but I didn't get a > confirmation e-mail. > I subscribed yesterday without issue. I would email postmaster to try and find out what happened. -Brett > > Regards > > Antoine. > > > On Tue, 31 Jul

Re: [Python-Dev] Testing C API

On Sun, Jul 29, 2018, 06:44 Serhiy Storchaka, wrote: > 29.07.18 15:39, Steve Dower пише: > > On 29Jul2018 1253, Serhiy Storchaka wrote: > >> The benefit is that it will be easier to run all C API tests at once, > >> and only them, and it will be clearer what C API is covered by tests. > >> The

Re: [Python-Dev] Tests failing on Windows with TESTFN

On Sat, Jul 28, 2018, 15:13 eryk sun, wrote: > On Sat, Jul 28, 2018 at 9:17 PM, Jeremy Kloth > wrote: > > > > *PLEASE*, don't use tempfile to create files/directories in tests. It > > is unfriendly to (Windows) buildbots. The current approach of > > directory-per-process ensures no test turds

Re: [Python-Dev] Tests failing on Windows with TESTFN

On Wed, 25 Jul 2018 at 15:16 Tim Golden wrote: > I'm just easing back into core development work by trying to get a > stable testing environment for Python development on Windows. > > One problem is that certain tests use support.TESTFN (a local directory > constructed from the pid) for output

Re: [Python-Dev] Fuzzing the Python standard library

On Tue, 17 Jul 2018 at 15:41 Nathaniel Smith wrote: > On Tue, Jul 17, 2018 at 9:44 AM, Jussi Judin wrote: > > * Exceptions that are something else than the documented ones. These > usually indicate an internal implementation issue. For example one would > not expect an UnicodeDecodeError from

Re: [Python-Dev] Question about PEP 484

On Mon, 16 Jul 2018 at 10:32 Adam Cataldo via Python-Dev < python-dev@python.org> wrote: > > > > > > *Hi Folks,Cc: Rebecca, pytypeThis is Adam Cataldo; I’m the engineering > manager for the Python team at Google. Rebecca Chen, our lead pytype > contributor, and

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

On Mon, 9 Jul 2018 at 12:05 Guido van Rossum wrote: > I think this is worth a try. > How far do we want to go with this? Update the docs? Update the grammar and/or code? I think the former is probably good enough for now to see if it takes, and if it does then we can talk about updating code to

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

On Sun, Jul 8, 2018, 18:30 Eric V. Smith, wrote: > On 7/8/2018 8:35 PM, Terry Reedy wrote: > > 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

Re: [Python-Dev] PEP 575, 576, 579 and 580

On Sat, Jul 7, 2018, 08:17 INADA Naoki, wrote: > > IMO, mailing lists are a terrible way to do software design, but a good > > way to gather requirements as it makes less likely that someone will be > > forgotten. > > > > Agreed. There are several topics we should discuss for these PEPs. >

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

On Fri, Jul 6, 2018, 16:32 Guido van Rossum, wrote: > On Fri, Jul 6, 2018 at 4:19 PM Terry Reedy 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 shot it down. The term is

Re: [Python-Dev] Tone it down on Twitter?

On Wed, 4 Jul 2018 at 11:54 Mark Lawrence wrote: > On 04/07/18 16:48, Stefan Krah wrote: > > > > Apparently I have made it into "club of three who don't care much about > > opinions of others" for the crime of a single +0.5 for PEP-572 without > > participating in the discussion at all (neither

Re: [Python-Dev] Tone it down on Twitter?

While I agree with Antoine that the wording by Serhiy on Twitter was unnecessary, the tone in responses here are also unnecessary. As has been discussed both here on this mailing list and at the PyCon US language summit, reacting to actual or perceived rudeness with more rudeness is not reasonable

Re: [Python-Dev] PEP 484

On Wed, 4 Jul 2018 at 22:07 Greg Ewing wrote: > Shawn Chen wrote: > > The PEP 484 is proposing a type hint which can annotate the type of each > > parameters. How ever code written in this format can not be run for > > python3.5 and below. > > You're a bit late. Parameter annotations have been a

Re: [Python-Dev] Removal of install_misc command from distutils

For referencing, the commit was https://github.com/python/cpython/commit/ef158c3ced3fce39e43f54e8d149dc2714e3456e#diff-ef2e84716aa6196aa0ebf0691e608986 and the issue was https://bugs.python.org/issue29218 . On Thu, 5 Jul 2018 at 11:27 Alexander Belopolsky < alexander.belopol...@gmail.com> wrote:

Re: [Python-Dev] Examples for PEP 572

On Wed, 4 Jul 2018 at 07:42 Antoine Pitrou wrote: > On Wed, 4 Jul 2018 09:43:04 -0300 > Brett Cannon wrote: > > > > I think this is a very key point that the "this is bad" crowd is > > overlooking. Even if this syntax turns out to not be that useful, abusing &g

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

On Fri, 6 Jul 2018 at 08:52 Chris Barker - NOAA Federal via Python-Dev < python-dev@python.org> wrote: > Are we just having fun here? > > Or might we actually start using a new naming convention for > the-syntax-formerly-known-as-generator-expressions? > If you can create a groundswell of

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

On Fri, 6 Jul 2018 at 11:02 Serhiy Storchaka wrote: > 04.07.18 15:05, Nick Coghlan пише: > > So my guess would be that this is a test suite error where we're not > > handling the "running in a reproducible build environment with > > SOURCE_DATE_EPOCH already set" case. > > Should

Re: [Python-Dev] Examples for PEP 572

On Tue, Jul 3, 2018, 22:27 Tim Peters, wrote: > [INADA Naoki] > > ... > > On the other hand, I understand PEP 572 allows clever code > > simplifies tedious code. It may increase readability of non-dirty > code. > > The latter is the entire intent ,of course. We can't force people to > write

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

On Thu, Jun 28, 2018, 21:28 Terry Reedy, wrote: > 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-Dev] We now have C code coverage!

Thanks to a PR from Ammar Askar we now run Python under lcov as part of the code coverage build. And thanks to codecov.io automatically merging code coverage reports we get a complete report of our coverage (the first results of which can now be seen at https://codecov.io/gh/python/cpython). And

Re: [Python-Dev] PySequence_Check but no __len__

Sorry, I don't quite follow. On Thu, 21 Jun 2018 at 08:50 Christian Tismer wrote: > Hi friends, > > there is a case in the Python API where I am not sure what to do: > > If an object defines __getitem__() only but no __len__(), > then PySequence_Check() already is true and does not care. >

Re: [Python-Dev] Can we make METH_FASTCALL public, from Python 3.7? (ref: PEP 579

On Wed, 20 Jun 2018 at 09:49 INADA Naoki wrote: > > 2018年6月21日(木) 1:17 Antoine Pitrou : > >> On Wed, 20 Jun 2018 18:09:00 +0200 >> Victor Stinner wrote: >> > >> > > If we can't at Python 3.7, I think we should do it at 3.8. >> > >> > What's the rationale to make it public in 3.7? Can't it wait

Re: [Python-Dev] Microsoft to acquire GitHub for $7.5 billion

On Wed, 6 Jun 2018 at 02:09 Matěj Cepl wrote: > On 2018-06-05, 15:03 GMT, Nick Coghlan wrote: > > I was actually looking into this recently to see if the > > repository import feature could be used to run a regularly > > updated repository mirror that included all issues and PR > > comments in

Re: [Python-Dev] Keeping an eye on Travis CI, AppVeyor and buildbots: revert on regression

On Wed, 6 Jun 2018 at 09:27 INADA Naoki wrote: > First I was also >> confused between travis-ci.com and travis-ci.org ... The documentation >> shows an example with .com, but Python organization uses .org. >> >> Victor >> > > .org is legacy. > > Open source projects can migrate to new .com. >

Re: [Python-Dev] Stable ABI

I know Kushal set up ABI testing for Fedora and has brought up taking the work he did for that and bringing it over to CPython, but I also know he is offline for personal reasons ATM and won't be able to to reply for a little while. On Mon, 4 Jun 2018 at 08:06 Eric Snow wrote: > I've pointed

Re: [Python-Dev] Forward of moderated message

If you look you will see this is being executed from within Kodi, so this is probably an embedding situation where Kodi has a bug and they are triggering a crash in the interpreter. On Wed, 30 May 2018 at 09:22 wrote: > > > > -- Forwarded message -- > From: "Oscar Ortiz Garcia

Re: [Python-Dev] Troubles to merge changes in the 2.7 branch: PR "out-of-date" branch

Ryan is right that there's no special setting in GitHub at least which would make merging more strict for certain branches as you're describing. On Mon, 28 May 2018 at 07:06 Ryan Gonzalez wrote: > AFAIK there's no setting like this available, and I've done this many > times >

Re: [Python-Dev] [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

On Thu, 17 May 2018 at 14:31 Serhiy Storchaka wrote: > 15.05.18 14:51, Ned Deily пише: > > This is it! We are down to THE FINAL WEEK for 3.7.0! Please get your > > feature fixes, bug fixes, and documentation updates in before > > 2018-05-21 ~23:59 Anywhere on Earth

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

On Thu, 17 May 2018 at 09:57 Paul Moore <p.f.mo...@gmail.com> wrote: > On 17 May 2018 at 14:42, Brett Cannon <br...@python.org> wrote: > > > > If I understand things correctly, our planned migration to VSTS will > include > > eventually automating the signing

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

On Thu, 17 May 2018 at 04:25 Paul Moore wrote: > On 17 May 2018 at 04:46, Alex Walters wrote: > >> 1. Producing binaries (to the quality we normally deliver - I'm not > >> talking about auto-built binaries produced from a CI system) is a > >> chunk

Re: [Python-Dev] Slow down...

On Tue, 8 May 2018 at 08:26 Craig Rodrigues wrote: > On Mon, May 7, 2018 at 2:24 PM Barry Warsaw wrote: > >> On May 7, 2018, at 11:49, Craig Rodrigues wrote: >> > >> > Would it be reasonable to request a 10 year moratorium on

Re: [Python-Dev] Slow down...

On Mon, 7 May 2018 at 09:55 Ivan Levkivskyi <levkivs...@gmail.com> wrote: > On 7 May 2018 at 17:32, Brett Cannon <br...@python.org> wrote: > >> On Mon, 7 May 2018 at 08:18 João Santos <j...@jsantos.eu> wrote: >> >>> Hi, >>> >>>

Re: [Python-Dev] Slow down...

On Mon, 7 May 2018 at 08:18 João Santos wrote: > Hi, > > I would like to see this go even further and have a tick-tock approach to > python versions, i.e. adopt new syntax and other large changes on one > version (for example odd versions) and polish everything up in the next >

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

On Sat, 5 May 2018 at 10:41 Eric Fahlgren wrote: > On Sat, May 5, 2018 at 10:30 AM, Toshio Kuratomi > wrote: > >> On Fri, May 4, 2018, 7:00 PM Nathaniel Smith wrote: >> >>> What are the obstacles to including "preloaded" objects in

Re: [Python-Dev] Dealing with tone in an email (was: Drop/deprecate Tkinter?)

think it's especially true in our responses as we should try to keep the moral high ground by being examples of what we expect and want from others. > > On Fri, May 4, 2018 at 8:43 AM, Steven D'Aprano <st...@pearwood.info> > wrote: > >> On Thu, May 03, 2018 at 06:31:03PM

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

On Fri, 4 May 2018 at 12:09 Matthias Bussonnier < bussonniermatth...@gmail.com> wrote: > On Fri, 4 May 2018 at 11:49, Serhiy Storchaka wrote: > >> 04.05.18 20:57, Matthias Bussonnier пише: >> > But when I hit a DeprecationWarning message there is one crucial piece >> of >> >

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

ports; IOW I would say Ivan was lucky this time and may not be so lucky next time). -Brett > > On Thu, May 3, 2018, 11:57 Brian Curtin <br...@python.org> wrote: > >> On Thu, May 3, 2018 at 2:45 PM Ivan Pozdeev via Python-Dev < >> python-dev@python.org> wrote: &

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

On Thu, 3 May 2018 at 12:01 Facundo Batista <facundobati...@gmail.com> wrote: > 2018-05-02 14:24 GMT-03:00 Brett Cannon <br...@python.org>: > > >> Maybe we should create a tool to list features scheduled for removal, > >> and open a discussion to check each rem

[Python-Dev] Dealing with tone in an email (was: Drop/deprecate Tkinter?)

On Thu, 3 May 2018 at 01:27 Paul Moore wrote: > On 3 May 2018 at 03:26, Steven D'Aprano wrote: > > >> Will all due respect, it's sometimes unpredictable what kind of wording > >> Anglo-Saxons will take as an insult, as there's lot of obsequiosity > >>

Re: [Python-Dev] Python startup time

On Thu, 3 May 2018 at 07:31 Nick Coghlan wrote: > On 3 May 2018 at 15:56, Glenn Linderman wrote: > >> On 5/2/2018 8:56 PM, Gregory Szorc wrote: >> >> Nobody in the project is seriously talking about a complete rewrite in >> Rust. Contributors to the

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

On Wed, 2 May 2018 at 02:12 Victor Stinner wrote: > Hi, > > As a follow-up to the "[Python-Dev] (Looking for) A Retrospective on > the Move to Python 3" thread, I will like to clarify how a feature > should be removed from Python. > > We have multiple tools: > > * Emit a

Re: [Python-Dev] (Looking for) A Retrospective on the Move to Python 3

On Thu, 26 Apr 2018 at 10:19 Barry Warsaw wrote: > On Apr 26, 2018, at 09:28, Eric Snow wrote: > > > > On Thu, Apr 26, 2018 at 10:25 AM, Eric Snow > wrote: > >> In pondering our approach to future Python major

Re: [Python-Dev] The new and improved PEP 572, same great taste with 75% less complexity!

With the new name restriction on the LHS, I'm now -0 on this. While I don't think the benefits outweigh the overhead cost of pushing Python closer to not fitting in my brain, I would admittedly use this if provided to me. (I also put this in the bucket of consenting adult features; ripe for abuse,

Re: [Python-Dev] Introducing python.zulipchat.com

The Zulip project maintainers are active on our instance so after you join go to the Zulip stream and start a topic about this. On Sat, Apr 21, 2018, 02:16 Paul Moore, wrote: > OK, got there now. Thanks for the help. That's a lousy sign-up > experience, though... > Paul > >

[Python-Dev] Introducing python.zulipchat.com

As an experiment we have gotten an instance of Zulip running for Python's development at https://python.zulipchat.com (IOW this is for discussing the development *of* Python only*)*. As Guido has put it you can view Zulip like "hyper-interactive email" as we have streams corresponding to

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

On Tue, 17 Apr 2018 at 14:53 Eric Snow wrote: > On Tue, Apr 17, 2018 at 7:55 AM, Steve Dower > wrote: > > Agree with Paul. The PEP is well thought out and well presented, but I > > really don’t think we need this in Python (and I say this as

Re: [Python-Dev] Possible undefined behavior on creating a method named "__dict__"

On Wed, 11 Apr 2018 at 05:09 Steven D'Aprano wrote: > On Wed, Apr 11, 2018 at 08:21:01AM -0300, Joao S. O. Bueno wrote: > > I just came across a code snippet that > > would define a method with the "__dict__" name - like in: > > > > class A: > > def __dict__(self): > >

Re: [Python-Dev] Soliciting comments on the future of the cmd module (bpo-33233)

On Sat, 7 Apr 2018 at 11:50 Chris Barker - NOAA Federal < chris.bar...@noaa.gov> wrote: > Is bringing cmd2 into the standard library an option to be considered? > Anything can be considered. ;) > > That water get included batteries and a more featurefull and supported lib. > > It seems (on

Re: [Python-Dev] Soliciting comments on the future of the cmdmodule (bpo-33233)

On Sat, 7 Apr 2018 at 02:09 Steven D'Aprano wrote: > On Sat, Apr 07, 2018 at 09:30:05AM +0100, Paul Moore wrote: > > On 7 April 2018 at 04:13, Steve Dower wrote: > > > Better to deprecate it before it becomes broken, in my opinion. > > That argument

Re: [Python-Dev] Error embedding python

Most likely your 'args' module is calling import with a bytes object and not a string and that it's getting that far into the process before you hit code that only works with strings (_os.listdir() returns bytes if you pass a bytes argument to it). At this point I would take the question to

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

On Thu, 5 Apr 2018 at 02:49 Skip Montanaro wrote: > > There are a bunch of open issues regarding gdb support including one > with a PR in need of review for 3.6+. > > I rejected one (which assumed everyone now uses a python-aware gdb), > commented on another

Re: [Python-Dev] ssl module and LibreSSL CVE-2018-8970

Nice work! Something to add to our "finding C compiler bugs" list of accomplishments.  On Wed, Apr 4, 2018, 13:39 Christian Heimes, wrote: > Hi, > > I like to share the story of a critical security bug with you. Contrary > to other issues in TLS/SSL, it's a story with

Re: [Python-Dev] Enum, Flag, __contains__, and False vs TypeError

On Wed, 4 Apr 2018 at 11:30 Ethan Furman wrote: > API question. > > Background: > -- > > When doing checks such as > > --> 3 in [4, 5, 6] > --> 'test' in {'test':True, 'live':False} > > the result is True or False. > > When doing checks such as > > --> 3 in 'hello

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