[Python-Dev] Something like PEP-0304 - suppress *.pyc generation
Hello, im looking for something like PEP-0304 ( http://www.python.org/dev/peps/pep-0304/) I need something to suppress the generation of *.pyc files because i have very much different machines which call a python program at same time. the python program crashes at different places and on different machines - i think the problem are the *.pyc files of different machines which are generated at the same time. is pep-0304 implemented in a newer python version ( we use 2.4.4 ) or is there a work around or can someone implement pep-0304? thank you for your help! Viele Grüße Christian Doll___ 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] Something like PEP-0304 - suppress *.pyc generation
On Mon, Apr 20, 2009 at 12:25 PM, Steven D'Aprano wrote: > On Mon, 20 Apr 2009 04:54:15 pm christian.d...@basf.com wrote: > >> I need something to suppress the generation of *.pyc files >> because i have very much different machines which call a python >> program at same time. > > This list is for development *of* Python, not development *with* > Python. You would probably be better off on comp.lang.python or > python-l...@python.org. > > However, I believe that the normal way to prevent the generation > of .pyc files is to remove write access to the directory where > the .py files are. Checkout http://docs.python.org/using/cmdline.html#envvar-PYTHONDONTWRITEBYTECODE Regards. -- İsmail DÖNMEZ ___ 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] Something like PEP-0304 - suppress *.pyc generation
On Mon, 20 Apr 2009 04:54:15 pm christian.d...@basf.com wrote: > I need something to suppress the generation of *.pyc files > because i have very much different machines which call a python > program at same time. This list is for development *of* Python, not development *with* Python. You would probably be better off on comp.lang.python or python-l...@python.org. However, I believe that the normal way to prevent the generation of .pyc files is to remove write access to the directory where the .py files are. -- Steven D'Aprano ___ 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-ideas] Proposed addtion to url lib.parse in 3.1 (and urlparse in 2.7)
Bill Janssen parc.com> writes: > > Sure. But nowhere does a spec say that this page charset should be used > in sending the values of a FORM using application/x-www-form-urlencoded > in a new HTTP request. It's just a convention some browsers use. Let's call it a de facto standard then. A behaviour doesn't have to be engraved in an RFC to be considered standard. Regards Antoine. ___ 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] #!/usr/bin/env python --> python3 where applicable
Greg Ewing wrote: > Steven Bethard wrote: > >> That's an unfortunate decision. When the 2.X line stops being >> maintained (after 2.7 maybe?) we're going to be stuck with the "3" >> suffix forever for the "real" Python. > > I don't see why we have to be stuck with it forever. > When 2.x has faded into the sunset, we can start > aliasing 'python' to 'python3' if we want, can't we? > You could, but it's not my favorite idea. Gets people used to the idea of python == python2 and python3 == python3 as something they can count on. Then says, "Oops, that was just an implementation detail, we're changing that now". Much better to either make a clean break and call the new language dialect python3 from now and forever or force people to come up with solutions to whether /usr/bin/python == python2 or python3 right now while it's fresh and relevant in their minds. -Toshio signature.asc Description: OpenPGP digital signature ___ 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-ideas] Proposed addtion to url lib.parse in 3.1 (and urlparse in 2.7)
Antoine Pitrou wrote: > Bill Janssen parc.com> writes: > > > > Sure. But nowhere does a spec say that this page charset should be used > > in sending the values of a FORM using application/x-www-form-urlencoded > > in a new HTTP request. It's just a convention some browsers use. > > Let's call it a de facto standard then. A behaviour doesn't have to be > engraved > in an RFC to be considered standard. Sure. And if HTTP was all about browsers keying off pages, that would be fine with me. But it's not. HTTP is used in lots of places where there are no browsers; in fact, the idea we're busy bike-shedding is all about a client-side library making calls on a server. It's used in places where there are no "pages", too, just servers on which clients are making REST-style calls. So in the real world, the only way in which you can reliably post non-ASCII values to a server using HTTP is with multipart/form-data, which allows you to explicitly say what character set you are using. I've debugged this problem too many times with REST servers of various kinds to think otherwise. Bill ___ 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-ideas] Proposed addtion to url lib.parse in 3.1 (and urlparse in 2.7)
Bill Janssen parc.com> writes: > > Sure. And if HTTP was all about browsers keying off pages, that would > be fine with me. But it's not. HTTP is used in lots of places where > there are no browsers; I'm sorry, I don't follow you. The fact that something else than a browser makes the request shouldn't change the behaviour on the /server/ side. > It's used in > places where there are no "pages", too, just servers on which clients > are making REST-style calls. So what? The designer of the REST API must mandate an encoding (most probably UTF-8 rather than Latin-1 as you bizarrely seemed to imply) and the problem is solved. Complaining that the RFC doesn't specify all this sounds like an excuse for programmer laziness. Antoine. ___ 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-ideas] Proposed addtion to url lib.parse in 3.1 (and urlparse in 2.7)
Antoine Pitrou wrote: > Bill Janssen parc.com> writes: > > > > Sure. And if HTTP was all about browsers keying off pages, that would > > be fine with me. But it's not. HTTP is used in lots of places where > > there are no browsers; > > I'm sorry, I don't follow you. The fact that something else than a browser > makes > the request shouldn't change the behaviour on the /server/ side. I'm talking about the client side, though. > > It's used in > > places where there are no "pages", too, just servers on which clients > > are making REST-style calls. > > So what? The designer of the REST API must mandate an encoding (most probably > UTF-8 rather than Latin-1 as you bizarrely seemed to imply) and the problem is > solved. Sure, if they understand that they have to do it. > Complaining that the RFC doesn't specify all this sounds like an excuse for > programmer laziness. Or incompetence, which I'm afraid is a more likely issue. Lots of folks write their own HTTP servers, and don't really understand just *what* they need to specify. As a client-side user of one of those servers, I'm left in the dark. I think we've beat this to death for python-dev. Feel free to continue it on Web-SIG, though, if you wish. Bill ___ 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] #!/usr/bin/env python --> python3 where applicable
On 19 Apr 2009, at 02:17, Stephen J. Turnbull wrote: Nick Coghlan writes: 3. Change the shebang lines in Python standard library scripts to be version specific and update release.py to fix them all when bumping the version number in the source tree. +1 I think that it's probably best to leave "python", "python2", and "python3" for the use of downstream distributors. ISTR that was what Guido concluded, in the discuss that led to Python 3 defaulting to altinstall---it wasn't just convenient because Python 3 is a major change, but that experience has shown that deciding which Python is going to be "The python" on somebody's system just isn't a decision that Python should make. Ok, so if I understand, the situation is: * python points to 2.x version * python3 points to 3.x version * need to be able to run certain 3k scripts from cmdline (since we're talking about shebangs) using Python3k even though "python" points to 2.x So, if I got the situation right, then do these same scripts understand that PYTHONPATH and PYTHONHOME and all the others are also probably pointing to 2.x code? Jared ___ 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] #!/usr/bin/env python --> python3 where applicable
Jared Grubb wrote: On 19 Apr 2009, at 02:17, Stephen J. Turnbull wrote: Nick Coghlan writes: 3. Change the shebang lines in Python standard library scripts to be version specific and update release.py to fix them all when bumping the version number in the source tree. +1 I think that it's probably best to leave "python", "python2", and "python3" for the use of downstream distributors. ISTR that was what Guido concluded, in the discuss that led to Python 3 defaulting to altinstall---it wasn't just convenient because Python 3 is a major change, but that experience has shown that deciding which Python is going to be "The python" on somebody's system just isn't a decision that Python should make. Ok, so if I understand, the situation is: * python points to 2.x version * python3 points to 3.x version * need to be able to run certain 3k scripts from cmdline (since we're talking about shebangs) using Python3k even though "python" points to 2.x So, if I got the situation right, then do these same scripts understand that PYTHONPATH and PYTHONHOME and all the others are also probably pointing to 2.x code? IIRC the proposal was to also create PYTHON3PATH and PYTHON3HOME. Michael Jared ___ 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/fuzzyman%40voidspace.org.uk -- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog ___ 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
[Python-Dev] 3.1 beta blockers
The first (and only) beta of 3.1 is scheduled for less than 2 weeks away, May 2nd, and is creeping onto the horizon. There are currently 6 blockers: #5692: test_zipfile fails under Windows - This looks like a fairly easy fix. #5775: marshal.c needs to be checked for out of memory errors - Looks like Eric has this one. #5410: msvcrt bytes cleanup - It would be nice to have a Windows expert examine the patch on this issue for correctness. #5786: [This isn't applicable to 3.1] #5783: IDLE cannot find windows chm file - Awaiting a fix to the IDLE or the doc build system. -- Thanks for your work, 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] 3.1 beta blockers
I forgot one: #4136 - Porting the json changes to py3k - This issue exposed the brokenness of the json module in py3k. Was any consensus reached about what the API of json should be? If the beta time rolls around and nothing has changed on this issue, I think Antoine's patch, which makes json input and output unicode should be applied. 2009/4/20 Benjamin Peterson : > The first (and only) beta of 3.1 is scheduled for less than 2 weeks > away, May 2nd, and is creeping onto the horizon. There are currently 6 > blockers: -- 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] 3.1 beta blockers
In article <1afaf6160904201509g2f5e784ah34c728732ca9b...@mail.gmail.com>, Benjamin Peterson wrote: > I forgot one: [...] What about #5756 - idle, pydoc, et al removed from 3.1? -- Ned Deily, n...@acm.org ___ 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] 3.1 beta blockers
On Apr 20, 2009, at 6:37 PM, Ned Deily wrote: In article <1afaf6160904201509g2f5e784ah34c728732ca9b...@mail.gmail.com>, Benjamin Peterson wrote: I forgot one: [...] What about #5756 - idle, pydoc, et al removed from 3.1? Were we going to remove this from 2.7 also? I'm working on splitting two of my Tools (pynche and world) off into separate projects and can't remember what we decided about that. -Barry PGP.sig Description: This is a digitally signed message part ___ 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] 3.1 beta blockers
In article <40d62762-abab-4de1-9be2-798e40ae2...@python.org>, Barry Warsaw wrote: > On Apr 20, 2009, at 6:37 PM, Ned Deily wrote: > > > In article > > <1afaf6160904201509g2f5e784ah34c728732ca9b...@mail.gmail.com>, > > Benjamin Peterson wrote: > >> I forgot one: [...] > > > > What about #5756 - idle, pydoc, et al removed from 3.1? > > Were we going to remove this from 2.7 also? I'm working on splitting > two of my Tools (pynche and world) off into separate projects and > can't remember what we decided about that. I'm confused. The point of #5756 was that 3.x builds are broken because the installation of idle, pydoc, 2to3, and smtpd.py have been commented out in setup.py and thus these scripts are no longer being installed. Unless I'm missing something, that's the only way they were being installed in any form. If nothing else, the change breaks the OSX installer build. If they were removed deliberately (and are intended to be removed from 2.7??), there needs to be some replacement and/or doc changes, no? -- Ned Deily, n...@acm.org ___ 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] 3.1 beta blockers
2009/4/20 Barry Warsaw : > On Apr 20, 2009, at 6:37 PM, Ned Deily wrote: > >> In article >> <1afaf6160904201509g2f5e784ah34c728732ca9b...@mail.gmail.com>, >> Benjamin Peterson wrote: >>> >>> I forgot one: [...] >> >> What about #5756 - idle, pydoc, et al removed from 3.1? > > Were we going to remove this from 2.7 also? I'm working on splitting two of > my Tools (pynche and world) off into separate projects and can't remember > what we decided about that. Those aren't installed as scripts like idle and pydoc, so I believe they can go. -- 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] 3.1 beta blockers
2009/4/20 Ned Deily : > In article > <1afaf6160904201509g2f5e784ah34c728732ca9b...@mail.gmail.com>, > Benjamin Peterson wrote: >> I forgot one: [...] > > What about #5756 - idle, pydoc, et al removed from 3.1? I just bumped priority and left a comment. -- 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
