Re: [Python-Dev] Why is Python for Windows compiled with MSVC?

On Wed, Jan 31, 2018 at 03:04:04PM +, Oleg Sivokon wrote: > Now, since Go won't compile with MSVC [...] Perhaps you should be asking Google why Go doesn't support the most popular C compiler on Windows. -- Steve ___ Python-Dev mailing list

[Python-Dev] [RELEASE] Python 3.7.0b1 is now available for testing

On behalf of the Python development community and the Python 3.7 release team, I'm happy to announce the availability of Python 3.7.0b1. b1 is the first of four planned beta releases of Python 3.7, the next major release of Python, and marks the end of the feature development phase for 3.7. You

[Python-Dev] [IMPORTANT] post 3.7.0b1 development now open

Here we are: 3.7.0b1 and feature code freeze! Congratulations and thanks to all of you who've contributed to the huge number of PEPs, features, bug fixes, and doc changes that have gone into 3.7 since feature development began back in September 2016, after 3.6.0b1, 3.6's feature freeze. Now that

[Python-Dev] "threading.Lock().locked()" is not documented

https://docs.python.org/3.6/library/threading.html doesn't document "threading.Lock().locked()", and it is something quite useful. In fact, it is used in "threading.py" itself. For instance, lines 109, 985, 1289. Is there any reason to not document it?. (I didn't investigate other objects in

Re: [Python-Dev] Why is Python for Windows compiled with MSVC?

TL;DR of Steve's post - MSVC is the compiler of choice for most serious software on Windows. So we use it to best integrate with the world. There is no compelling reason to change that. The free-as-in-beer MSVC community edition is finally non-sucky (their earlier efforts were crippled, they seem

Re: [Python-Dev] OS-X builds for 3.7.0

On 1/31/2018 6:23 PM, Chris Barker wrote: On Wed, Jan 31, 2018 at 4:20 AM, INADA Naoki > wrote: > Against the official CPython 3.6 (probably .3 or .4) release I see: > 1 that is 2.01x faster (python-startup, 24.6ms down to 12.2ms)

Re: [Python-Dev] OS-X builds for 3.7.0

On Wed, Jan 31, 2018 at 4:20 AM, INADA Naoki wrote: > > Against the official CPython 3.6 (probably .3 or .4) release I see: > > 1 that is 2.01x faster (python-startup, 24.6ms down to 12.2ms) > > 5 that are >=1.5x,<1.6x faster. > > 13 that are >=1.4x,<1.5x faster. > > 21

Re: [Python-Dev] OS-X builds for 3.7.0

On Wed, Jan 31, 2018 at 3:13 AM, Joni Orponen wrote: > On Wed, Jan 31, 2018 at 12:43 AM, Chris Barker - NOAA Federal < > chris.bar...@noaa.gov> wrote: > >> And maybe we could even get rid of the "Framework" builds.. >>> >> >> Please do not. These make life easier for

Re: [Python-Dev] Why is Python for Windows compiled with MSVC?

Because every other supported platform builds using the native tools, so why shouldn’t the one with the most users? I’m likely biased because I work there and I’m the main intermediary with python-dev, but these days Microsoft is one of the strongest supporters of CPython. We employ the most

Re: [Python-Dev] Why is Python for Windows compiled with MSVC?

On 2018-01-31 19:07, Ray Donnelly wrote: On Wed, Jan 31, 2018 at 3:04 PM, Oleg Sivokon wrote: Hello list. I'll give some background before asking my question in more detail. [snip] Now all I had to do was to re-create my success on Windows (most of the employees in my

[Python-Dev] Backfilling 'awaiting' labels

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

Re: [Python-Dev] Why is Python for Windows compiled with MSVC?

On 1/31/2018 10:04 AM, Oleg Sivokon wrote: Why did you choose to use non-free compiler, which also makes cross-compilation impossible? There wasn't really a reason not to choose MinGW as Python was ported to DOS years before the initial 1998 release of the mingw32 predecessor. There has

Re: [Python-Dev] Why is Python for Windows compiled with MSVC?

On Wed, Jan 31, 2018 at 3:04 PM, Oleg Sivokon wrote: > Hello list. > > I'll give some background before asking my question in more detail. > > I've been tasked with writing some infrastructure code that needs to talk to > Kubernetes. (Kubernetes is a popular software for

[Python-Dev] Why is Python for Windows compiled with MSVC?

Hello list. I'll give some background before asking my question in more detail. I've been tasked with writing some infrastructure code that needs to talk to Kubernetes. (Kubernetes is a popular software for managing and automating virtualization / containerization of cloud services). One of

Re: [Python-Dev] OS-X builds for 3.7.0

Doh! Thank you. Steve Holden ___ 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/archive%40mail-archive.com

Re: [Python-Dev] OS-X builds for 3.7.0

Click on "[x] horizontal" to exchange the two axis ;-) Victor 2018-01-31 16:08 GMT+01:00 Steve Holden : > The horizontal axis labelling in that graph is useless with so many tests > included! > > Would a graphic with hover labels over the bars be more useful? > > Steve

Re: [Python-Dev] OS-X builds for 3.7.0

The horizontal axis labelling in that graph is useless with so many tests included! Would a graphic with hover labels over the bars be more useful? Steve Holden On Wed, Jan 31, 2018 at 1:06 PM, Victor Stinner wrote: > There is https://speed.python.org/comparison/ to

Re: [Python-Dev] OS-X builds for 3.7.0

There is https://speed.python.org/comparison/ to compare Python 2.7, 3.5, 3.6 and master (future 3.7). Victor Le 31 janv. 2018 13:14, "Ray Donnelly" a écrit : > On Wed, Jan 31, 2018 at 11:16 AM, Joni Orponen > wrote: > > On Wed, Jan 31, 2018 at

Re: [Python-Dev] OS-X builds for 3.7.0

> > Against the official CPython 3.6 (probably .3 or .4) release I see: > 1 that is 2.01x faster (python-startup, 24.6ms down to 12.2ms) > 5 that are >=1.5x,<1.6x faster. > 13 that are >=1.4x,<1.5x faster. > 21 that are >=1.3x,<1.4x faster. > 14 that are >=1.2x,<1.3x faster. > 5 that are

Re: [Python-Dev] OS-X builds for 3.7.0

On Wed, Jan 31, 2018 at 11:16 AM, Joni Orponen wrote: > On Wed, Jan 31, 2018 at 9:31 AM, Ray Donnelly > wrote: >> >> We see a 1.1 to 1.2 times performance benefit over official releases as >> measured using 'python performance'. >> >> Apart from a

Re: [Python-Dev] OS-X builds for 3.7.0

On Wed, Jan 31, 2018 at 9:31 AM, Ray Donnelly wrote: > We see a 1.1 to 1.2 times performance benefit over official releases as > measured using 'python performance'. > > Apart from a static interpreter we also enable LTO and PGO and only build > for 64-bit so I'm not

Re: [Python-Dev] OS-X builds for 3.7.0

On Wed, Jan 31, 2018 at 12:43 AM, Chris Barker - NOAA Federal < chris.bar...@noaa.gov> wrote: > And maybe we could even get rid of the "Framework" builds.. >> > > Please do not. These make life easier for doing things the Apple way for > signed sandboxed applications. > > Thanks — good to

Re: [Python-Dev] Making "-j0" the default setting for the test suite?

2018-01-31 3:23 GMT+01:00 Nick Coghlan : > Something like: > > Total duration: 16 minutes 33 seconds (serial execution, pass > '-j0' for parallel execution) > > Such a change would be a safe way to nudge new contributors towards > "./python -m test -j0" for faster local

Re: [Python-Dev] OS-X builds for 3.7.0

On Jan 31, 2018 8:31 AM, "Ray Donnelly" wrote: On Jan 30, 2018 6:47 PM, "Joni Orponen" wrote: On Tue, Jan 30, 2018 at 6:50 PM, Ray Donnelly wrote: > While we're making such macOS-build requests, any chance of

Re: [Python-Dev] OS-X builds for 3.7.0

On Jan 30, 2018 6:47 PM, "Joni Orponen" wrote: On Tue, Jan 30, 2018 at 6:50 PM, Ray Donnelly wrote: > While we're making such macOS-build requests, any chance of building a > static interpreter too? We've been doing that on the Anaconda >

[Python-Dev] 3.7.0b1 status

Just a quick update: thanks to all of you who worked long hours to get features completed and merged in for the 3.7 feature code cutoff yesterday. We release elves have been busy behind the scenes baking goodies. So far everything looks OK. But we're taking a little longer than usual: this