On Fri, May 16, 2008 at 5:49 PM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Raymond Hettinger wrote:
>>
>> I say leave the new names in 3.0 and let the 2-to-3 tool do its job.
>> Why confuse the 2.6 landscape with double naming clutter.
>
> To increase the common subset of code which can run on both
Raymond Hettinger wrote:
I say leave the new names in 3.0 and let the 2-to-3 tool do its job.
Why confuse the 2.6 landscape with double naming clutter.
To increase the common subset of code which can run on both 2.6 and 3.0
*without* invoking 2to3?
PEP-8'ifying these names also makes them ea
Martin v. Löwis wrote:
In building a package with several platforms, I
ran across the warning message below from Visual
Studio 2008. Should we add the /EHsc option to the
compile_options in distutils for MSVC? Or is it more
complex than that...
Who is "we"? If you have a module that uses C++
On Fri, May 16, 2008 at 1:32 AM, Ulrich Berning
<[EMAIL PROTECTED]> wrote:
>
> As long as the ctypes extension doesn't build on major Un*x platforms (AIX,
> HP-UX), I don't like to see ctypes dependend modules included into the
> stdlib. Please keep the stdlib as portable as possible.
Nice in theo
[Brett[
For the sake of argument, let's consider the Queue module. It is now
named queue. For 2.6 I plan on having both Queue and queue listed in
the index, with Queue deprecated with instructions to use the new
name.
FWIW, I don't consider this to be a value added backport.
Renaming doesn't
> Until recently, python had its own cross-platform implementation of
> strerror, but it was removed because it was deemed redundant. This
> tells me that it should work on windows.
That conclusion is incorrect. It works on MSVCRT, but for this specific
aspect, using MSVCRT is a bad idea (because
> Apart from (1) and (2) which I think are unavoidable, nearly all the C
> code is Windows specific. I assume you don't want to bring
> in the whole of pywin32 into stdlib...
I wouldn't structure it the same way as pywin32, but yes, I have
pondered exposing all of Win32 in a module, as part of th
2008/5/14 "Martin v. Löwis" <[EMAIL PROTECTED]>:
>> I really do feel that inclusion of this library offers us the best of
>> both worlds - it gives us (as a community) an easy answer to those
>> people who would dismiss python due to the GIL and it also allows
>> users to easily implement their app
On Fri, May 16, 2008 at 5:43 AM, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
> On 2008-05-12 04:34, Brett Cannon wrote:
>>
>> For the sake of argument, let's consider the Queue module. It is now
>> named queue. For 2.6 I plan on having both Queue and queue listed in
>> the index, with Queue deprecated
On Fri, May 16, 2008 at 10:42 AM, Guilherme Polo <[EMAIL PROTECTED]> wrote:
> 2008/5/16 Collin Winter <[EMAIL PROTECTED]>:
>> On Fri, May 16, 2008 at 10:30 AM, Guilherme Polo <[EMAIL PROTECTED]> wrote:
>>> 2008/5/12 Collin Winter <[EMAIL PROTECTED]>:
On Mon, May 12, 2008 at 1:58 PM, Guilherme
2008/5/16 Collin Winter <[EMAIL PROTECTED]>:
> On Fri, May 16, 2008 at 10:30 AM, Guilherme Polo <[EMAIL PROTECTED]> wrote:
>> 2008/5/12 Collin Winter <[EMAIL PROTECTED]>:
>>> On Mon, May 12, 2008 at 1:58 PM, Guilherme Polo <[EMAIL PROTECTED]> wrote:
Hello,
Would someone tell me how
On Fri, May 16, 2008 at 10:30 AM, Guilherme Polo <[EMAIL PROTECTED]> wrote:
> 2008/5/12 Collin Winter <[EMAIL PROTECTED]>:
>> On Mon, May 12, 2008 at 1:58 PM, Guilherme Polo <[EMAIL PROTECTED]> wrote:
>>> Hello,
>>>
>>> Would someone tell me how can I add a new entry in the MAPPING dict in
>>> th
2008/5/12 Collin Winter <[EMAIL PROTECTED]>:
> On Mon, May 12, 2008 at 1:58 PM, Guilherme Polo <[EMAIL PROTECTED]> wrote:
>> Hello,
>>
>> Would someone tell me how can I add a new entry in the MAPPING dict in
>> the lib2to3/fixes/fix_imports.py that does the following:
>>
>> "import A" gets fixe
[Facundo]
I think that including in the stdlib a threading-like-API module is a
clear win.
I also think this is vital and should not wait for Py2.7.
Raymond
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/p
On Fri, May 16, 2008 at 10:52 AM, Yannick Gingras <[EMAIL PROTECTED]> wrote:
> "Alexander Belopolsky" <[EMAIL PROTECTED]> writes:
>
> try:
>> ...open('/')
>> ... except Exception,e:
>> ...pass
>> ...
> print e
>> [Errno 21] Is a directory
>>
>> So now I am not sure what OP is propos
2008/5/13 Jesse Noller <[EMAIL PROTECTED]>:
> I am looking for any questions, concerns or benchmarks python-dev has
> regarding the possible inclusion of the pyprocessing module to the
> standard library - preferably in the 2.6 timeline. In March, I began
+1 to include this module in the library
On 2008-05-16 17:02, Alexander Belopolsky wrote:
On Fri, May 16, 2008 at 10:52 AM, Yannick Gingras <[EMAIL PROTECTED]> wrote:
print e
[Errno 21] Is a directory
So now I am not sure what OP is proposing. Do you want to replace 21
with EISDIR in the above?
Yes, that's what I had in mind.
I
On Fri, May 16, 2008 at 11:22 AM, Thomas Heller <[EMAIL PROTECTED]> wrote:
> Ulrich Berning schrieb:
>> Nick Craig-Wood wrote:
>>
>>>Jesse Noller <[EMAIL PROTECTED]> wrote:
>>>
>>>
I am looking for any questions, concerns or benchmarks python-dev has
regarding the possible inclusion of th
On 2008-05-16 16:15, Nick Coghlan wrote:
Alexander Belopolsky wrote:
Yannick Gingras ygingras.net> writes:
2) Where can I find the symbolic name in C?
Use standard C library char* strerror(int errnum) function. You can see
an example usage in Modules/posixmodule.c (posix_strerror).
I don
Ulrich Berning schrieb:
> Nick Craig-Wood wrote:
>
>>Jesse Noller <[EMAIL PROTECTED]> wrote:
>>
>>
>>> I am looking for any questions, concerns or benchmarks python-dev has
>>> regarding the possible inclusion of the pyprocessing module to the
>>> standard library - preferably in the 2.6 timelin
On Fri, May 16, 2008 at 10:52 AM, Yannick Gingras <[EMAIL PROTECTED]> wrote:
> print e
>> [Errno 21] Is a directory
>>
>> So now I am not sure what OP is proposing. Do you want to replace 21
>> with EISDIR in the above?
>
> Yes, that's what I had in mind.
>
In this case, I have a more drasti
"Alexander Belopolsky" <[EMAIL PROTECTED]> writes:
try:
> ...open('/')
> ... except Exception,e:
> ...pass
> ...
print e
> [Errno 21] Is a directory
>
> So now I am not sure what OP is proposing. Do you want to replace 21
> with EISDIR in the above?
Yes, that's what I had in mi
On Fri, May 16, 2008 at 10:15 AM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Alexander Belopolsky wrote:
..
>> Use standard C library char* strerror(int errnum) function. You can see
>> an example usage in Modules/posixmodule.c (posix_strerror).
>
> I don't believe that would provide adequate Wind
On Sat, 17 May 2008 00:15:23 +1000, Nick Coghlan <[EMAIL PROTECTED]> wrote:
Alexander Belopolsky wrote:
Yannick Gingras ygingras.net> writes:
2) Where can I find the symbolic name in C?
Use standard C library char* strerror(int errnum) function. You can see
an example usage in Modules/posi
Alexander Belopolsky wrote:
Yannick Gingras ygingras.net> writes:
2) Where can I find the symbolic name in C?
Use standard C library char* strerror(int errnum) function. You can see
an example usage in Modules/posixmodule.c (posix_strerror).
I don't believe that would provide adequate Win
Yannick Gingras wrote:
1) Should OSError.__str__() print the symbolic name of errno?
+1 (assuming the performance hit for doing so is incurred only when the
exception is actually printed)
2) Where can I find the symbolic name in C?
Modules/errnomodule.c
Cheers,
Nick.
--
Nick Coghlan |
Yannick Gingras ygingras.net> writes:
..
>
> 1) Should OSError.__str__() print the symbolic name of errno?
>
+1 for the change
> 2) Where can I find the symbolic name in C?
Use standard C library char* strerror(int errnum) function. You can see
an example usage in Modules/posixmodule.c (pos
On 2008-05-16 15:28, Rasmus Andersson wrote:
On 16 maj 2008, at 15.00, M.-A. Lemburg wrote:
On 2008-05-15 22:33, A.M. Kuchling wrote:
So there already is a lot of porting effort needed to support
a reasonable number of targets.
I don't think it takes a lot of effort to keep distutils
runn
Ulrich Berning wrote:
More and more people tend to say "Runs on Un*x" when they really mean
"Tested on Linux". Un*x is not Linux.
Hmm, perhaps that would be why there are Solaris, FreeBSD and Tru64
machines amongst the main Python buildbots, to go along with the
assorted OS X, Windows and Lin
On Fri, May 16, 2008 at 10:32:30AM +0200, Ulrich Berning wrote:
> As long as the ctypes extension doesn't build on major Un*x platforms
> (AIX, HP-UX), I don't like to see ctypes dependend modules included into
> the stdlib. Please keep the stdlib as portable as possible.
> More and more people t
On 2008-05-15 23:54, Benjamin Peterson wrote:
At the moment, the test for the platform module merely calls each
function. I realize that this is a hard module to test well, but are
there some assumptions we can make? For example, if sys.platform is
'java', can it be assumed that java_ver is going
On 2008-05-15 22:33, A.M. Kuchling wrote:
Python 2.6 renames the ConfigParser module to be configparser.
Distutils imports ConfigParser in various places. I just made a
commit updating the import in one places, and then noticed that part
of commit r63248, which made the same change, was reverte
* M.-A. Lemburg wrote:
> On 2008-05-12 04:34, Brett Cannon wrote:
> > For the sake of argument, let's consider the Queue module. It is now
> > named queue. For 2.6 I plan on having both Queue and queue listed in
> > the index, with Queue deprecated with instructions to use the new
> > name.
> >
On 2008-05-12 04:34, Brett Cannon wrote:
For the sake of argument, let's consider the Queue module. It is now
named queue. For 2.6 I plan on having both Queue and queue listed in
the index, with Queue deprecated with instructions to use the new
name.
But what to do about all the references. Shou
Hello! I would like to share a useful tip on how to speedup many short ssh
(scp, rsync, svn over ssh) sessions (on Unix). Sorry if this information is
widely known; I learned the trick a week ago and I am pretty happy with it.
OpenSSH4 on Unix allows connection sharing - utilizing one authenticate
2008/5/16 Hrvoje Nikšić <[EMAIL PROTECTED]>:
> On Fri, 2008-05-16 at 08:04 -0400, Tom Pinckney wrote:
> > Here's one example, albeit from a few years ago
> >
> > http://aspn.activestate.com/ASPN/Mail/Message/numpy-discussion/1625465
>
> Thanks for the pointer. I'm not sure I fully understand Konr
On Fri, 2008-05-16 at 08:04 -0400, Tom Pinckney wrote:
> Here's one example, albeit from a few years ago
>
> http://aspn.activestate.com/ASPN/Mail/Message/numpy-discussion/1625465
Thanks for the pointer. I'm not sure I fully understand Konrad Hinsen's
concerns, but maybe the problem is that Nump
Here's one example, albeit from a few years ago
http://aspn.activestate.com/ASPN/Mail/Message/numpy-discussion/1625465
But, I am a numpy novice and so no idea what it actually does in its
current form.
On May 16, 2008, at 4:17 AM, Hrvoje Nik?i? wrote:
On Thu, 2008-05-15 at 21:02 -0400, Tom
A.M. Kuchling wrote:
* There's no standalone distutils package on PyPI, nor can I find
such a package with a general web search. Am I missing it?
* I do not see users advising other users to use a later version of
Distutils to fix their problems.
Is anyone actually benefiting from the ef
Hi,
I spent some time googleing for "OSError 4" before it occurred to me
that "4" was actually an irrelevant implementation detail. As soon as
I searched for "EINTR", I found exactly what I was looking for. (not
really but this is another story)
I jumped to the conclusion that OSError.__str_
Martin v. Lo"wis wrote:
(Hmm, is changing Modules/Setup enough to sort the Windows build out as
well? Or does that need a separate change to some of the Visual Studio
files?)
The latter. Whenever you add, remove, or rename an extension module, you
need to adjust the PCbuild files as well. (tech
Nick Craig-Wood wrote:
Jesse Noller <[EMAIL PROTECTED]> wrote:
I am looking for any questions, concerns or benchmarks python-dev has
regarding the possible inclusion of the pyprocessing module to the
standard library - preferably in the 2.6 timeline. In March, I began
working on the PEP for
On Thu, 2008-05-15 at 21:02 -0400, Tom Pinckney wrote:
> I found some other references where people were expressing concern
> over numpy releasing the GIL due to the fact that other C extensions
> could call numpy and unexpectedly have the GIL released on them (or
> something like that).
Cou
2008/5/15 Atsuo Ishimoto <[EMAIL PROTECTED]>:
> With my proposal, print("Hello\u03C8") prints "Hello\u03C8" instead of
> raising an exception. And print(repr("Hello\u03C8")) prints
> "'Hello\u03C8'", so no garbage are printed.
>
> Now, let's say you are Greek and working on Greek version of XP.
>
44 matches
Mail list logo
