On 26/11/2011 07:46, Maciej Fijalkowski wrote:
On Sat, Nov 26, 2011 at 6:39 AM, Nick Coghlanncogh...@gmail.com wrote:
On Sat, Nov 26, 2011 at 8:14 AM, Michael Foord
fuzzy...@voidspace.org.uk wrote:
On 24 Nov 2011, at 04:06, Nick Coghlan wrote:
On Thu, Nov 24, 2011 at 10:28 AM, Guido van
Le 25/11/2011 19:21, Amaury Forgeot d'Arc a écrit :
And oh, I almost forgot distutils, which needs to parse some Makefile which
of course does not exist in PyPy.
This is a bug (#10764) that I intend to fix for the next releases of 2.7
and 3.2. I also want to fix all modules that use
Le 26/11/2011 03:18, Jesus Cea a écrit :
On 12/11/11 16:56, Éric Araujo wrote:
Ezio and I chatted a bit about his on IRC and he may try to write
a Python parser for Misc/NEWS in order to write a fully automated
merge tool.
Anything new in this front? :-)
Not from me. I don’t have the
On Fri, Nov 25, 2011, Jesus Cea wrote:
Checking documentation abut the contributor license agreement, I had
encounter a wrong HTML link in http://www.python.org/about/help/ :
* Python Patch Guidelines points to
http://www.python.org/dev/patches/, that doesn't exist.
Fixed
PS: The
Le 26/11/2011 06:29, Nick Coghlan a écrit :
On Sat, Nov 26, 2011 at 3:14 PM, Raymond Hettinger wrote:
To me, it would make more sense to split the file into a Misc/NEWS3.2 and
Misc/NEWS3.3 much as we've done with whatsnew. That would make merging a
piece of cake and would avoid adding a
Le 24/11/2011 22:46, Xavier Morel a écrit :
Wouldn't it be simpler to just use MQ and upload the patch(es)
from the series?
MQ is a very powerful and useful tool, but its learning curve is steeper
than regular Mercurial, and it is not designed for long-term
development. Rebasing patches is more
Le 25/11/2011 03:39, Jesus Cea a écrit :
On 24/11/11 18:08, Éric Araujo wrote:
I have a question and I would rather have an answer instead of
actually trying and getting myself in a messy situation.
Clones are cheap, trying is cheap! cheap wink
[snip valid reasons for not trying]
My reply was
Hi,
+1 to all Ezio said. One specific remark:
PendingDeprecationWarning could just become an alias of
DeprecationWarning, but maybe there is code out there that relies on the
distinction, and there is no real value in making it an alias (there is
value in removing it altogether, but we can’t do
Hi,
Going through my email backlog.
Le 11/08/2011 20:30, P.J. Eby a écrit :
At 04:39 PM 8/11/2011 +0200, Éric Araujo wrote:
(By the way, both of these additions to the import protocol (i.e. the
dynamically-added ``__path__``, and dynamically-created modules)
apply recursively to child
2011/11/25 Raymond Hettinger raymond.hettin...@gmail.com:
To me, it would make more sense to split the file into a Misc/NEWS3.2 and
Misc/NEWS3.3 much as we've done with whatsnew. That would make merging a
piece of cake and would avoid adding a parser (an its idiosyncracies) to the
toolchain.
Hi,
I apologize in advance for the length of this mail.
sys.path
When a script or a module is executed by invoking python with proper
arguments, sys.path is extended. When a path to script is given, the
directory containing the script is prepended. When '-m' or '-c' is used,
$CWD is
2011/11/27 Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl:
I guess that it would be useful to have an option to turn off those sys.path
manipulations.
Yeah, I recently proposed exactly that (a '--nopath0' option) in
http://bugs.python.org/issue13475 (that issue also proposes a
-p/--path0 option
12 matches
Mail list logo
