Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10278
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12922
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4806
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11944
___
___
Python-bugs-list
Martin Panter vadmium...@gmail.com added the comment:
I haven’t tried to understand what the patches do, but Issue 5218 looks like a
very similar problem with a patch including a test case.
--
___
Python tracker rep...@bugs.python.org
http
Martin Panter vadmium...@gmail.com added the comment:
See also Issue 4806
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5218
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16809
___
___
Python-bugs-list
Martin Panter vadmium...@gmail.com added the comment:
Another infinite loop that isn't caught in Python 3.2.1: With the symbolic link
link = link/inside
a readlink(link) call will keep looping.
Anyhow, the proposed solution in issue11397_py32_2.patch does not account for
paths
New submission from Martin Panter vadmium...@gmail.com:
See attached leaky_generator.py demo. Python doesn't appear to delete the
exception variable if an exception is thrown back into it (via throw, close
or by deleting it). The result is a reference cycle that needs garbage
collecting
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3982
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14653
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15125
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17974
___
___
Python-bugs-list
Martin Panter added the comment:
I was surprised to discover that “option straddling” doesn’t work this way with
nargs=*. It seems to work fine with most other kinds of positional arguments
I have tried, and I imagine that this was by design rather than accident. Many
Gnu CLI programs also
Martin Panter added the comment:
It sounds like this bug might cover Issue 15112, which is only concerned with
options between different positional parameters.
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1944
___
___
Python-bugs-list
Martin Panter added the comment:
Similarly, I expected this to return rtmp://host/app?auth=token:
urljoin(rtmp://host/app, ?auth=token)
I'm not sure adding everybody's custom scheme to a hard-coded whitelist is the
best way to do solve this.
Below I have identified some other schemes
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1500504
___
___
Python-bugs-list
Martin Panter added the comment:
If this goes ahead, would a bytes.dedent() method be also considered? I
recently discovered that textwrap.dedent() does not work on bytes() in Python
3. I would have used it for the contents of an input file in a test case.
For the record there’s an older
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11344
___
___
Python-bugs-list
New submission from Martin Panter:
I am using the C version of Element Tree via the main ElementTree module. I
have subclassed XMLParser, and created my own target object. I am not that
interested in XML doctypes, but the following simplified code raises a
DeprecationWarning:
$ python3.3
Martin Panter added the comment:
What happened to this patch? The current documentation is very misleading
because the descriptions of the two block fields appear to complement each
other.
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
Martin Panter added the comment:
There is an issue in Python 2.7 (and 3.2 if that matters) with the
DeprecationWarning for the doctype() method being triggered internally. It is a
bit different from this issue but I think a solution has already been committed
for 3.3, and the commit message
Martin Panter added the comment:
The best way to work around it for me is just to ignore the warning. It doesn’t
really worry me that much, I only noticed it while porting a program to Python
3 anyway. So if you don’t want to touch the 2.7 branch I can live
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15873
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3566
___
___
Python-bugs-list
Martin Panter added the comment:
I wrote a basic “urllib.request” handler class that I have been using for HTTP
persistent connections. It is called PersistentConnectionHandler; see
https://github.com/vadmium/python-iview/blob/80dc1b4/iview/hds.py#L442
I am happy for this to be used
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9951
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8402
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15955
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16043
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17005
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16901
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9740
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6181
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3132
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2909
___
___
Python-bugs-list
Martin Panter added the comment:
Also it would be nice to clarify if struct.Struct.format is meant to be a byte
string. Reading the documentation and examples I expected a character string.
It was an issue for me when embedding one structure within another:
HSF_VOL_DESC = Struct( B 5s B
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13238
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8604
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7317
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2927
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16549
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19456
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19411
___
___
Python-bugs-list
Martin Panter added the comment:
The a2b_qp() function also documents a byte string restriction for 3.2, and now
3.3 also seems to support ASCII-compatible text strings. Maybe the
documentation should reflect this also?
--
nosy: +vadmium
___
Python
New submission from Martin Panter:
The AbstractHTTPHandler.do_open() method creates a HTTPConnection object but
does not save it anywhere. This means a ResourceWarning is eventually
triggered, at least when the HTTP server leaves the the connection open.
Demonstration code:
from
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19251
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17823
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3244
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11245
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1348
___
___
Python-bugs-list
Martin Panter added the comment:
Just thinking the first case might get quite a few false positives. Maybe that
would still be acceptable, I dunno.
- the str.encode method is called (redirect to codecs.encode to handle
arbitrary input types in a forward compatible way)
I guess you
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19291
___
___
Python-bugs-list
New submission from Martin Panter:
Currently the documentation for the “bufsize” parameter in the “subprocess”
module says:
Changed in version 3.2.4,: 3.3.1
bufsize now defaults to -1 to enable buffering by default to match the behavior
that most code expects. In 3.2.0 through 3.2.3
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10712
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19627
___
___
Python-bugs-list
Martin Panter added the comment:
The ntpath.splitpath() version is easy to get lost in. It would probably help
if you spelt out all the single-letter variable names, and explained that
tri-state root/separator = None/True/False flag. Maybe there is a less
convoluted way to write it too, I
Martin Panter added the comment:
Please apply Neil Muller’s documentation patch. It is certainly better than the
current state.
If you want to improve it further, maybe get rid of the trailing comma, and
mention that the close() method returns the exit status encoded like the wait()
function
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19656
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15204
___
___
Python-bugs-list
Martin Panter added the comment:
Also it would be good to document that it returns a text stream, not a binary
stream.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6490
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19737
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19691
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9374
___
___
Python-bugs-list
Martin Panter added the comment:
Suspect this is now fixed in a generic way by Issue 9374. The fix seems to be
in 2.7, 3.2 and 3.3.
$ python3.3
Python 3.3.2 (default, May 16 2013, 23:40:52)
[GCC 4.6.3] on linux
Type help, copyright, credits or license for more information.
from urllib.parse
Martin Panter added the comment:
Looks like Issue 9374 already covers most of this, with fixes in 2.7, 3.2 and
3.3.
$ python3.3
Python 3.3.2 (default, May 16 2013, 23:40:52)
[GCC 4.6.3] on linux
Type help, copyright, credits or license for more information.
from urllib.parse import urlparse
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15009
___
___
Python-bugs-list
Martin Panter added the comment:
The updated text to “suprocess.rst” is better, but now it looks like the whole
paragraph fails to render at
http://docs.python.org/dev/library/subprocess#subprocess.Popen. I have no idea
about the syntax but maybe the blank line separating “versionchanged
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19758
___
___
Python-bugs-list
Martin Panter added the comment:
For the record, this issue seemed to forget about the effect of buffering the
pipe to the subprocess’s input stream. Buffering an input pipe means that data
is hidden away until it is flushed, and the close() method can raise a broken
pipe error. I have
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17232
___
___
Python-bugs-list
Martin Panter added the comment:
How about swapping the two sentences for globals() then:
“Returns the dictionary of the module . . . This represents the symbol table .
. .”
I thought the current locals() entry is fairly clear. It actually says _not_ to
modify the dictionary
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18879
___
___
Python-bugs-list
New submission from Martin Panter:
I think the documentation is rather vague about closing the underlying OS
socket. Can someone verify if the following is true (*asterisked* bits are my
additions), and maybe update the documentation?
socket.close(): Close the socket *object*. *The underlying
Martin Panter added the comment:
I think the fix for this bug only works if it gets the server to respond with a
“Connection: close” header itself. I opened Issue 19524 because I was seeing
keep-alive responses using chunked encoding that still trigger a socket leak.
--
nosy: +vadmium
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13797
___
___
Python-bugs-list
Martin Panter added the comment:
Here are two patches: a test case, and a fix for my issue. They were done
against an installed version of Python 3.3.3.
I’m not entirely happy with the fix because it is accessing the private
HTTPConnection.sock attribute from the urllib.request module, which
Changes by Martin Panter vadmium...@gmail.com:
Added file: http://bugs.python.org/file33005/urlopen-sock-close.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19524
Martin Panter added the comment:
Confirmed that this happens when the server sends a chunked response, or sends
a Content-Length header, but not when the server just sends “Connection:
close”. So this looks like the same as Issue 19524, and my patch for that seems
to fix the issue here
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19842
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13736
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6143
___
___
Python-bugs-list
Martin Panter added the comment:
Thanks for looking at this. Perhaps you weren’t pasting the HTTP response into
“socat”. After the six request lines are printed out, I enter the five lines
between HTTP response start and HTTP response end; I didn’t really make
this obvious. Otherwise, urlopen
Martin Panter added the comment:
How is it safer to manually set “h.sock._closed”? Playing with the internals of
HTTPConnection is one thing, but playing with the internals of the socket
object as well does not seem necessary.
Also the ResourceWarning is warning that the socket and connection
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19977
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4492
___
___
Python-bugs-list
Martin Panter added the comment:
Sounds like urlopen() is relying on garbage collection to close the socket and
connection. Maybe it would be better to explicitly close the socket, even if
you do eliminate all the garbage reference cycles.
My test code for Issue 19524 might be useful here
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20059
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20074
___
___
Python-bugs-list
Martin Panter added the comment:
Any chance of backporting this to version 3.3? I think it is a real-world issue
beyond the test suite. See Issue 19524.
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12692
Martin Panter added the comment:
Just discovered the same fix of manually closing the socket object was already
made independently of my patch in the “default” branch! See Issue 12692.
http://hg.python.org/cpython/rev/92656b5df2f2
The main difference is my patch should also close
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20096
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6135
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19729
___
___
Python-bugs-list
Martin Panter added the comment:
Try this to trigger a warning:
python2 -b -c 'bytearray(3) == u3'
-c:1: BytesWarning: Comparison between bytearray and string
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Martin Panter added the comment:
The Issue 12692 fix has been backported to the 3.3 branch, and it fixes this
bug. However here is an updated patch (against revision 28337a8fb502 in the
“3.3” branch) consisting of two left over bits you might still want to use:
1. My test case
2. Explicitly
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13881
___
___
Python-bugs-list
New submission from Martin Panter:
Many of the incremental codecs do not handle fragmented data very well. In the
past I think I was interested in using the Base-64 and Quoted-printable codecs,
and playing with other codecs today reveals many more issues. A lot of the
issues reflect missing
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8796
___
___
Python-bugs-list
1 - 100 of 4209 matches
Mail list logo
