New submission from Dmitry Vasiliev :
Currently help(zlib) gives the following traceback:
Python 3.1a2+ (py3k:71538M, Apr 12 2009, 21:54:44)
>>> import zlib
>>> help(zlib)
Traceback (most recent call last):
File "", line 1, in
File "Lib/site.py&q
Dmitry Vasiliev added the comment:
Attached patch for test_urllib, possible source of the "NO_PROXY" problem.
Added file: http://bugs.python.org/file12577/no_proxy.patch
___
Python tracker
<http://bugs.python.
Dmitry Vasiliev added the comment:
Antoine Pitrou wrote:
>> Strange error and it seems there is only part of the traceback. I've
>> already seen such "partially displayed" Python 3 traceback and error
>> actually can be in very different place.
>
> If y
Dmitry Vasiliev added the comment:
Antoine Pitrou wrote:
> There's another problem in that buildbot failure with the environment
> variable "NO_PROXY". We'll see if it's still there after the patch.
Strange error and it seems there is only part of the tr
Dmitry Vasiliev added the comment:
Antoine Pitrou wrote:
> People, does this patch look ok to you?
Oh, didn't know about -bb.
The patch looks OK for me.
___
Python tracker
<http://bugs.python.or
Dmitry Vasiliev added the comment:
Graham Dumpleton wrote:
> Thus have odd situation where with Python 3.0, one could technically return
> str as iterable, with rule that would apply would be that each str returned
> would then be converted to bytes by way of latin-1 conversion
New submission from Dmitry Vasiliev :
Small typo about "call" Process.daemon flag. The patch attached.
--
assignee: georg.brandl
components: Documentation
files: multiprocessing.patch
keywords: patch
messages: 78516
nosy: georg.brandl, hdima
severity: normal
status: open
ti
Dmitry Vasiliev added the comment:
Antoine Pitrou wrote:
> Why do you say they were removed? I see code like "assert
> isinstance(value, bytes)".
Support and tests for mutable "bytearray" and "memoryview" was removed.
All subclasses of "bytes"
Dmitry Vasiliev added the comment:
Antoine Pitrou wrote:
>> Hmm, it's strange because such tests was removed two versions ago (per
>> discussion with Phillip). But at the time they really was needed.
>
> Not a big deal anyway, let's keep them and we'll see.
Dmitry Vasiliev added the comment:
Antoine Pitrou wrote:
> The patch looks ok to me, although the tests against mutable byte-like
> types are probably useless.
Hmm, it's strange because such tests was removed two versions ago (per
discussion with Phillip). But at the time they
Dmitry Vasiliev added the comment:
Added check for wsgi.input.read() argument.
Added file: http://bugs.python.org/file12454/wsgiref2.patch
___
Python tracker
<http://bugs.python.org/issue4
Dmitry Vasiliev added the comment:
Attached more generic version of the patch.
--
nosy: +hdima
Added file: http://bugs.python.org/file12450/io_fixes.patch
___
Python tracker
<http://bugs.python.org/issue4
Dmitry Vasiliev added the comment:
Graham Dumpleton wrote:
> the check for number of arguments supplied to wsgi.input.read() is wrong as
> it allows for an optional argument,
> when argument is supposed to mandatory.
I think it's a good idea. I'll up
Dmitry Vasiliev added the comment:
Attached updated version of the patch.
Added file: http://bugs.python.org/file12447/wsgiref.patch
___
Python tracker
<http://bugs.python.org/issue4
Changes by Dmitry Vasiliev :
Removed file: http://bugs.python.org/file12439/wsgiref.patch
___
Python tracker
<http://bugs.python.org/issue4718>
___
___
Python-bugs-list m
Dmitry Vasiliev added the comment:
Phillip J. Eby wrote:
> Graham: thanks for pointing that out; I completely forgot we already
> *had* the migration discussion on the Web-SIG! It just slipped my
> mind because I didn't have any 3.0 work on the horizon.
Good to see we came
Dmitry Vasiliev added the comment:
Attached new WSGI 1.0+ version of the patch.
Added file: http://bugs.python.org/file12439/wsgiref.patch
___
Python tracker
<http://bugs.python.org/issue4
Changes by Dmitry Vasiliev :
Removed file: http://bugs.python.org/file12431/wsgiref_pep333.patch
___
Python tracker
<http://bugs.python.org/issue4718>
___
___
Python-bug
Changes by Dmitry Vasiliev :
Removed file: http://bugs.python.org/file12429/wsgiref2.patch
___
Python tracker
<http://bugs.python.org/issue4718>
___
___
Python-bugs-list m
Changes by Dmitry Vasiliev :
Removed file: http://bugs.python.org/file12423/wsgiref.patch
___
Python tracker
<http://bugs.python.org/issue4718>
___
___
Python-bugs-list m
Dmitry Vasiliev added the comment:
Antoine Pitrou wrote:
> Le mardi 23 décembre 2008 à 11:15 +0000, Dmitry Vasiliev a écrit :
>> OK, I've attached PEP-333 compatible fixes for wsgiref.
>
> I may be mistaken, but it seems that your patch forces iso-8859-1
> encoding of ht
Dmitry Vasiliev added the comment:
OK, I've attached PEP-333 compatible fixes for wsgiref. I think there is
only one problem remains:
- wsgiref expects io.BytesIO as input and output streams because of
http.server module. I didn't find any restrictions on data returned by
read() met
Dmitry Vasiliev added the comment:
New version of the patch:
- Now only Unicode strings are allowed as status and headers because
allowing bytes leads to big changes in wsgiref.validate and
wsgiref.handlers;
--
versions: -Python 3.1
Added file: http://bugs.python.org/file12429
Dmitry Vasiliev added the comment:
Antoine Pitrou wrote:
>> If you want to change to using bytes, you're going to have to take it
>> to the Web-SIG and hash out a revision to PEP 333, which at the moment
>> requires the use of strings, period.
>
> What was cal
Dmitry Vasiliev added the comment:
Antoine Pitrou wrote:
> FYI, instead of trying to do exhaustive type checking in _check_type(),
> you can just rely on duck typing and catch the TypeError:
Good point! I'll update the patch soon.
___
Python tra
New submission from Dmitry Vasiliev :
It seems the wsgiref package was copied from Python 2.* without any
modifications. There are already 3 issues about that but they only
describe a part of the problem so I decided to start a new one. The
issues was:
http://bugs.python.org/issue3348
http
New submission from Dmitry Vasiliev <[EMAIL PROTECTED]>:
The attached patch removes dependency on ctypes from uuid.uuid1() and
uuid.uuid4() functions.
--
components: Library (Lib)
files: uuid.patch
keywords: patch
messages: 76107
nosy: hdima
severity: normal
status: open
title
Dmitry Vasiliev <[EMAIL PROTECTED]> added the comment:
The patch is good. It's exactly what I told about in msg72132.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.
Dmitry Vasiliev <[EMAIL PROTECTED]> added the comment:
Oh, you need to read the comments first:
- Use of ISO-8859-1 it's a bad idea here. See msg72776 for details.
Moreover RFC-3977 explicitly say about UTF-8, so I think we need to use
UTF-8.
- Maybe set_encoding() isn't needed
Dmitry Vasiliev <[EMAIL PROTECTED]> added the comment:
Good idea! Don't know why I didn't use it in the very first version. :-)
New patch attached.
Added file: http://bugs.python.org/file11623/bisect2.patch
___
Python tracker <[EMAI
Dmitry Vasiliev <[EMAIL PROTECTED]> added the comment:
Actually it was an optimization. PyList_Insert() was used for list and
list-derived objects.
I've attached the patch which fix the issue and for me the new code
looks even cleaner than the original code.
--
keywords:
Dmitry Vasiliev <[EMAIL PROTECTED]> added the comment:
RFC-3977 say the following about headers:
- The names of headers (e.g., "From" or "Subject") MUST be in
US-ASCII.
- Header values SHOULD use US-ASCII or an encoding based on it, such
as RFC 2047 [RFC2047],
Dmitry Vasiliev <[EMAIL PROTECTED]> added the comment:
If I understand it correctly there is no "character set used by server"
because every article can be in different encoding. RFC-3977 say:
"""
The character set of article bodies SHOULD be indicated in the
arti
Dmitry Vasiliev <[EMAIL PROTECTED]> added the comment:
Actually RFC-977 said all characters must be in ASCII, but RFC-3977
changed default character set to UTF-8. So I think UTF-8 must be default
encoding, not Latin-1. Moreover Latin-1 can silently hide a real
encoding, for example:
Dmitry Vasiliev <[EMAIL PROTECTED]> added the comment:
Ah, yes.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3728>
___
___
Python-bugs
New submission from Dmitry Vasiliev <[EMAIL PROTECTED]>:
Example:
>>> from imaplib import IMAP4
>>> m = IMAP4("localhost")
Traceback (most recent call last):
File "", line 1, in
File "/py3k/Lib/imaplib.py", line 185, in __init__
New submission from Dmitry Vasiliev <[EMAIL PROTECTED]>:
Example:
>>> from poplib import POP3
>>> p = POP3("localhost")
>>> p.user("user")
Traceback (most recent call last):
File "", line 1, in
File "/py3k/Lib/poplib.py&qu
Dmitry Vasiliev <[EMAIL PROTECTED]> added the comment:
I think only bytes need to be allowed for write() and read*() because of
low-level nature of Telnet. I can create a patch later.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
New submission from Dmitry Vasiliev <[EMAIL PROTECTED]>:
Simple example:
>>> from telnetlib import Telnet
>>> t = Telnet("google.com", 80)
>>> t.write("GET / HTTP/1.1\r\n")
Traceback (most recent call last):
File "",
Dmitry Vasiliev <[EMAIL PROTECTED]> added the comment:
I've attached the patch which adds encoding parameter to the NNTP class.
--
keywords: +patch
Added file: http://bugs.python.org/file11292/nntplib.patch
___
Python tracker <[E
New submission from Dmitry Vasiliev <[EMAIL PROTECTED]>:
The following commands fail badly:
>>> from nntplib import NNTP
>>> s = NNTP("free-text.usenetserver.com")
Traceback (most recent call last):
File "", line 1, in
File "/py3k/Lib/nn
41 matches
Mail list logo
