Re: [Python-Dev] Single-file Python executables (was: Computed Goto dispatch for Python 2)

2015-05-29 Thread Steven D'Aprano
On Thu, May 28, 2015 at 01:20:06PM -0400, Donald Stufft wrote: I think it’s an issue for all platforms, even when there is a system Python that can be used. Here’s why: * Even on Linux systems Python isn’t always a guaranteed thing to be installed,   for instance Debian works just fine

Re: [Python-Dev] Single-file Python executables (was: Computed Goto dispatch for Python 2)

2015-05-29 Thread Steven D'Aprano
On Thu, May 28, 2015 at 05:38:49PM +0100, Paul Moore wrote: I suspect single file executables just aren't viewed as a desirable solution on Unix. More of an anti-pattern than a pattern. A single file executable means that when you have a security update, instead of patching one library, you

Re: [Python-Dev] Computed Goto dispatch for Python 2

2015-05-29 Thread Nick Coghlan
On 29 May 2015 11:01 am, Victor Stinner victor.stin...@gmail.com wrote: Why not continue to enhance Python 3 instead of wasting our time with Python 2? We have limited resources in term of developers to maintain Python. (I'm not talking about fixing *bugs* in Python 2 which is fine with me.)

Re: [Python-Dev] time-based releases (was Re: Preserving the definition order of class namespaces.)

2015-05-29 Thread Nathaniel Smith
On Thu, May 28, 2015 at 11:40 PM, Nick Coghlan ncogh...@gmail.com wrote: On 29 May 2015 9:17 am, Antoine Pitrou solip...@pitrou.net wrote: On Thu, 28 May 2015 08:48:11 +1000 Nick Coghlan ncogh...@gmail.com wrote: After all, the real difference between the alphas and the final releases

[Python-Dev] Python 3.5 schedule addendum adding a new Python 3.5.0 beta, this weekend

2015-05-29 Thread Larry Hastings
On behalf of the Python 3.5 release team: Due to a particularly bad bug ( http://bugs.python.org/issue24285 ), we're going to issue a new beta of Python 3.5 this weekend. This will not change the rest of the schedule; it'll just bump the remaining beta numbers up by 1. Thus the schedule

Re: [Python-Dev] Keeping competitive with Go (was Re: Computed Goto dispatch for Python 2)

2015-05-29 Thread Nick Coghlan
On 29 May 2015 9:48 am, Donald Stufft don...@stufft.io wrote: On May 28, 2015 at 7:40:26 PM, Nick Coghlan (ncogh...@gmail.com) wrote: One thing I've seen more than once is that new development happens in Python until the problem is understood, then the code is ported to Go.

Re: [Python-Dev] time-based releases (was Re: Preserving the definition order of class namespaces.)

2015-05-29 Thread Nick Coghlan
On 29 May 2015 9:17 am, Antoine Pitrou solip...@pitrou.net wrote: On Thu, 28 May 2015 08:48:11 +1000 Nick Coghlan ncogh...@gmail.com wrote: After all, the real difference between the alphas and the final releases isn't about anything *we* do, it's about the testing *other people* do that

Re: [Python-Dev] Single-file Python executables (was: Computed Goto dispatch for Python 2)

2015-05-29 Thread Paul Sokolovsky
Hello, On Fri, 29 May 2015 20:53:53 +1000 Steven D'Aprano st...@pearwood.info wrote: [ insightful statistics skipped ] I think there are some exciting and interesting languages coming up: Swift, Julia, Go, Rust and others. Only those? Every one in a dozen university student comes up with

Re: [Python-Dev] time-based releases (was Re: Preserving the definition order of class namespaces.)

2015-05-29 Thread Nick Coghlan
On 29 May 2015 20:24, Stephen J. Turnbull step...@xemacs.org wrote: Nathaniel Smith writes: DVCS back in the day :-). Unfortunately hg makes this a little trickier than it could be, because in hg the same commit can't be in two different branches; but this just means you have to insert

Re: [Python-Dev] time-based releases (was Re: Preserving the definition order of class namespaces.)

2015-05-29 Thread Antoine Pitrou
On Fri, 29 May 2015 21:39:55 +1000 Nick Coghlan ncogh...@gmail.com wrote: The key is whether or not we can readily notify people when the most recent known good hash *changes*, and less about the mechanics of how we then record the history of which commits *were* stable, or the identity of the

Re: [Python-Dev] Single-file Python executables (was: Computed Goto dispatch for Python 2)

2015-05-29 Thread Paul Moore
On 29 May 2015 at 09:36, Steven D'Aprano st...@pearwood.info wrote: The point is, in the Linux circles I move in, this idea of single file installation would be about as popular as a police raid at a rave club. Maybe you move in different circles (perhaps more enterprisey?), but I can already

Re: [Python-Dev] Single-file Python executables (was: Computed Goto dispatch for Python 2)

2015-05-29 Thread Steven D'Aprano
On Fri, May 29, 2015 at 07:08:43AM +1000, Nick Coghlan wrote: On 29 May 2015 05:25, Chris Barker chris.bar...@noaa.gov wrote: OK, I'm really confused here: 1) what the heck is so special about go all of a sudden? People have been writing and deploying single file executables built with

Re: [Python-Dev] Single-file Python executables (was: Computed Goto dispatch for Python 2)

2015-05-29 Thread Stephen J. Turnbull
Paul Moore writes: In my environments, we frequently have ancient versions of RHEL installed, sometimes with no Python at all (IIRC) or nothing better than 2.4. That's pretty advanced as older Red Hat systems go. You're lucky it isn't 1.5.2! Getting serious, Red Hat systems have included

Re: [Python-Dev] time-based releases (was Re: Preserving the definition order of class namespaces.)

2015-05-29 Thread Stephen J. Turnbull
Nathaniel Smith writes: DVCS back in the day :-). Unfortunately hg makes this a little trickier than it could be, because in hg the same commit can't be in two different branches; but this just means you have to insert some no-op merges, oh well. Don't use named branches (friends don't

Re: [Python-Dev] Single-file Python executables (was: Computed Goto dispatch for Python 2)

2015-05-29 Thread Paul Moore
On 28 May 2015 at 22:09, Glenn Linderman v+pyt...@g.nevcal.com wrote: This would be something I could use and benefit from immediately upon it being available, so I laud your idea, and hope you have a successful implementation, and look forward to using it. It would largely replace the need

Re: [Python-Dev] Single-file Python executables (was: Computed Goto dispatch for Python 2)

2015-05-29 Thread Donald Stufft
On May 29, 2015 at 4:37:37 AM, Steven D'Aprano (st...@pearwood.info) wrote: On Thu, May 28, 2015 at 01:20:06PM -0400, Donald Stufft wrote: I think it’s an issue for all platforms, even when there is a system Python that can be used. Here’s why: * Even on Linux systems Python

Re: [Python-Dev] Keeping competitive with Go (was Re: Computed Goto dispatch for Python 2)

2015-05-29 Thread Donald Stufft
On May 29, 2015 at 2:58:28 AM, Nick Coghlan (ncogh...@gmail.com) wrote: On 29 May 2015 9:48 am, Donald Stufft wrote: On May 28, 2015 at 7:40:26 PM, Nick Coghlan (ncogh...@gmail.com) wrote: One thing I've seen more than once is that new development happens in Python until

Re: [Python-Dev] Not getting the exact file to start

2015-05-29 Thread Brett Cannon
This mailing list is for the development *of* Python, not *with* it. Your best option for getting help like this is python-l...@python.org. On Fri, May 29, 2015 at 9:36 AM Saket Sourav souravsake...@gmail.com wrote: Hello sir. I have just installed python 3.4.2. I'm not getting the file 'IDLE

Re: [Python-Dev] Single-file Python executables (was: Computed Goto dispatch for Python 2)

2015-05-29 Thread Antoine Pitrou
On Fri, 29 May 2015 18:36:02 +1000 Steven D'Aprano st...@pearwood.info wrote: The point is, in the Linux circles I move in, this idea of single file installation would be about as popular as a police raid at a rave club. This is frankly not true. There are many programs (e.g. games) which

[Python-Dev] Not getting the exact file to start

2015-05-29 Thread Saket Sourav
Hello sir. I have just installed python 3.4.2. I'm not getting the file 'IDLE (python GUI)' to start programming. Or which file I should open to write code ___ Python-Dev mailing list Python-Dev@python.org

Re: [Python-Dev] Obtaining stack-frames from co-routine objects

2015-05-29 Thread Yury Selivanov
Hi Ben, Is there any real-world scenario where you would need this? It looks like this can help with debugging, somehow, but the easiest solution is to put a if debug: log(...) before yield in your switch() function. You'll have a perfect traceback there. Thanks, Yury On 2015-05-29 12:46 AM,

Re: [Python-Dev] Keeping competitive with Go (was Re: Computed Goto dispatch for Python 2)

2015-05-29 Thread André Freitas
Speaking about distribution I believe Pip is the simplest way of distributing. I have used some freezing tools in the past such cxfreeze but with more complex projects they start being hard to manage. Now instead of saying people to goto an url, download and put in the path I just say: pip install

[Python-Dev] Summary of Python tracker Issues

2015-05-29 Thread Python tracker
ACTIVITY SUMMARY (2015-05-22 - 2015-05-29) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open4844 (+11) closed 31241 (+47) total 36085 (+58) Open issues

Re: [Python-Dev] Single-file Python executables (was: Computed Goto dispatch for Python 2)

2015-05-29 Thread Terry Reedy
On 5/28/2015 4:29 PM, Paul Moore wrote: On 28 May 2015 at 20:47, Brett Cannon br...@python.org wrote: I think it's to have a single tool to do it for any platform, not to have the technical nuts and bolts be the same necessarily. I think it's also to figure out if there is anything the

Re: [Python-Dev] Single-file Python executables (was: Computed Goto dispatch for Python 2)

2015-05-29 Thread Paul Moore
On 29 May 2015 at 23:15, Glenn Linderman v+pyt...@g.nevcal.com wrote: I don't presently see any C:\Python34\DLLs or C:\Python34 on my path, but I didn't ask the installer to put it there either. So I'm guessing your option 1 assumes asking the Python installer to put it there? Not automatically

Re: [Python-Dev] 2.7 is here until 2020, please don't call it a waste.

2015-05-29 Thread Christian Heimes
On 2015-05-29 23:14, Gregory P. Smith wrote: On Fri, May 29, 2015 at 12:24 AM Nick Coghlan ncogh...@gmail.com mailto:ncogh...@gmail.com wrote: On 29 May 2015 11:01 am, Victor Stinner victor.stin...@gmail.com mailto:victor.stin...@gmail.com wrote: Why not continue to

Re: [Python-Dev] 2.7 is here until 2020, please don't call it a waste.

2015-05-29 Thread Nick Coghlan
On 30 May 2015 09:57, Antoine Pitrou solip...@pitrou.net wrote: On Sat, 30 May 2015 01:49:10 +0200 Christian Heimes christ...@python.org wrote: For performance patches we have to consider our responsibility for the environment. Every improvement means more speed and less power

Re: [Python-Dev] 2.7 is here until 2020, please don't call it a waste.

2015-05-29 Thread Ian Cordasco
On Fri, May 29, 2015 at 4:14 PM, Gregory P. Smith g...@krypto.org wrote: On Fri, May 29, 2015 at 12:24 AM Nick Coghlan ncogh...@gmail.com wrote: On 29 May 2015 11:01 am, Victor Stinner victor.stin...@gmail.com wrote: Why not continue to enhance Python 3 instead of wasting our time with

Re: [Python-Dev] Single-file Python executables (was: Computed Goto dispatch for Python 2)

2015-05-29 Thread Glenn Linderman
On 5/29/2015 2:45 PM, Paul Moore wrote: On 29 May 2015 at 21:49, Glenn Linderman v+pyt...@g.nevcal.com wrote: That looks interesting, I wonder what compilation environment it would need? I don't think I've even installed a C compiler on my last couple boxes, and the only version of a C compiler

Re: [Python-Dev] 2.7 is here until 2020, please don't call it a waste.

2015-05-29 Thread Nick Coghlan
On 30 May 2015 07:14, Gregory P. Smith g...@krypto.org wrote: On Fri, May 29, 2015 at 12:24 AM Nick Coghlan ncogh...@gmail.com wrote: On 29 May 2015 11:01 am, Victor Stinner victor.stin...@gmail.com wrote: Why not continue to enhance Python 3 instead of wasting our time with Python 2?

Re: [Python-Dev] 2.7 is here until 2020, please don't call it a waste.

2015-05-29 Thread Alexander Walters
Python is a giant cache-miss generator. A little performance boost on the opt-code dispatch isn't going to change that much. If we really do care about improving python to do less environmental damage, then that is a discussion we should be having on it's own merits. It was really out of

Re: [Python-Dev] Single-file Python executables (was: Computed Goto dispatch for Python 2)

2015-05-29 Thread Glenn Linderman
On 5/29/2015 3:28 PM, Paul Moore wrote: On 29 May 2015 at 23:15, Glenn Linderman v+pyt...@g.nevcal.com wrote: I don't presently see any C:\Python34\DLLs or C:\Python34 on my path, but I didn't ask the installer to put it there either. So I'm guessing your option 1 assumes asking the Python

Re: [Python-Dev] Computed Goto dispatch for Python 2

2015-05-29 Thread Ronald Oussoren
Op 28 mei 2015 om 21:37 heeft Chris Barker chris.bar...@noaa.gov het volgende geschreven: On Thu, May 28, 2015 at 12:25 PM, Sturla Molden sturla.mol...@gmail.com wrote: The system Python should be left alone as it is. absolutely! By the way, py2app will build an application bundle

Re: [Python-Dev] Single-file Python executables (was: Computed Goto dispatch for Python 2)

2015-05-29 Thread Steve Dower
Paul Moore wrote: One mildly annoying thing is that python3.dll is only installed in python install dir\DLLs, which typically isn't on PATH. So actually using the limited API from your own application fails by default. Fixing that's mostly a user admin issue, though (and you can just link

Re: [Python-Dev] 2.7 is here until 2020, please don't call it a waste.

2015-05-29 Thread Guido van Rossum
On Fri, May 29, 2015 at 2:52 PM, Ian Cordasco graffatcolmin...@gmail.com wrote: On Fri, May 29, 2015 at 4:14 PM, Gregory P. Smith g...@krypto.org wrote: On Fri, May 29, 2015 at 12:24 AM Nick Coghlan ncogh...@gmail.com wrote: On 29 May 2015 11:01 am, Victor Stinner

Re: [Python-Dev] 2.7 is here until 2020, please don't call it a waste.

2015-05-29 Thread Barry Warsaw
On May 29, 2015, at 04:04 PM, Guido van Rossum wrote: There are a fair number of people on this thread whose employer pays them to work on Python. My guess is that as Python 2.7 gets longer in the tooth, and it becomes harder to motivate volunteers to shepherd contributed patches into Python 2,

Re: [Python-Dev] Keeping competitive with Go (was Re: Computed Goto dispatch for Python 2)

2015-05-29 Thread Nick Coghlan
On 29 May 2015 22:50, Donald Stufft don...@stufft.io wrote: This might be something that people could have done before with C/C++ but with a nicer language behind it... but that's kind of the point? You don't need to be stuck with a terrible language to get a nice single file executable

Re: [Python-Dev] Single-file Python executables (was: Computed Goto dispatch for Python 2)

2015-05-29 Thread Ryan Gonzalez
I did that once; it wasn't worth it. It was no smaller than what PyInstaller would output and required manually adding in the required modules that weren't in the stdlib, along with any extra DLLs (e.g. the Qt DLLs). On Fri, May 29, 2015 at 4:45 PM, Paul Moore p.f.mo...@gmail.com wrote: On 29

Re: [Python-Dev] 2.7 is here until 2020, please don't call it a waste.

2015-05-29 Thread Ian Cordasco
On Fri, May 29, 2015 at 6:04 PM, Guido van Rossum gu...@python.org wrote: On Fri, May 29, 2015 at 2:52 PM, Ian Cordasco graffatcolmin...@gmail.com wrote: On Fri, May 29, 2015 at 4:14 PM, Gregory P. Smith g...@krypto.org wrote: On Fri, May 29, 2015 at 12:24 AM Nick Coghlan

Re: [Python-Dev] 2.7 is here until 2020, please don't call it a waste.

2015-05-29 Thread Nick Coghlan
On 30 May 2015 09:21, Barry Warsaw ba...@python.org wrote: On May 29, 2015, at 04:04 PM, Guido van Rossum wrote: There are a fair number of people on this thread whose employer pays them to work on Python. My guess is that as Python 2.7 gets longer in the tooth, and it becomes harder to

Re: [Python-Dev] 2.7 is here until 2020, please don't call it a waste.

2015-05-29 Thread Antoine Pitrou
On Sat, 30 May 2015 01:49:10 +0200 Christian Heimes christ...@python.org wrote: For performance patches we have to consider our responsibility for the environment. Every improvement means more speed and less power consumption. Python runs of hundreds of thousands of machines in the cloud.

Re: [Python-Dev] [Distutils] Single-file Python executables (including case of self-sufficient package manager)

2015-05-29 Thread Chris Barker
On Fri, May 29, 2015 at 7:23 AM, Paul Sokolovsky pmis...@gmail.com wrote: An example of a product that does this is Chef, they install their own Ruby and everything but libc into /opt/chef to completely isolate themselves from the host system. this sounds a bit like what conda does --

Re: [Python-Dev] Single-file Python executables (was: Computed Goto dispatch for Python 2)

2015-05-29 Thread Glenn Linderman
On 5/29/2015 3:33 AM, Paul Moore wrote: On 28 May 2015 at 22:09, Glenn Linderman v+pyt...@g.nevcal.com wrote: This would be something I could use and benefit from immediately upon it being available, so I laud your idea, and hope you have a successful implementation, and look forward to using

Re: [Python-Dev] Single-file Python executables (including case of self-sufficient package manager)

2015-05-29 Thread Paul Sokolovsky
Hello, On Fri, 29 May 2015 08:35:44 -0400 Donald Stufft don...@stufft.io wrote: [] Another example is one that I personally worked on recently, where the company I worked for wanted to distribute a CLI to our customers which would just work that they could use to interact with the []

Re: [Python-Dev] 2.7 is here until 2020, please don't call it a waste.

2015-05-29 Thread Gregory P. Smith
On Fri, May 29, 2015 at 12:24 AM Nick Coghlan ncogh...@gmail.com wrote: On 29 May 2015 11:01 am, Victor Stinner victor.stin...@gmail.com wrote: Why not continue to enhance Python 3 instead of wasting our time with Python 2? We have limited resources in term of developers to maintain

Re: [Python-Dev] Single-file Python executables (was: Computed Goto dispatch for Python 2)

2015-05-29 Thread Paul Moore
On 29 May 2015 at 21:49, Glenn Linderman v+pyt...@g.nevcal.com wrote: That looks interesting, I wonder what compilation environment it would need? I don't think I've even installed a C compiler on my last couple boxes, and the only version of a C compiler I have is, umm... M$VC++6.0, since