New submission from Martin Matusiak:
The offending section:
http://docs.python.org/devguide/faq.html#how-do-i-find-which-changeset-introduced-a-bug-or-regression
I think this could be improved a bit. The key point is that "hg bisect
--bad/good" is a command relative to the c
New submission from Martin Matusiak:
- The purpose of this document is to outline how the latter three steps of the
process works.
work
--
components: Devguide
files: typo_compiler.diff
keywords: patch
messages: 200567
nosy: ezio.melotti, numerodix
priority: normal
severity: normal
New submission from Martin Matusiak:
- Querying data from the node structs can be done with the following macros
(which are all defined in Include/token.h
They are actually in Include/node.h, which is logical, because that is where
"node" is defined.
--
components: Devg
New submission from Martin Matusiak:
Location:
http://docs.python.org/devguide/compiler.html#parse-trees
- To tie all of this example, consider the rule for ‘while’:
Probably meant to be: To tie all of this together with an example, ...
- The node representing this will have TYPE(node
New submission from Martin Matusiak:
- All code relating to the arena is in either Include/pyarena.h or
Python/pyarena.c .
I propose: All code relating to the arena is either in Include/pyarena.h or in
Python/pyarena.c .
--
components: Devguide
files: wording_compiler.diff
keywords
Martin Matusiak added the comment:
- This needs to only be called in strategic areas where the compiler exits.
I propose: This only needs to be called in strategic areas where the compiler
exits.
--
Added file: http://bugs.python.org/file32247/wording_compiler2.diff
Martin Matusiak added the comment:
- The functions called to generate AST nodes from the parse tree all have the
name ast_for_xx where xx is what the grammar rule that the function handles
(alias_for_import_name is the exception to this).
I'm not sure if this ought to be "where
Martin Matusiak added the comment:
- Function and macros for creating and using asdl_seq * types as found in
Python/asdl.c and Include/asdl.h:
I propose: The following are functions and macros for creating and using
asdl_seq * types as found in Python/asdl.c and Include/asdl.h
Martin Matusiak added the comment:
- As for handling the line number on which a statement is defined, is handled
by compiler_visit_stmt() and thus is not a worry.
I don't understand the final clause here. What is not a worry and why would it
be a worry?
The grammar is awkward as
Martin Matusiak added the comment:
- But you will also need to change the ‘compiler’ package. The key files to do
that are Lib/compiler/pyassem.py and Lib/compiler/pycodegen.py .
"compiler" was removed in 2.6 or 2.7 iirc. I think it's safe to remove these
two sentences.
--
Martin Matusiak added the comment:
- If you wish to make changes that affect the output of bytecode without having
to update the magic number each time (while testing your changes) you can just
delete your old .py(c|o) files! Even though you will end up changing the magic
number if you change
Martin Matusiak added the comment:
- marshaling
marshalling
--
Added file: http://bugs.python.org/file32251/wording_typo.diff
___
Python tracker
<http://bugs.python.org/issue19
Martin Matusiak added the comment:
- import.c
- Home of the magic number (named MAGIC) for bytecode versioning
Probably out of date. I cannot find MAGIC being defined in this file.
--
___
Python tracker
<http://bugs.python.org/issue19
Martin Matusiak added the comment:
- Lib/
- compiler/
- pyassem.py
- One of the files that must be modified if Include/opcode.h is changed.
- pycodegen.py
- One of the files that must be modified if Include/opcode.h is changed.
More mentions of the compiler package.
--
Added file: http
Martin Matusiak added the comment:
I have been thinking about a fix for this. A straightforward fix would be to
add a kwarg readrc=True to the constructor of Pdb that will default to reading
the rc files as it does now, and allows disabling this default.
The implication is that all tests in
Changes by Martin Matusiak :
--
nosy: +numerodix
___
Python tracker
<http://bugs.python.org/issue8083>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Martin Matusiak :
--
nosy: +numerodix
___
Python tracker
<http://bugs.python.org/issue7757>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Martin Matusiak :
--
nosy: +numerodix
___
Python tracker
<http://bugs.python.org/issue19318>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Martin Matusiak :
--
nosy: +numerodix
___
Python tracker
<http://bugs.python.org/issue19319>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Martin Matusiak :
--
nosy: +numerodix
___
Python tracker
<http://bugs.python.org/issue17951>
___
___
Python-bugs-list mailing list
Unsubscribe:
Martin Matusiak added the comment:
I see one potential problem with this, namely that refactoring code that
contains "break n" statements would become more error prone whenever the depth
of the code block gets modified. So if you had something like:
for i in range(10):
for j i
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 with that
Changes by Martin Panter :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue15873>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Martin Panter :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue3566>
___
___
Python-bugs-list mailing list
Unsubscribe:
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 as the
Changes by Martin Panter :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue19456>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Martin Panter :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue19411>
___
___
Python-bugs-list mailing list
Unsubscribe:
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 :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue19251>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Martin Panter :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue17823>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Martin Panter :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue3244>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Martin Panter :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue11245>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Martin Panter :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue1348>
___
___
Python-bugs-list mailing list
Unsubscribe:
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 y
Changes by Martin Panter :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue19291>
___
___
Python-bugs-list mailing list
Unsubscribe:
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 th
Changes by Martin Panter :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue10712>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Martin Panter :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue19627>
___
___
Python-bugs-list mailing list
Unsubscribe:
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 :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue19656>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Martin Panter :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue15204>
___
___
Python-bugs-list mailing list
Unsubscribe:
Martin Panter added the comment:
Also it would be good to document that it returns a text stream, not a binary
stream.
--
___
Python tracker
<http://bugs.python.org/issue6
Changes by Martin Panter :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue19737>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Martin Panter :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue19691>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Martin Panter :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue9374>
___
___
Python-bugs-list mailing list
Unsubscribe:
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 "lice
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
Changes by Martin Panter :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue15009>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Martin Dengler :
--
nosy: +mdengler
___
Python tracker
<http://bugs.python.org/issue7511>
___
___
Python-bugs-list mailing list
Unsubscribe:
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 :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue19758>
___
___
Python-bugs-list mailing list
Unsubscribe:
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 Dengler :
--
nosy: +mdengler
___
Python tracker
<http://bugs.python.org/issue2226>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Martin Dengler :
--
nosy: +mdengler
___
Python tracker
<http://bugs.python.org/issue8743>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Martin Panter :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue17232>
___
___
Python-bugs-list mailing list
Unsubscribe:
Martin Pitt added the comment:
More precisely, it broke unittest's discovery (not specific to autopilot). For
any installed test, you now get:
$ python -m unittest discover lazr
Traceback (most recent call last):
File "/usr/lib/python2.7/runpy.py", line 162, in _run
Martin Pitt added the comment:
In this new code:
mod_file = os.path.abspath(getattr(module, '__file__',
full_path))
realpath = os.path.splitext(os.path.realpath(mod_file))[0]
fullpath_noext =
os.path.splitext(os.pat
Martin Pitt added the comment:
Yes, this affects python 2.7 only; as I said, this is all solved in python3 by
introducing the explicit extensions like __pycache__/*..cpython-33.pyc so that
multiple versions can share one directory. With that these symlink hacks aren't
necessary any
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 :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue18879>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Martin Natano:
This patch adds support for Bitrig to 2.7.
--
components: Build
files: cpython2.7-bitrig.patch
keywords: patch
messages: 204930
nosy: Martin.Natano
priority: normal
severity: normal
status: open
title: Add support for Bitrig
versions: Python 2.7
Added
New submission from Martin Natano:
This patch adds support for Bitrig to 3.4.
--
components: Build
files: cpython3.4-bitrig.patch
keywords: patch
messages: 204931
nosy: Martin.Natano
priority: normal
severity: normal
status: open
title: Add support for Bitrig to 3.4
versions: Python 3.4
Changes by Martin Natano :
--
title: Add support for Bitrig -> Add support for Bitrig to 2.7
___
Python tracker
<http://bugs.python.org/issue19853>
___
___
Py
Martin Mokrejs added the comment:
The issue could have been caused the malfunctioning memory or CPU.
http://bugs.python.org/issue18843#msg204954
--
___
Python tracker
<http://bugs.python.org/issue18
Martin Mokrejs added the comment:
Hi,
I think I should report back what I found on the hardware side. While memory
testing tools like memtest86+ and other did not find any error, the built in
Dell ePSA test suite likely does compute a checksum of tested memory regions.
It reported some
Martin Mokrejs added the comment:
The issue could have been caused the malfunctioning memory or CPU.
http://bugs.python.org/issue18843#msg204954
--
___
Python tracker
<http://bugs.python.org/issue18
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 :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue13797>
___
___
Python-bugs-list mailing list
Unsubscribe:
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 :
Added file: http://bugs.python.org/file33005/urlopen-sock-close.diff
___
Python tracker
<http://bugs.python.org/issue19524>
___
___
Python-bug
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 :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue19842>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Martin Panter :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue13736>
___
___
Python-bugs-list mailing list
Unsubscribe:
Martin Vignali added the comment:
I'm okay with just testing the first two bytes, it's the method we currently
use for our
internal tools.
But maybe it can be interesting, to add another test, in order to detect
incomplete file
(created when a camera make a recording error for ex
Changes by Martin Dengler :
--
nosy: +mdengler
___
Python tracker
<http://bugs.python.org/issue2943>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Martin Panter :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue6631>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Martin Panter:
This isn’t a particularly important problem for me but when reading the code I
noticed some bit rot in this function, where a host name in a “file:” URL would
be handled differently than intended.
* The url[:2] == '//' check is probably wrong bec
Changes by Martin Panter :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue21793>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Martin Panter :
Added file: http://bugs.python.org/file35980/test2.patch
___
Python tracker
<http://bugs.python.org/issue19524>
___
___
Python-bugs-list mailin
Martin Panter added the comment:
Added a new test for the invalid response case. Now both tests are included in
test2.patch.
I separated the actual fix into a separate close3.4.patch (refreshed for the
3.4 branch). This way it is easier for me to make sure the tests work before
applying the
Martin Panter added the comment:
A file called “package/__main__.py” is executed as a script by “python -m
package”. See <https://docs.python.org/dev/library/__main__.html>.
I’ve came across this issue myself. You don’t even need the __main__.py file to
be doing anything special, as l
New submission from Martin Panter:
It looks like if you pass a “fileobj” argument to “gettarinfo”, it assumes it
can use the “name” as a text string.
>>> import tarfile
>>> with tarfile.open("/dev/null", "w") as tar, open("/bin/sh",
Martin Panter added the comment:
Opened Issue 21996 for the “gettarinfo” method.
Also, Serhiy, I think you may have got me mixed up with someone else. I don’t
think I did any patches here, so I probably shouldn’t be credited for them
New submission from Martin Morrison:
Minimal testcase of the problem situation is tokenising (with posix mode on):
''),
Specifically, an empty string, followed by a non-word character, followed by a
non-space character. In this case, the token buffer is empty and due to a
missing
Changes by Martin Morrison :
Added file: http://bugs.python.org/file35984/shlex.2.7.patch
___
Python tracker
<http://bugs.python.org/issue21999>
___
___
Python-bugs-list m
Martin Panter added the comment:
I experimented with various redirections to /dev/null, files, and other
terminal windows on Linux. Current behaviour I am seeing seems to be something
like this:
* Prefers prompting to stderr if both stdout and stderr are terminals
* Prefers prompting to
Changes by Martin Panter :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue1152248>
___
___
Python-bugs-list mailing list
Unsubscribe:
Martin Panter added the comment:
For Posix (dunno about Windows), calling terminate or kill at the OS level
after a poll or wait has already succeeded is a bad idea, because the PID may
have been recycled. It is essentially operating on a released resource, similar
to calling “os.close” on a
Changes by Martin Panter :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue22021>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Martin Matusiak:
bits shared by the stringobject and unicodeobject implementations (and
possibly other modules, in a not too distant future).
"stringobject" should be "bytesobject"
--
components: Interpreter Core
files: fix_typo_stringlib.
Changes by Martin Matusiak :
--
nosy: +benjamin.peterson
___
Python tracker
<http://bugs.python.org/issue22036>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Martin Panter :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue1025395>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Martin Matusiak:
The csv module has an exception message with bad grammar:
- delimiter" must be an 1-character string
"an" should be "a"
--
components: Library (Lib)
files: csv_grammar_fix.diff
keywords: patch
messages: 2240
Changes by Martin Panter :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue11429>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Martin Panter :
--
nosy: +vadmium
___
Python tracker
<http://bugs.python.org/issue15986>
___
___
Python-bugs-list mailing list
Unsubscribe:
Martin Panter added the comment:
This issue was linked from
<https://mail.python.org/pipermail/python-dev/2012-September/121781.html>. I
was looking for ways to pass read-only memory views into “ctypes” without
copying memory, and came across that thread. Assuming this “buf” attribute
1001 - 1100 of 9043 matches
Mail list logo
