[Python-Dev] Python launcher command line usage (Was: 3.2.1 encoding surprise)

2011-07-19 Thread Paul Moore
On 19 July 2011 02:41, Vinay Sajip vinay_sa...@yahoo.co.uk wrote: The use of py from the command line is merely a convenience for developers (as the PEP says) - it's better to rely on shebang lines together with settings in the .ini to get the behaviour you want. But it's a *huge* convenience

Re: [Python-Dev] Python launcher command line usage (Was: 3.2.1 encoding surprise)

2011-07-19 Thread Antoine Pitrou
On Tue, 19 Jul 2011 16:00:57 +0100 Paul Moore p.f.mo...@gmail.com wrote: On 19 July 2011 02:41, Vinay Sajip vinay_sa...@yahoo.co.uk wrote: The use of py from the command line is merely a convenience for developers (as the PEP says) - it's better to rely on shebang lines together with

Re: [Python-Dev] Python launcher command line usage (Was: 3.2.1 encoding surprise)

2011-07-19 Thread Paul Moore
On 19 July 2011 16:16, Antoine Pitrou solip...@pitrou.net wrote: On Tue, 19 Jul 2011 16:00:57 +0100 Paul Moore p.f.mo...@gmail.com wrote: On 19 July 2011 02:41, Vinay Sajip vinay_sa...@yahoo.co.uk wrote: The use of py from the command line is merely a convenience for developers (as the

[Python-Dev] knee.py import hook in 2.6

2011-07-19 Thread Timothy D. Kadich
Hi, I'm trying to use the import hook in Python2.6, but I'm having a problem. It doesn't work for numpy. My error is such: import knee import numpy Traceback (most recent call last): File stdin, line 1, in module File knee.py, line 16, in import_hook q, tail =

Re: [Python-Dev] knee.py import hook in 2.6

2011-07-19 Thread Oleg Broytman
Hello. We are sorry but we cannot help you. This mailing list is to work on developing Python (adding new features to Python itself and fixing bugs); if you're having problems learning, understanding or using Python, please find another forum. Probably python-list/comp.lang.python mailing

Re: [Python-Dev] Python launcher command line usage (Was: 3.2.1 encoding surprise)

2011-07-19 Thread Antoine Pitrou
On Tue, 19 Jul 2011 17:21:30 +0100 Paul Moore p.f.mo...@gmail.com wrote: Two questions: 1. What level of support is there for PEP 397? If it's unlikely to get accepted, there's little point in basing a solution on it. It only needs support from our Windows users or developers. It is doubtful

[Python-Dev] email-6.0.0.a1

2011-07-19 Thread R. David Murray
OK, so I've released the first iteration of the email6 package on pypi as email-6.0.0a1. After install you import it as email6. This will allow anyone curious and/or motivated to test it out under Python 3.2. I'm especially interested in anyone with a working program that uses email in 3.2: it

Re: [Python-Dev] Python launcher command line usage (Was: 3.2.1 encoding surprise)

2011-07-19 Thread Nick Coghlan
On Wed, Jul 20, 2011 at 6:59 AM, Antoine Pitrou solip...@pitrou.net wrote: (if you want an explicit +1, here it is :-)) FWIW, +1 from me as well, but keep in mind that I actively avoid programming on Windows (although I'm happy enough using it as a gaming platform) Cheers, Nick. -- Nick

Re: [Python-Dev] Python launcher command line usage (Was: 3.2.1 encoding surprise)

2011-07-19 Thread Mark Hammond
On 20/07/2011 1:00 AM, Paul Moore wrote: On 19 July 2011 02:41, Vinay Sajipvinay_sa...@yahoo.co.uk wrote: The use of py from the command line is merely a convenience for developers (as the PEP says) - it's better to rely on shebang lines together with settings in the .ini to get the behaviour

Re: [Python-Dev] Python launcher command line usage (Was: 3.2.1 encoding surprise)

2011-07-19 Thread Terry Reedy
On 7/19/2011 12:21 PM, Paul Moore wrote: On 19 July 2011 16:16, Antoine Pitrousolip...@pitrou.net wrote: On Tue, 19 Jul 2011 16:00:57 +0100 Perhaps this could be changed? As far as I can see, python.exe is a small executable around ~25KB (all the code being in the DLL), so there doesn't

[Python-Dev] Draft PEP: Simplified Package Layout and Partitioning

2011-07-19 Thread P.J. Eby
So, over on the Import-SIG, we were talking about the implementation and terminology for PEP 382, and it became increasingly obvious that things were, well, not entirely okay in the implementation is easy to explain department. Anyway, to make a long story short, we came up with an