[Python-Dev] On the necessity of PEPs [was "collections.sortedtree"]

On Wed, Mar 26, 2014, at 14:25, Barry Warsaw wrote: > On Mar 26, 2014, at 01:55 PM, Benjamin Peterson wrote: > > >It's not a bad idea. (I believe others have proposed an red-black tree.) > >Certainly, it requires a PEP and a few months of bikesheding, though. >

Re: [Python-Dev] Jython site now seems to redirect to docs.python.org???

On Fri, Mar 28, 2014, at 3:28, Paul Moore wrote: > I'm not sure if this is a result of the recent website reorg, but > www.jython.org seems to be redirecting to docs.python.org for me. > Presumably this is an error - where do I report it and/or is it a > known issue? This was my fault, though mayb

Re: [Python-Dev] libpython added to ABI tracker

On Tue, Apr 1, 2014, at 4:45, Nick Coghlan wrote: > Georg, Larry, Benjamin - should checking these be added to PEP 101, so > we don't get the same thing happening for 3.5? I would like it if we could put this in the testsuite somehow. ___

Re: [Python-Dev] libpython added to ABI tracker

On Tue, Apr 1, 2014, at 13:59, Nick Coghlan wrote: > On 2 Apr 2014 00:54, "Benjamin Peterson" wrote: > > > > On Tue, Apr 1, 2014, at 4:45, Nick Coghlan wrote: > > > Georg, Larry, Benjamin - should checking these be added to PEP 101, so > > > we

Re: [Python-Dev] [Python-checkins] cpython (3.3): minor docfix (reported at d...@python.org) trace.py argument is --count not

On Sun, Apr 6, 2014, at 11:01, senthil.kumaran wrote: > http://hg.python.org/cpython/rev/b49d990aaa9d > changeset: 90160:b49d990aaa9d > branch: 3.3 > parent: 90130:63e6afd3ff1f > user:Senthil Kumaran > date:Sun Apr 06 10:59:47 2014 -0700 > summary: > minor docfix (rep

Re: [Python-Dev] PEP 465: A dedicated infix operator for matrix multiplication

On Sun, Apr 6, 2014, at 18:41, Nathaniel Smith wrote: > Hi all, > > I've just finished updating PEP 465 with resolutions to the various > issues that were raised during the python-ideas thread about it. (The > main changes since that thread are that @@ has been removed, and we > now definitely pro

Re: [Python-Dev] PEP 465: A dedicated infix operator for matrix multiplication

On Mon, Apr 7, 2014, at 9:52, Alexander Belopolsky wrote: > On Sun, Apr 6, 2014 at 11:13 PM, Benjamin Peterson > wrote: > > > > I believe this leaves only one open question, which is where exactly > > > to stick the new matmul slots into PyTypeObject. This is the

Re: [Python-Dev] PEP 465: A dedicated infix operator for matrix multiplication

On Mon, Apr 7, 2014, at 14:22, Alexander Belopolsky wrote: > On Mon, Apr 7, 2014 at 1:11 PM, Benjamin Peterson > wrote: > > > > > We can populate that struct with array-specific alternatives for > > > PySequence/PyMappingMethods and eliminate the need for dynamic

Re: [Python-Dev] PEP 465: A dedicated infix operator for matrix multiplication

On Mon, Apr 7, 2014, at 14:33, Alexander Belopolsky wrote: > On Mon, Apr 7, 2014 at 5:23 PM, Benjamin Peterson > wrote: > > > I can understand why creating new array types is good fun, but how is > > creating a new struct helpful? > > > > We can start by

Re: [Python-Dev] PEP 465: A dedicated infix operator for matrix multiplication

On Mon, Apr 7, 2014, at 14:58, Barry Warsaw wrote: > On Apr 07, 2014, at 05:47 PM, Alexander Belopolsky wrote: > > >Python used to have an alias <> for != and I for one miss <> in 3.x. I > >don't think TOOWTDI should be the last word in this debate. > > PEP 401 to the rescue: It occurs to me th

Re: [Python-Dev] PEP 465: A dedicated infix operator for matrix multiplication

On Mon, Apr 7, 2014, at 18:04, Steven D'Aprano wrote: > On Mon, Apr 07, 2014 at 03:04:18PM -0700, Benjamin Peterson wrote: > > On Mon, Apr 7, 2014, at 14:58, Barry Warsaw wrote: > > > On Apr 07, 2014, at 05:47 PM, Alexander Belopolsky wrote: > > > > > > &g

[Python-Dev] stupid jokes (was PEP 465: A dedicated infix operator for matrix multiplication)

On Mon, Apr 7, 2014, at 18:11, Barry Warsaw wrote: > On Apr 07, 2014, at 06:06 PM, Benjamin Peterson wrote: > > >> > It occurs to me that since that Aprils' Fools joke is many years old > >> > now, we should remove it. > >> > >> -1 on remo

Re: [Python-Dev] A Friendly IDLE

On Tue, Apr 8, 2014, at 21:25, adnanume...@gmail.com wrote: > Greeting Everyone. First of all I want to introduce my self Adnan Umer as > a student of bachelors in Information Technology. > > > I’ve few suggestions on improving IDLE. Here are few: > > On windows we can open any python file from

[Python-Dev] death to 2.7; long live 2.7

t a measured (6-12 months) pace. These releases will be source only (unless someone steps up to make installers). Planning-on-making-2.7-releases-'til-the-cows-come-home-ly yours, Benjamin ___ Python-Dev mailing list Python-Dev@python.org https://ma

Re: [Python-Dev] death to 2.7; long live 2.7

On Wed, Apr 9, 2014, at 18:31, Guido van Rossum wrote: > I think this is pretty much what Nick Coghlan implied at the summit. He implied that it's currently the plan or that it should be the plan? ___ Python-Dev mailing list Python-Dev@python.org https

Re: [Python-Dev] death to 2.7; long live 2.7

On Wed, Apr 9, 2014, at 18:43, Chris Angelico wrote: > On Thu, Apr 10, 2014 at 11:22 AM, Benjamin Peterson > wrote: > > Planning-on-making-2.7-releases-'til-the-cows-come-home-ly yours, > > Past 2.7.9, will you make 2.7.10 etc, or does that violate other > policies? I&

Re: [Python-Dev] death to 2.7; long live 2.7

On Wed, Apr 9, 2014, at 18:46, Senthil Kumaran wrote: > On Wed, Apr 9, 2014 at 9:22 PM, Benjamin Peterson > wrote: > > > Instead dealing 2.7 will just be completely optional for core > > developers. (The much anticipated vendor support arrives at this point.) > >

Re: [Python-Dev] death to 2.7; long live 2.7

On Wed, Apr 9, 2014, at 19:09, Senthil Kumaran wrote: > On Wed, Apr 9, 2014 at 10:02 PM, Benjamin Peterson > >> Instead dealing 2.7 will just be completely optional for core developers > > I was worried about this part, that if bug-fixes are > optionally back-ported,

Re: [Python-Dev] Windows installers and OpenSSL

On Thu, Apr 10, 2014, at 14:50, Gregory P. Smith wrote: > Yep. All binary Python distributions that bundle SSL support need > updating. > But... what MRAB said. > > We also *likely* have SSL certificates and SSH host keys on > python.orginfrastructure that need to be revoked and new certs > reissu

Re: [Python-Dev] flock in Python 3

On Fri, Apr 11, 2014, at 5:58, Jakub QB Dorňák wrote: > Hi all, > > writing a threaded application I've been surprised that there is no > object api for fcntl.flock implementing __enter__() and __exit__() > methods to be used with 'with' statement. > I have written one (https://pypi.python.org/pyp

Re: [Python-Dev] Appeal for reviews

On Sat, Apr 12, 2014, at 17:30, Stephen J. Turnbull wrote: > I apologize for the tone. I need to go *right* now, and can't fix > that. Really, I'm sympathetic and my goal is not just to defend > python-dev, but to help you get the reviews your work deserves. > Please read with that in mind. I do

[Python-Dev] your next regular installment of python 2.7

o, I doubt anyone cares, but I'm going to do the last security release of python 3.1 concurrently. That will, of course, be a source-only release. Regards, Benjamin ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/list

Re: [Python-Dev] [numpy wishlist] PyMem_*Calloc

On Sun, Apr 13, 2014, at 22:39, Nathaniel Smith wrote: > Hi all, > > The new tracemalloc infrastructure in python 3.4 is super-interesting > to numerical folks, because we really like memory profiling. Numerical > programs allocate a lot of memory, and sometimes it's not clear which > operations a

Re: [Python-Dev] [Python-checkins] cpython (3.1): disallow a negative idx parameter

On Mon, Apr 14, 2014, at 9:14, Zachary Ware wrote: > On Mon, Apr 14, 2014 at 10:52 AM, benjamin.peterson > wrote: > > http://hg.python.org/cpython/rev/4bd1fb0f4f44 > > changeset: 90256:4bd1fb0f4f44 > > branch: 3.1 > > parent: 90235:a8facac493ef >

Re: [Python-Dev] cpython (2.7): do not generate pipe names in the temporary dir

On Wed, Apr 16, 2014, at 7:39, Antoine Pitrou wrote: > On Mon, 14 Apr 2014 18:24:44 +0200 (CEST) > benjamin.peterson wrote: > > http://hg.python.org/cpython/rev/ea677e26dbeb > > changeset: 90269:ea677e26dbeb > > branch: 2.7 > > parent: 90261:c095ff9b

Re: [Python-Dev] Language Summit notes

On Wed, Apr 16, 2014, at 15:26, Antoine Pitrou wrote: > > Hi Taavi, > > Thanks for the report! > > > Disussion about packaging continues. Glyph asks if the PSF could fund a > > usability study on installing Python. People generally seem to think > > it's a good idea. > > What does this mean exa

Re: [Python-Dev] [Python-checkins] cpython (merge 3.4 -> default): Merge 3.4

On Thu, Apr 17, 2014, at 8:55, matthias.klose wrote: > http://hg.python.org/cpython/rev/1d1aefd00f07 > changeset: 90382:1d1aefd00f07 > parent: 90380:517de1983677 > parent: 90381:1a00e04a233d > user:d...@ubuntu.com > date:Thu Apr 17 17:55:03 2014 +0200 > summary: > Merg

Re: [Python-Dev] devguide: Add note about Kushal Das' privs

On Fri, Apr 18, 2014, at 11:29, Antoine Pitrou wrote: > On Mon, 14 Apr 2014 23:18:42 +0200 (CEST) > brett.cannon wrote: > > http://hg.python.org/devguide/rev/c14c8a195fec > > changeset: 686:c14c8a195fec > > user:Brett Cannon > > date:Mon Apr 14 17:18:37 2014 -0400 > > summary: >

Re: [Python-Dev] dict and required hashing

On Fri, Apr 18, 2014, at 14:46, Jim J. Jewett wrote: > (1) I believe the recent consensus was that the number of comparisons > made in a dict lookup is an implementation detail. (Please correct me > if I am wrong.) Absolutely. > > (2) Is "the item will be hashed at least once" a language guar

Re: [Python-Dev] dict and required hashing

On Fri, Apr 18, 2014, at 17:30, Steven D'Aprano wrote: > On Fri, Apr 18, 2014 at 02:57:55PM -0700, Benjamin Peterson wrote: > > On Fri, Apr 18, 2014, at 14:46, Jim J. Jewett wrote: > > > (1) I believe the recent consensus was that the number of comparisons > >

Re: [Python-Dev] PEP 469: Restoring the iterkeys/values/items() methods

On Fri, Apr 18, 2014, at 19:31, Nick Coghlan wrote: > After spending some time talking to the folks at the PyCon Twisted > sprints, they persuaded me that adding back the iterkeys/values/items > methods for mapping objects would be a nice way to eliminate a key > porting hassle for them (and likely

Re: [Python-Dev] dict and required hashing

On Fri, Apr 18, 2014, at 20:05, Victor Stinner wrote: > Does it mean that depending of the number of items, keys can be mutable? > It > sounds like a terrible idea. I believe Jim is talking about internal implementation. ___ Python-Dev mailing list Pytho

Re: [Python-Dev] PEP 469: Restoring the iterkeys/values/items() methods

On Sat, Apr 19, 2014, at 9:30, Stephen J. Turnbull wrote: > Guido van Rossum writes: > > > Does everyone involved know that "for x in d.iterkeys()" is > > equivalent to "for x in d" and works the same in Python 2 and 3? > [...] > > > This doesn't solve itervalues() and iteritems() but I exp

Re: [Python-Dev] ref leaks

On Wed, Apr 23, 2014, at 19:14, Ethan Furman wrote: > Command line: > >./python -m test.regrtest -v -R3:3 test_tools > > Results: > >Ran 44 tests in 7.628s > >OK (skipped=1) >. >test_tools leaked [0, 2, 2] references, sum=4 >1 test failed: >test_tools > > Any wo

Re: [Python-Dev] Python 2.7.7. on Windows

On Mon, Apr 28, 2014, at 17:14, Brian Curtin wrote: > If it's an acceptable change to the release manager (Benjamin?), and > if there's actually time before the RC (I don't know when it is > planned), I am willing to backport my 3.3 change to get this in the >

[Python-Dev] pushing 2.7.7 back a week

I'm pushing the release schedule for 2.7.7 back a week. That means the release candidate will be next weekend (May 17). This will hopefully save some trouble for the people who build our binaries, since 3.4.1 final is happening next weekend, too. Regards, Ben

[Python-Dev] [RELEASED] Python 2.7.7 release candidate 1

sting release. Assuming no horrible bugs are found, 2.7.7 final will be released in two weeks time. Please consider testing your applications and libraries with the release candidate and reporting bugs to http://bugs.python.org/ Enjoy, Benjamin Peterson 2.7 Release Manager [1] http://bugs.pytho

Re: [Python-Dev] Python 2.7.7 and PEP 466

On Sun, May 18, 2014, at 18:53, Guido van Rossum wrote: > On Sun, May 18, 2014 at 5:49 PM, Benjamin Peterson > wrote: > > > Greetings Python users, > > Python 2.7.7 release candidate 1 is now available for download. [...] > > > > http://hg.python.org/cpytho

Re: [Python-Dev] Python 2.7.7 and PEP 466

On Sun, May 18, 2014, at 18:53, Guido van Rossum wrote: > On Sun, May 18, 2014 at 5:49 PM, Benjamin Peterson > wrote: > > > Greetings Python users, > > Python 2.7.7 release candidate 1 is now available for download. [...] > > > > http://hg.python.org/cpytho

Re: [Python-Dev] Python 2.7.7 and PEP 466

On Sun, May 18, 2014, at 18:53, Guido van Rossum wrote: > On Sun, May 18, 2014 at 5:49 PM, Benjamin Peterson > wrote: > > > Greetings Python users, > > Python 2.7.7 release candidate 1 is now available for download. [...] > > > > http://hg.python.org/cpytho

Re: [Python-Dev] Unexpected increase of globals() refcount

On Fri, May 23, 2014, at 8:49, Chandra Srinivasan wrote: > Hi, > I ran the following code in the Python interpreter and am trying to > determine if the behavior I see is expected: > > import sys > print sys.getrefcount(globals()) > class Foo(object): >def __init__(self): > pass > print s

Re: [Python-Dev] Language Summit Follow-Up

On Wed, May 28, 2014, at 15:26, Glyph Lefkowitz wrote: > Add some warnings about python 3 compatibility. > It should at least be possible to get a warning for every single implicit > string coercion. > Old-style classes. > Old-style division. Fun fact: This can be achieved with the -Qwarn comman

[Python-Dev] [RELEASE] Python 2.7.7

s the implementation of PEP 466, Network Security Enhancements for Python 2.7.x. Downloads are at https://python.org/download/releases/2.7.7/ This is a production release. As always, please report bugs to http://bugs.python.org/ Build great things, Benjamin Peterson 2.7 Release Manage

Re: [Python-Dev] subprocess shell=True on Windows doesn't escape ^ character

On Wed, Jun 11, 2014, at 13:26, anatoly techtonik wrote: > I am banned from tracker, so I post the bug here: Being banned from the tracker is not an invitation to use python-dev@ as one. ___ Python-Dev mailing list Python-Dev@python.org https://mail.pyth

Re: [Python-Dev] Why does IOBase.__del__ call .close?

On Wed, Jun 11, 2014, at 17:11, Nikolaus Rath wrote: > MRAB writes: > > On 2014-06-11 02:30, Nikolaus Rath wrote: > >> Hello, > >> > >> I recently noticed (after some rather protacted debugging) that the > >> io.IOBase class comes with a destructor that calls self.close(): > >> > >> [0] nikratio@v

Re: [Python-Dev] Why does IOBase.__del__ call .close?

On Thu, Jun 12, 2014, at 18:06, Nikolaus Rath wrote: > Consider this simple example: > > $ cat test.py > import io > import warnings > > class StridedStream(io.IOBase): > def __init__(self, name, stride=2): > super().__init__() > self.fh = open(name, 'rb') > self.stri

Re: [Python-Dev] Why does IOBase.__del__ call .close?

On Fri, Jun 13, 2014, at 20:04, Nikolaus Rath wrote: > Benjamin Peterson writes: > > On Thu, Jun 12, 2014, at 18:06, Nikolaus Rath wrote: > >> Consider this simple example: > >> > >> $ cat test.py > >> import io > >> import warnings &

Re: [Python-Dev] Why does _pyio.*.readinto have to work with 'b' arrays?

On Sat, Jun 14, 2014, at 15:39, Nikolaus Rath wrote: > It seems to me that a much cleaner solution would be to simply declare > _pyio's readinto to only work with bytearrays, and to explicitly raise a > (more helpful) TypeError if anything else is passed in. That seems reasonable. I don't think _p

Re: [Python-Dev] Issue 21671: CVE-2014-0224 OpenSSL upgrade to 1.0.1h on Windows required

On Tue, Jun 17, 2014, at 12:03, Ned Deily wrote: > In article > <81f84430ce0242e5bfa5b2264777d...@blupr03mb389.namprd03.prod.outlook.com > >, > Steve Dower wrote: > > You'll only need to rebuild the _ssl and _hashlib extension modules with > > the > > new OpenSSL version. The easiest way to do

Re: [Python-Dev] A Subtle Bug in Class Initializations

This would be a good thing to fix. The only hard part is dealing with thirdparty extensions. Note we also have been working around this problem by putting PyType_Ready calls in various generic code paths of the interpreter when an uninitialized type passes through. On Mon, Aug 6, 2018, at 11:0

Re: [Python-Dev] Python 2.7 EOL date

_ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/benjamin%40python.org ___ Python-Dev mail

Re: [Python-Dev] Stop automerging

On Wed, Sep 12, 2018, at 01:33, Serhiy Storchaka wrote: > 12.09.18 01:34, Miss Islington (bot) пише: > > https://github.com/python/cpython/commit/d13e59c1b512069d90efe7ee9b613d3913e79c56 > > commit: d13e59c1b512069d90efe7ee9b613d3913e79c56 > > branch: master > >

Re: [Python-Dev] LDLAST variable in configure.ac

On Mon, Oct 1, 2018, at 12:12, Michael Felt wrote: > Hi all, > > Before I submit a patch to increase the default MAXDATA setting for AIX > when in 32-bit mode - I want to know if I can put this LDFLAG setting in > LDLAST, or if I should introduce a new AC_SUBST() variable (e.g., > LDMAXDATA).

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

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. > > https://bugs.python.org/issue34880 > > Currently, assert do

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

On Tue, Oct 9, 2018, at 17:14, Barry Warsaw wrote: > On Oct 9, 2018, at 16:21, Steven D'Aprano wrote: > > > > On Tue, Oct 09, 2018 at 10:26:50AM -0700, Guido van Rossum wrote: > >> My feeling is that limiting it to strings is fine, but checking those > >> strings for resembling identifiers is p

Re: [Python-Dev] Rename Include/internals/ to Include/pycore/

On Sun, Oct 28, 2018, at 09:20, Victor Stinner wrote: > Hi, > > Python C API has no strict separation between the 3 levels of API: > > * core: Py_BUILD_CORE define > * stable: Py_LIMITED_API define (it has a value) > * regular: no define > > IMHO the current design of header files is done bac

Re: [Python-Dev] Rename Include/internals/ to Include/pycore/

On Sun, Oct 28, 2018, at 14:30, Victor Stinner wrote: > Le dim. 28 oct. 2018 à 21:50, Benjamin Peterson a écrit > : > > I don't think more or less API should be magically included based on > > whether Py_BUILD_CORE is defined or not. If we want to have private > &g

Re: [Python-Dev] Rename Include/internals/ to Include/pycore/

On Mon, Oct 29, 2018, at 05:38, Victor Stinner wrote: > Le lun. 29 oct. 2018 à 06:32, Benjamin Peterson a écrit > : > > > My overall approach is to make sure that we don't leak functions by > > > mistakes into the public API or into the stable API anymore. For &g

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

On Wed, Nov 21, 2018, at 06:53, Matěj Cepl wrote: > On 2018-11-19, 11:59 GMT, Stefan Krah wrote: > > In practice people desperately *have* to use whatever is > > there, including functions with underscores that are not even > > officially in the C-API. > > Yes, there are some functions which e

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

On Thu, Nov 29, 2018, at 04:54, Antoine Pitrou wrote: > On Thu, 29 Nov 2018 09:52:29 + > Paul Moore wrote: > > [This is getting off-topic, so I'll limit my comments to this one email] > > > > On Thu, 29 Nov 2018 at 03:17, Brett Cannon wrote: > > > We have never really had a discussion abo

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

On Wed, Nov 28, 2018, at 15:27, 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?

On Thu, Nov 29, 2018, at 08:45, Antoine Pitrou wrote: > > Le 29/11/2018 à 15:36, Benjamin Peterson a écrit : > >> > >> I'd like to point the discussion is asymmetric here. > >> > >> On the one hand, people who don't have access to PyPI would

Re: [Python-Dev] Standard library vs Standard distribution?

On Fri, 30 Nov 2018 at 00:17, Steven D'Aprano wrote: > > On Thu, Nov 29, 2018 at 01:30:28PM -0800, Nathaniel Smith wrote: > > [...] > > > > https://anaconda.com/ > > > > https://www.activestate.com/products/activepython/ > > > > http://winpython.github.io/ > > > > http://python-xy.github.io/ > > >

[Python-Dev] 2.7.16 release dates

Greetings, I've set the dates for the 2.7.16 release in PEP 373. The release candidate will happen on February 16 with a final release 2 weeks later on March 2 if all goes well. Servus, Benjamin ___ Python-Dev mailing list Python-Dev@python.org

[Python-Dev] [RELEASE] Python 2.7.16 release candidate 1

ng to plan, Python 2.7.16 final will be released on March 2. All the best, Benjamin ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/ar

[Python-Dev] [RELEASE] Python 2.7.16

gelog for a full list of changes: https://raw.githubusercontent.com/python/cpython/v2.7.16/Misc/NEWS.d/2.7.16rc1.rst Please report any bugs to https://bugs.python.org/. Regards, Benjamin 2.7 release manager (on behalf of all Python 2.7's co

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

On Tue, Mar 5, 2019, at 03:18, Miro Hrončok wrote: > On 04. 03. 19 4:30, Benjamin Peterson wrote: > > Hello all, > > I'm pleased to announce the immediate availability of Python 2.7.16 for > > download at https://www.python.org/downloads/release/python-2716/. > >

Re: [Python-Dev] Farewell, Python 3.4

rs of the release team that worked on > Python 3.4: > > > Georg Brandl > > > Julien Palard > > > Martin von Löwis > > > Ned Deily > > > Steve Dower > > > Terry Reedy > > > and all the engineers of the Python infrastructure team. >

Re: [Python-Dev] Python in next Windows 10 update

On Tue, 21 May 2019 at 21:32, Steve Dower wrote: > > In the next Windows 10 update that starts rolling out today, we > (Microsoft) have added "python.exe" and "python3.exe" commands that are > installed on PATH *by default* and will open the Microsoft Store at the > page where we (Python core team

[Python-Dev] Re: Concerns about PEP 634

On Sat, 6 Feb 2021 at 19:54, Daniel Moisset wrote: > > Hi Mark, > > I think some of these issues have already been raised and replied (even if no > agreement has been reached). but this is a good summary, so let me reply with > a summary of responses for this. > > On Sat, 6 Feb 2021 at 15:51, Ma

[Python-Dev] Re: Python standardization

On Fri, Feb 12, 2021, at 12:33, Dan Stromberg wrote: > > What would it take to create an ANSI, ECMA and/or ISO standard for Python? > > It seems to have really helped C. That confuses cause and effect. C was standardized because there sprung up hundreds of vaguely compatible implementations—a

[Python-Dev] Re: PEP 653: Precise Semantics for Pattern Matching

On Thu, 18 Feb 2021 at 17:35, Brandt Bucher wrote: > > Thanks for taking the time to work on this, Mark. Yes, thanks Mark. I'm not sure I've fully understood the PEP yet but I can see some parts that I definitely like. > I fear this is at the expense of most simple classes, which currently "just

[Python-Dev] Re: PEP 653: Precise Semantics for Pattern Matching

On Fri, 19 Feb 2021 at 16:27, Tobias Kohn wrote: > > Quoting Oscar Benjamin : > > > I'm not entirely sure but I think that with PEP 653 you can implement this > > like: > > > > def __deconstruct__(obj): > > if obj.step != 1: > &

[Python-Dev] Re: PEP 653: Precise Semantics for Pattern Matching

On Fri, 19 Feb 2021 at 15:41, Tobias Kohn wrote: > > Hi Mark, > > Thank you for your proposal to try and have more precise semantics for > pattern matching. Of course, the proposal primarily introduces a new and > extended protocol for pattern matching, upon which the 'semantics' is then > bas

[Python-Dev] Re: Have virtual environments led to neglect of the actual environment?

On Fri, 26 Feb 2021 at 09:07, Steven D'Aprano wrote: > > On Fri, Feb 26, 2021 at 11:41:56AM +0900, Stephen J. Turnbull wrote: > > Mike Miller writes: > > > > > "sys-admin" is a bit of an overstatement in my phrasing. The core > > > is that you need to understand how a PATH works and be able to

[Python-Dev] Re: Have virtual environments led to neglect of the actual environment?

On Fri, 26 Feb 2021 at 23:06, Jim J. Jewett wrote: > > I think his point is that most of his students (economics or business, rather > than comp sci) will never need to use Perl or C or Java. Python is friendly > enough to be useful, but this is still a major pain point. Thanks Jim, that is th

[Python-Dev] Re: Have virtual environments led to neglect of the actual environment?

On Sat, 27 Feb 2021 at 11:04, Paul Moore wrote: > > On Sat, 27 Feb 2021 at 01:08, Oscar Benjamin > wrote: > > > > The other point though is that it doesn't need to be like this. If the > > issue was just installing Python and then setting up your PATH then >

[Python-Dev] Re: Have virtual environments led to neglect of the actual environment?

On Sun, 28 Feb 2021 at 07:04, Stephen J. Turnbull wrote: > > Jim J. Jewett writes: > > > > which file am I actually running? > > > which interpreter am I actually running? > > > how do I tell the computer to use a different interpreter? > > > > If you need to care about any of these, then the

[Python-Dev] Re: Have virtual environments led to neglect of the actual environment?

On Mon, 1 Mar 2021 at 00:13, Eryk Sun wrote: > > On 2/28/21, Oscar Benjamin wrote: > > > > - It is possible to configure a default version (although I think you > > have to do it with an environment variable) > > The py launcher in Windows supports a "py.ini&q

[Python-Dev] Re: Request for comments on final version of PEP 653 (Precise Semantics for Pattern Matching)

On Sat, 27 Mar 2021 at 13:40, Mark Shannon wrote: > Hi Mark, Thanks for putting this together. > As the 3.10 beta is not so far away, I've cut down PEP 653 down to the > minimum needed for 3.10. The extensions will have to wait for 3.11. > > The essence of the PEP is now that: > > 1. The semant

[Python-Dev] Re: Request for comments on final version of PEP 653 (Precise Semantics for Pattern Matching)

On Tue, 30 Mar 2021 at 17:32, Brandt Bucher wrote: Hi Brandt, > > Which requires the sympy class `Symbol` to "self" match. For `sympy` to > > support this pattern with PEP 634 is possible, but a bit tricky. With this > > PEP it can be implemented very easily. > > Maybe I'm missing something, b

[Python-Dev] Re: In support of PEP 649

On Fri, 16 Apr 2021 at 01:13, Guido van Rossum wrote: > > On Thu, Apr 15, 2021 at 16:48 Christopher Barker wrote: >> >> And as I noted in my last post — many folks have not been paying attention >> to the typing discussions because they didn’t realize it concerned them. > > It seems a little dis

[Python-Dev] Re: PEP 659: Specializing Adaptive Interpreter

On Thu, 20 May 2021 at 04:58, Terry Reedy wrote: > > On 5/13/2021 4:18 AM, Mark Shannon wrote: > > > If a program does 95% of its work in a C++ library and 5% in Python, it > > can easily spend the majority of its time in Python because CPython is a > > lot slower than C++ (in general). > > I beli

[Python-Dev] Re: IRC #python-dev channel is now on Libera Chat (bye bye Freenode)

On Thu, 27 May 2021 at 00:52, Dan Stromberg wrote: > > > On Wed, May 26, 2021 at 4:25 PM Greg Ewing > wrote: >> >> > On Wed, May 26, 2021 at 8:55 AM Ammar Askar > > > wrote: >> > >> > most >> > recently if your topic mentioned libera.chat, the new freenode ow

Re: [Python-Dev] XML DoS vulnerabilities and exploits in Python

at Are these going to become patches for Python, too? -- Regards, Benjamin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Python 2.7.4 and 3.2.4

hon base or should I > go for 2.7.3 and 3.2.3 -- Regards, Benjamin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

let me know and I >> >> can add them to the agenda. >> > >> > May I in absentia propose at least a short discussion of the XML fixes >> > and accompanying security releases? FWIW, for 3.2 and 3.3 I have no >> > objections to sec

[Python-Dev] 2.7.4 is inevitable

I am going to cut the 2.7.4 release branch next weekend (March 23, 24). Things which are breaking the buildbots at the point will be backed out. Owners of current release blockers will be poked, but nothing is going to hold up the release. The show must go on. Benjamin

Re: [Python-Dev] Status of XML fixes

= 0 > > -Barry I understand why your bedtime is 21:30. :) -- Regards, Benjamin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] [Python-checkins] peps: update 2.7.4 release dates

Good catch. 2013/3/19 Andrew Svetlov : > Are you sure about 2.7.4 2012-04-06? I mean 2012 year. > > On Tue, Mar 19, 2013 at 9:15 PM, benjamin.peterson > wrote: >> http://hg.python.org/peps/rev/ce17779c395c >> changeset: 4810:ce17779c395c >> user:Benjamin

Re: [Python-Dev] IDLE in the stdlib

it was not clear for years whether core developers could touch it even though the external project had died. Either the stdlib and IDLE should go separate ways or development has to happen in the stdlib with CPython release schedule and policies. -- Regards, Benjamin _

Re: [Python-Dev] backporting the _sysconfigdata.py module to 2.7

urrently > only found in 2.7, 3.3 and the trunk. This is a fairly small non-userfacing change, so okay. -- Regards, Benjamin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: ht

Re: [Python-Dev] Interested in GSoC for biopython

On 22 March 2013 21:34, 阮铮 wrote: > Hi, > > I'm Zheng from the University of Georgia. I heard about the GSoC several > weeks before and found biopython also involved in the peoject. I plan to > apply for the GSoC 2013, hoping to make some contributions this summer. [SNIP] This mailing list is for

Re: [Python-Dev] wsgi validator with asynchronous handlers/servers

ration. > > I'm I misinterpreting the pep, or the wsgi validator should be fixed > accordingly? > > Regards, > Luca > > > ___ > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe:

[Python-Dev] [RELEASE] Python 2.7.4 release candidate 1

will occur in 2 weeks. Downloads are at http://python.org/download/releases/2.7.4/ As always, please report bugs to http://bugs.python.org/ Enjoy, Benjamin Peterson 2.7 Release Manager ___ Python-Dev mailing list Python-Dev@python.org

Re: [Python-Dev] Simple IDLE issues to commit before Python 2.7.4 release in two weeks on 4/6/2013

n land for 2.7.5, which will be in approximately 6 months. -- Regards, Benjamin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Simple IDLE issues to commit before Python 2.7.4 release in two weeks on 4/6/2013

2013/3/25 Glyph : > > On Mar 25, 2013, at 1:40 PM, Benjamin Peterson wrote: > > ... Assuming PEP 343 becomes policy ... > > > Are you sure you got this PEP number right? The 'with' statement? Sorry, I meant PEP 434. -- Regards, Benjamin ___

Re: [Python-Dev] [RELEASE] Python 2.7.4 release candidate 1

2013/3/26 Matthias Klose : > Am 25.03.2013 01:30, schrieb Benjamin Peterson: >> 2.7.4 will be the latest maintenance release in the Python 2.7 series. > > I hope it's not (and in the IDLE thread you say so otherwise too). "latest" is different from &qu

Re: [Python-Dev] Can I introspect/reflect to get arguments exec()?

x27;my_exec': > ,, ... > > > In a different setting, CPython byte-code assembly that gets generated for > running exec() is: > > 25 88 LOAD_GLOBAL10 (exec) > 91 LOAD_CONST 4 > ('show_args(inspec

Re: [Python-Dev] Semantics of __int__(), __index__()

On 4 April 2013 10:39, Hrvoje Niksic wrote: > >> On Wed, Apr 3, 2013 at 6:47 AM, Hrvoje Niksic >> wrote: >>> >>> It seems like a good feature that an __int__ implementation can choose to >>> return an int subclass with additional (and optional) information. After >>> all, int subclass instances s

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