I'd prefer Counter to refuse non-numerical values right away as the
present behaviour may hide bugs (e.g. a forgotten string->int
conversion). Any opinions? (And what about negative values or floats?)
Please file a report on bugs.python.org so that there's a record of this
issue.
Done: http://
Paul Moore wrote:
2009/5/9 Chris Withers :
Martin v. Löwis wrote:
I thought .pth files just had python in them?
Not at all - they never did. They have paths in them.
I've certainly seen them with python in, and that's what I hate about
them...
AIUI, there was a small special case that lines
Ok I've changed the PEP with all the points you mentioned, if you want
to take a look.
2009/5/15 P.J. Eby :
> Next, the doc for the metadata API functions seems quite sparse. ISTR that
> I've previously commented on such issues as case- and
> punctuation-insensitivity of project names, and '/' se
Yes, I don't think it's relevant to optimize install/uninstall code in Python.
In the whole PEP 376 proposal, the only part that will need care will
be the code
that browses sys.path.
On Fri, May 15, 2009 at 9:50 AM, Dirkjan Ochtman wrote:
> On Fri, May 15, 2009 at 8:32 AM, Jeroen Ruigrok van de
At 06:06 PM 5/16/2009 +0200, Tarek Ziadé wrote:
Ok I've changed the PEP with all the points you mentioned, if you want
to take a look.
Some notes:
1. Why ';' separation, instead of tabs as in PEP 262? Aren't
semicolons a valid character in filenames?
2. "if the installed file is located in
On approximately 5/16/2009 9:55 AM, came the following characters from
the keyboard of P.J. Eby:
At 06:06 PM 5/16/2009 +0200, Tarek Ziadé wrote:
Ok I've changed the PEP with all the points you mentioned, if you want
to take a look.
Some notes:
1. Why ';' separation, instead of tabs as in PEP
At 11:17 AM 5/16/2009 -0700, Glenn Linderman wrote:
On approximately 5/16/2009 9:55 AM, came the following characters
from the keyboard of P.J. Eby:
At 06:06 PM 5/16/2009 +0200, Tarek Ziadé wrote:
Ok I've changed the PEP with all the points you mentioned, if you want
to take a look.
Some notes
On approximately 5/16/2009 11:58 AM, came the following characters from
the keyboard of P.J. Eby:
At 11:17 AM 5/16/2009 -0700, Glenn Linderman wrote:
On approximately 5/16/2009 9:55 AM, came the following characters from
the keyboard of P.J. Eby:
At 06:06 PM 5/16/2009 +0200, Tarek Ziadé wrote:
В Сбт, 16/05/2009 в 14:58 -0400, P.J. Eby пишет:
> ";" *is* valid in Windows filenames, actually. Tabs aresn't.
I was sure ';' is separator for PATH in Windows. Do I miss something? If
I remember right os.path.pathsep is ';' under Windows.
___
Python-D
Alexander Shigin wrote:
> В Сбт, 16/05/2009 в 14:58 -0400, P.J. Eby пишет:
>> ";" *is* valid in Windows filenames, actually. Tabs aresn't.
>
> I was sure ';' is separator for PATH in Windows. Do I miss something?
Yes, this:
http://msdn.microsoft.com/en-us/library/aa365247.aspx
Regards,
Martin
On approximately 5/16/2009 1:08 PM, came the following characters from
the keyboard of Martin v. Löwis:
Alexander Shigin wrote:
В Сбт, 16/05/2009 в 14:58 -0400, P.J. Eby пишет:
";" *is* valid in Windows filenames, actually. Tabs aresn't.
I was sure ';' is separator for PATH in Windows. Do I mi
Glenn Linderman wrote:
On approximately 5/16/2009 11:58 AM, came the following characters from
the keyboard of P.J. Eby:
At 11:17 AM 5/16/2009 -0700, Glenn Linderman wrote:
On approximately 5/16/2009 9:55 AM, came the following characters
from the keyboard of P.J. Eby:
At 06:06 PM 5/16/2009 +0
MRAB mrabarnett.plus.com> writes:
>
> I'd probably say that TAB is s reasonable character to use, even though
> it's OK in POSIX; after all, should anyone really be using a control
> character in a filename?
Even newline characters are valid characters in a filename.
Why not go for the safe choi
В Сбт, 16/05/2009 в 13:26 -0700, Glenn Linderman пишет:
> On approximately 5/16/2009 1:08 PM, came the following characters from
> the keyboard of Martin v. Löwis:
> > Yes, this:
> >
> > http://msdn.microsoft.com/en-us/library/aa365247.aspx
>
> Well, maybe he was missing that, or maybe he was mis
В Сбт, 16/05/2009 в 23:15 +0100, MRAB пишет:
> FYI, on RISC OS '/' is a valid filename character and '.' is used as
> the directory separator.
>
> I'd probably say that TAB is s reasonable character to use, even
> though it's OK in POSIX; after all, should anyone really be using a
> control charac
Issue 6012 proposes to add cleanup support for O& converters;
a first client for this would be PyUnicode_FSConverter. Using
cleanup is always necessary if the conversion function allocates
memory, and a later argument converter fails. The memory allocated
must then be released.
There are three opt
16 matches
Mail list logo
