Trent Nelson [EMAIL PROTECTED] added the comment:
I was thinking about this on the way home last night and concluded that
my last suggestion (s/0.0.0.0/127.0.0.1/) is a terrible one as well.
I'd be happy with a mention in the documentation (for now) stating that
if you listen on '0.0.0.0',
Martin v. Löwis [EMAIL PROTECTED] added the comment:
Lists of possible string encodings are here:
http://developer.apple.com/documentation/CoreFoundation/Reference/CFStringRef/Reference/reference.html#//apple_ref/c/tdef/CFStringBuiltInEncodings
and
Georg Brandl [EMAIL PROTECTED] added the comment:
This is already fixed in SVN.
--
resolution: - out of date
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3544
___
Hrvoje Nikšić [EMAIL PROTECTED] added the comment:
Unfortunately dumping the internal representation of non-long arrays
won't work, for several reasons. First, it breaks when porting pickles
between platforms of different endianness such as Intel and SPARC.
Then, it ignores the considerable
New submission from Anders Bensryd [EMAIL PROTECTED]:
We are using Windows XP SP2, Visual Studio 2005 Python 2.5.2.
In Objects/exceptions.c the following code turns off all assertions.
#if defined _MSC_VER _MSC_VER = 1400 defined(__STDC_SECURE_LIB__)
/* Set CRT argument error handler */
Martin v. Löwis [EMAIL PROTECTED] added the comment:
I like to challenge the view what correct behavior is here. If I
pickle an array of 32-bit integer values on one system, and unpickle it
as an array of 64-bit integer values on a different system, is that
correct, or incorrect?
IMO, correct
Hrvoje Nikšić [EMAIL PROTECTED] added the comment:
I think preserving integer width is a good idea because it saves us from
having to throw overflow errors when unpickling to machines with
different width of C types. The cost is that pickling/unpickling the
array might change the array's
Martin v. Löwis [EMAIL PROTECTED] added the comment:
I have now committed the patch to 2.6 as r65654, adding changes for the
bz2module.
I also decided to make the Py_buffer structure own its reference, as I
was running out of arguments why not to. In the process, I removed
New submission from Robert Schuppenies [EMAIL PROTECTED]:
There is a linebreak missing in the doctest extension. See attached patch.
--
assignee: georg.brandl
components: Documentation tools (Sphinx)
files: linebreak.patch
keywords: patch
messages: 71053
nosy: georg.brandl, schuppenies
Matt Giuca [EMAIL PROTECTED] added the comment:
Bill, this debate is getting snipy, and going nowhere. We could argue
about what is the pure and correct thing to do, but we have a
limited time frame here, so I suggest we just look at the important facts.
1. There is an overwhelming consensus
Matt Giuca [EMAIL PROTECTED] added the comment:
By the way, what is the current status of this bug? Is anybody waiting
on me to do anything? (Re: Patch 9)
To recap my previous list of outstanding issues raised by the review:
Should unquote accept a bytes/bytearray as well as a str?
Currently,
Antoine Pitrou [EMAIL PROTECTED] added the comment:
I agree that given two similar patches, the one with more tests earns
some bonus points. Also, it seems to me that round-trippability of
quote()/unquote() is a logical and semantic requirement: in particular,
if there is a default encoding, it
Bill Janssen [EMAIL PROTECTED] added the comment:
I think I'm just going to bring the unwrap already in the _ssl.c code
out to the ssl.py module, that seems to be the simplest fix. Still not
sure you can do a proper fix to ftplib here, but that seems to be a good
thing to do anyway, rather than
Martin v. Löwis [EMAIL PROTECTED] added the comment:
I also started working on porting it to 3.0, but couldn't complete that
port yet - the memoryview object doesn't play nicely.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3139
New submission from Tim Maxwell [EMAIL PROTECTED]:
Steps to reproduce:
Python 2.5.2 (r252:60911, Feb 22 2008, 07:57:53)
[GCC 4.0.1 (Apple Computer, Inc. build 5363)] on darwin
Type help, copyright, credits or license for more information.
from ctypes import *
fields = [('a', c_short,
Senthil [EMAIL PROTECTED] added the comment:
I could reproduce this issue on trunk and p3k branch. The patch attached
by Adrianna Pinska appropriately fixes this issue. I agree with the
logic. Attaching the patch for py3k with the same fix.
Thanks,
Senthil
Added file:
Bill Janssen [EMAIL PROTECTED] added the comment:
OK, I think I've done the minimal fix necessary to the SSL module to
allow this work to proceed.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2054
___
New submission from Miki Tebeka [EMAIL PROTECTED]:
Attached is a patch that add pipe command to the subprocess module.
pipe([ls], [grep, test_]) will return the output of
ls | grep test_.
--
components: Library (Lib)
files: pipe.patch
keywords: patch
messages: 71062
nosy: tebeka
Miki Tebeka [EMAIL PROTECTED] added the comment:
Not sure about the name, maybe chain will be better?
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3548
___
___
Bill Janssen [EMAIL PROTECTED] added the comment:
Larry Masinter is off on vacation, but I did get a brief message saying
that he will dig up similar discussions that he was involved in when he
gets back.
Out of curiosity, I sent a note off to the www-international mailing
list, and received
Bill Janssen [EMAIL PROTECTED] added the comment:
For Antoine:
I think the problem that Barry is facing with the email package is that
Unicode strings are an ambiguous representation of a sequence of bytes;
that is, there are a number of different byte sequences a Unicode string
may have come
Martin v. Löwis [EMAIL PROTECTED] added the comment:
As you must be building your own Python DLL, anyway, can't you just
simply remove that code if you don't want it?
--
nosy: +loewis
___
Python tracker [EMAIL PROTECTED]
Guido van Rossum [EMAIL PROTECTED] added the comment:
Instead of sticking to network byte order, I propose to include byte
order information in the pickle (for example as '' or '' like struct
does), so that pickling/unpickling between the same-endianness
architectures doesn't have to convert
Ismail Donmez [EMAIL PROTECTED] added the comment:
With trunk when running test_multiprocessing in a tight loop I saw
another problem:
test_multiprocessing
Process Process-61:
Traceback (most recent call last):
File /Users/cartman/Sources/py3k/Lib/multiprocessing/process.py,
line 229, in
Bill Janssen [EMAIL PROTECTED] added the comment:
Here's another thought:
Let's put string_to_bytes and string_from_bytes into the binascii
module, as a2b_percent and b2a_percent, respectively.
Then parse.py would import them as
from binascii import a2b_percent as percent_decode_as_bytes
John J Lee [EMAIL PROTECTED] added the comment:
The CaseInsensitive dict class fails to preserve its invariants (implied
invariants, since there are no tests for it). There are also problems
with the documentation in the patch. I will submit a modified patch, I
hope later this week.
John J Lee [EMAIL PROTECTED] added the comment:
By the way, this is a feature addition, not a bug fix. The first beta
releases for 2.6 and 3.0 came out some time ago, so according to PEP
361, this change should not be committed to trunk until after the 2.6 /
3.0 maintenance branches have been
Antoine Pitrou [EMAIL PROTECTED] added the comment:
Le mardi 12 août 2008 à 19:37 +, Bill Janssen a écrit :
Let's put string_to_bytes and string_from_bytes into the binascii
module, as a2b_percent and b2a_percent, respectively.
Well, it's my personal opinion, but I think we should focus
Guido van Rossum [EMAIL PROTECTED] added the comment:
Matt Giuca [EMAIL PROTECTED] added the comment:
By the way, what is the current status of this bug? Is anybody waiting
on me to do anything? (Re: Patch 9)
I'll be reviewing it today or tomorrow. From looking at it briefly I
worry that the
cfr [EMAIL PROTECTED] added the comment:
Interesting. At least the 39 makes sense. I don't understand the
documentation well enough to know what the 79 is about.
I'm sorry but I can't work out what I should do with:
printf(Encoding is %x\n, enc);
Am I meant to use this in python, a standard
cfr [EMAIL PROTECTED] added the comment:
Just realised what I'm meant to do with it. Sorry - it is late (early,
actually). Will report back when I get a chance to recompile.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3362
31 matches
Mail list logo
