New submission from Martin gzl...@googlemail.com:
My build got broken by the change for issue 9981 in revision 86137. The problem
is it adds $(IntDir) to various places in the vcproj file, including the
command line arguments to make_buildinfo, and my svn checkout is under a dir
with a space
Martin gzl...@googlemail.com added the comment:
Thanks. Don't actually need to quote the whole path, but what you've landed
works for me.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10501
New submission from Martin gzl...@googlemail.com:
The build changes in r87093 broke me, as my py3k branch is under a dir with a
space in the name, and the OutDir path needs escaping in the makefiles. Various
extra quoting seems to be sufficient, though inelegant.
--
components: Build
Martin gzl...@googlemail.com added the comment:
Oh, and after building with this, I get:
$ svn st
? PC/python3dll.obj
So either that wants moving or svn:ignore needs updating.
--
___
Python tracker rep...@bugs.python.org
http
Martin gzl...@googlemail.com added the comment:
Removing the quotes rebreaks the case where tmppath contains a space.
Instead, either:
* Call subwcrev.exe directly without going through COMSPEC: switch 'system' to
'CreateProcess'.
* More quotes! Change `A .. B` to `A .. B` which when it hits
Martin gzl...@googlemail.com added the comment:
This bug only hits people who:
1) Have TortoiseSVN installed (buildbots won't, I don't)
2) ...on a path that needs quoting.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11034
Martin gzl...@googlemail.com added the comment:
My build is still affected by this, can you find some time to look at the
attached patch please?
Relevant bit of log is:
Performing Makefile project actions
Microsoft (R) Program Maintenance Utility Version 9.00.21022.08
Copyright (C) Microsoft
Martin gzl...@googlemail.com added the comment:
Eli, was just answering your question about why this didn't fail for other
people.
Try the attached patch to see if it fixes the problem for you.
--
keywords: +patch
Added file: http://bugs.python.org/file20571/issue11034.patch
Martin gzl...@googlemail.com added the comment:
...and this apparently came up on the mailinglist as well with Prasun providing
nearly exactly the same patch:
http://mail.python.org/pipermail/python-dev/2011-January/107599.html
--
___
Python
New submission from Martin gzl...@googlemail.com:
With the logging change to using weakrefs for handler cleanup done by the
follow-on patch in issue 6615 exceptions may now be thrown during module
teardown.
There are two distinct problem cases:
1) The new `_removeHandlerRef` function may run
Martin gzl...@googlemail.com added the comment:
This could be fixed in a similar way to was done for the shutdown function in
r51206 (which incidentally seems both unnecessary and incomplete - the function
runs atexit which precedes module teardown, but also uses the raiseExceptions
module
Martin gzl...@googlemail.com added the comment:
For the second case, just reverting the change to Handler.close may be best, I
don't see why the module should be keeping responsibility for flushing and
closing handlers it no longer has a strong reference to.
--
Added file: http
Martin gzl...@googlemail.com added the comment:
spiv wrote a script to repo the issue in the downstream ubuntu bug:
https://bugs.launchpad.net/python/+bug/615240
--
nosy: +gz
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9543
New submission from Martin gzl...@googlemail.com:
The change in response to bug 9324 breaks bzr on windows as we use
signal.SIGBREAK to listen for a ctrl+break keyboard press.
Although SIGBREAK is not documented as valid on:
http://msdn.microsoft.com/library/xdkz3x12
It does in fact work
Martin gzl...@googlemail.com added the comment:
Also, the test seems to set signal handlers and never unset them, which I've
also corrected.
--
keywords: +patch
Added file: http://bugs.python.org/file19076/sigbreak_windows_10003.patch
___
Python
Martin gzl...@googlemail.com added the comment:
Thanks for the quick resolution Brian, head now works as expected.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10003
New submission from Martin gzl...@googlemail.com:
Prior to being split up into a package, unittest had an extensible method of
trimming uninteresting, testing-framework related parts from tracebacks. As an
unintended side effect, this is no longer the case, only modules actually named
New submission from Martin famar...@gmail.com:
When the following is run:
s='the Los Angeles Symphony';
s.capitalize();
it displays 'The los angeles symphony'
instead of 'The Los Angeles Symphony'
the str.capitalize() should only deal with the first letter, not lower-case the
rest
Martin gzl...@googlemail.com added the comment:
This patch has been reviewed by both Andrew and myself, it would be nice if
someone made the time to land it. The test change is unlikely to break
anything, and hey, that's what buildbots are for.
--
nosy: +gz
Martin famar...@gmail.com added the comment:
Looks like python needs eof() or something for file objects, just like
any other languages.
Since read() is using the system call, that's the right behavior: read()
blocks until EOF, and returns whatever was buffered. EOF character is
consumed
Martin gzl...@googlemail.com added the comment:
Does Victor Stinner have a psychic link with Armin Rigo? :)
https://bitbucket.org/pypy/pypy/src/7f593e7877d4/pypy/module/_multibytecodec/app_multibytecodec.py
# My theory is that they are not widely used on CPython either, because
# I found two
Martin gzl...@googlemail.com added the comment:
New cjk_encreset.patch looks good to me.
As with issue 12100 this likely wasn't reported before because decoders are
robust against escape sequence oddities.
--
___
Python tracker rep
New submission from Martin gzl...@googlemail.com:
Currently when running Python on a non-OSX posix environment under either the C
locale, or with an invalid or missing locale, it's not possible to operate
using unicode filenames outside the ascii range. Using bytes works, as does
reading
Martin gzl...@googlemail.com added the comment:
I'm not sure why having a locale set to C or something invalid should be
considered a Python bug. You have to handle un-decodable filenames no
matter what you do, since things aren't always encoded in utf-8 on non-OSX
unix even when
Martin gzl...@googlemail.com added the comment:
It was already discussed: using a different encoding for filenames and for
other things is really not a good idea. The main problem is the interaction
with other programs.
Yes, for many programs, a change like this will mean they create
Martin gzl...@googlemail.com added the comment:
During 1 month, we had PYTHONFSENCODING environment variable. It was not a
good idea.
I strongly agree. There is no sense in having a separate configurable value,
anyone who would think about using a PYTHONFSENCODING should just change
Martin gzl...@googlemail.com added the comment:
Nope. The locale encoding is chosen using LC_ALL, LC_CTYPE or LANG
variable: use the first non-empty variable. LC_MESSAGES doesn't affect
the encoding. Example:
That's good to know, thanks. Only leaves the case where setlocale is called
Martin gzl...@googlemail.com added the comment:
I built random-2.patch on my windows xp box (updating the project and fixing
some compile errors in random.c required), and initialising crypto has a
noticeable impact on startup time. The numbers vary a fair bit naturally, two
representative
Martin gzl...@googlemail.com added the comment:
Has anyone had a chance to try this patch on Windows? Martin? I'm
hoping that it doesn't impose a startup cost in the default
no-randomization cost, and that any startup cost in the -R case is
acceptable.
Just tested as requested
New submission from Martin:
The fix from issue 14398 for 4GB inputs regressed the behaviour when
compressing an empty string. Going by issue 853061 the expectation is this
should work.
The problem was noticed when using the updated Python 2.7 package in Ubuntu
Raring caused test failures
Martin added the comment:
On trunk, both the compressor and the standalone function (which uses the
compressor) are affected. The easiest fix is rearranging the logic in function
shared between BZ2Compressor.compress and BZ2Compressor.flush so the exit on no
remaining input for the former
Martin added the comment:
On 2.7 only the compress() function is affected, and the fix is much simpler.
Just using BZ_FINISH when the input is less then 4GB is sufficient.
--
Added file: http://bugs.python.org/file28513/bz2_compress_empty_string_27.patch
Martin added the comment:
This looks like a downstream issue in a patch Debian is applying:
http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=nobug=703872
http://patch-tracker.debian.org/patch/series/view/python2.7/2.7.4~rc1-2/webbrowser.diff
--
nosy: +gz
New submission from Martin gzl...@googlemail.com:
The fix for issue 10326 landing on Python 2.7 trunk has interfered with a hack
I wrote in Bazaar to break the reference cycles the private
`unittest.TestCase._type_equality_funcs` member creates.
As the change to make pickling work is nearly
Changes by Martin gzl...@googlemail.com:
--
keywords: +patch
Added file: http://bugs.python.org/file22636/avoid_TestCase_refcycle.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12544
Martin gzl...@googlemail.com added the comment:
Michael: See attached patch, that should merge up to Python 3 without too much
pain as well.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12544
Changes by Martin gzl...@googlemail.com:
Removed file: http://bugs.python.org/file22636/avoid_TestCase_refcycle.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12544
Martin gzl...@googlemail.com added the comment:
...typo in the first patch, this one should be okay. But... already landed
without the testcase?
--
Added file: http://bugs.python.org/file22637/avoid_TestCase_refcycle.diff
___
Python tracker rep
Martin gzl...@googlemail.com added the comment:
Yes, this is still reproducible. For instance, by:
hg clone -b default 3.3 feature branch
cd feature branch/PCbuild
call build_env.bat
call build.bat
It seems python33.dll now does get created so it's less severe, but the
python3dll still
New submission from Martin:
Hello! My name is Martin, a member of Free Software in Comahue National
University of Neuquén, Argentina. We have detected an error in the compiler
for Python 2.7 using Ubuntu 12.04: I write the code, without realizing I
leave a comment with syntax error in that line
New submission from Martin:
Hello! My name is Martin, a member of Free Software in Comahue National
University of Neuquén, Argentina. We have detected an error in the compiler for
Python 2.7 using Ubuntu 12.04: I write the code, without realizing I leave a
comment with syntax error
Martin added the comment:
I have three shell windows open because everytime i run the code corrected, it
opens a new shell, I try to close them but there is one that keeps open, unless
I kill it by terminal (kill) I attach a photo of compiling the line of code,
closing leftover shell ... What
Martin added the comment:
Thank you very much for your help.
Specification of error :
In python 2.7.3 for Ubuntu 12.04 32-bit
It creates a program with the following line of code :
Python is a programming language That lets you work more quickly and integrate
your systems more effectively
New submission from Martin <martin.bend...@gmail.com>:
>>> x = {"x":123}.update({"abc":123})
>>> type(x)
--
messages: 306977
nosy: thedemz
priority: normal
severity: normal
status: open
title: Dict creation with update will result to
Martin <mdelij...@gmail.com> added the comment:
I used Python on other machines, I know how it's supposed to work. I'm using
Windows 7 and this problem happened with 2.7.14, 2.7.13 and 2.7.9. I didn't
bother trying all other versions because it looked like it didn't matter what
v
New submission from Martin <mdelij...@gmail.com>:
When I try to run a really simple script like:
def fun(a):
print a
return
I get this error:
Exception in Tkinter callback
Traceback (most recent call last):
File "C:\Python27\lib\lib-tk\Tkinter.py", line 1541, in __c
New submission from Martin <ma...@dtu.dk>:
difflib.SequenceMatcher fails to make a proper alignment between 2 sequences
with only 3 single letter changes. Its performance is completely off with a
similarity ratio of 0.16, in stead of the more accurate 0.99.
Here is a snippet to rep
Martin added the comment:
Our production system hit this issue using Python 3.6.7 once a few days ago, so
presumably the race is still possible with the applied patch, just less likely?
```
RuntimeError: dictionary changed size during iteration
at _decompose (/usr/lib/python3.6/enum.py:858
New submission from Martin :
I experience a problem with multiprocessing and print.
I tried to make a minimal working example, please see the attached file.
WITHOUT the offending print statement in the queue filler thread, everything
works:
- pytest experiments/mp_problem.py
- pytest
Martin added the comment:
python experiments/mp_problem.py also fails for:
- 3.8.3, 3.8.2, 3.8.1, 3.8.0
- 3.7.7
- 3.6.10
--
___
Python tracker
<https://bugs.python.org/issue41
Change by Martin :
--
keywords: +patch
pull_requests: +20993
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/21869
___
Python tracker
<https://bugs.python.org/issu
New submission from Martin :
Although multiprocessing.Process has a `daemon` parameter,
multiprocessing.dummy.Process doesn't.
As multiprocessing.dummy is meant to replicate the API of multiprocessing and
the daemon parameter is readily available in threading.Thread, it should also
Martin added the comment:
While I appreciate your suggestion, it does not help me much.
The problem that people usually have is that the output is scrambled. That is
not the problem I'm dealing with.
I'm experiencing a deadlock caused by the print statement which seems like a
python bug
Martin added the comment:
Thanks for the explanations. I think this issue can be closed then.
--
title: StackSummary.format fails if str(value) fails -> StackSummary.format
fails if repr(value) fails
___
Python tracker
<https://bugs.pyth
Martin added the comment:
Yes, I think it should at least be documented.
But then it practically says: "Do not use print in your library because it
might be used in a threading context" This sounds unacceptable to me.
It would be great to "just make it work".
> I
Martin added the comment:
Thanks for the pointer, @pitrou!
--
___
Python tracker
<https://bugs.python.org/issue41539>
___
___
Python-bugs-list mailing list
Unsub
Martin added the comment:
Yes, it is repr in FrameSummary.__init__.
--
___
Python tracker
<https://bugs.python.org/issue43656>
___
___
Python-bugs-list mailin
Martin added the comment:
I can't find any mention of this in the documentation:
https://docs.python.org/3/reference/datamodel.html#object.__repr__
https://docs.python.org/3/library/functions.html#repr
I think this should be mentioned somewhere
Martin added the comment:
I didn't know repr is supposed to always succeed. Does the documentation
mention this?
--
___
Python tracker
<https://bugs.python.org/issue43
New submission from Martin :
With `capture_locals=True`, `StackSummary.format` prints the local variables
for every frame:
https://github.com/python/cpython/blob/4827483f47906fecee6b5d9097df2a69a293a85c/Lib/traceback.py#L440
This will fail, however, if string conversion fails
Martin added the comment:
I have to correct myself: The conversion to string already happens during
construction, in `FrameSummary.__init__`:
https://github.com/python/cpython/blob/4827483f47906fecee6b5d9097df2a69a293a85c/Lib/traceback.py#L273
The issue remains as severe and the fix remains
Change by Martin :
--
keywords: +patch
pull_requests: +23812
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/25062
___
Python tracker
<https://bugs.python.org/issu
Martin added the comment:
> Even correctly raised code can raise exceptions such as MemoryError,
> RecursionError and KeybordInterrupt.
For me, this is an argument in favor of the change (although KeybordInterrupt
and probably a couple more should not be caught).
traceback i
Martin added the comment:
pdb uses vanilla repr as well:
https://github.com/python/cpython/blob/f3ab670fea75ebe177e3412a5ebe39263cd428e3/Lib/pdb.py#L1180
--
___
Python tracker
<https://bugs.python.org/issue39
Martin added the comment:
> As is true for most special methods, it is a bug for __repr__ methods to
> raise.
Is this codified anywhere? I only learned about that in this bug report.
--
nosy: +moi90
___
Python tracker
<https://bugs.p
Martin added the comment:
Thanks, Joe, this is a very good summary of all the problems.
Another idea to fix this could be an additional parameter "repr=repr" to
StackSummary.extract. This way, the default behavior is not changed, but the
user is allowed to supply their own repr
Martin added the comment:
> Can we determine if they came from an initialized object or from object in
> the middle of initialization?
That would be very nice because inside __init__ is the only place where we have
to deal with partly initialized objects. But I think Python does not p
Martin added the comment:
Thanks Joe!
> 1. The changes are sufficient to let the user make things work the way it is
> requested that they work and anyone who does not start using the new
> format_locals parameter will get the old behavior.
That was my goal :)
> 2. A side com
Martin added the comment:
Irit, would you be able to take a look at the patch?
---
I found another application scenario for the patch: In Numpy and Pandas, the
assert_* functions in testing have a __tracebackhide__ local that advises
pytest to hide the frame. With the patch in place, we
Martin added the comment:
Thanks for your definitive answer, this is what I was waiting for.
I understand and I totally agree that subclassing is the way to go to make
traceback more flexible.
Would you mind linking the other issues concerning the general improvement of
traceback
Change by Martin :
--
pull_requests: +27563
stage: resolved -> patch review
pull_request: https://github.com/python/cpython/pull/29299
___
Python tracker
<https://bugs.python.org/issu
Martin added the comment:
Once again a very good summary, thanks Joe!
> it would be quite useful if this function parameter was given not just the
> local variable values, but also the name of the local variable and maybe also
> the stack frame it is in
So this would be somet
Martin added the comment:
I improved the example in traceback.rst to illustrate how format_locals works.
--
___
Python tracker
<https://bugs.python.org/issue43
Martin added the comment:
Just to avoid misunderstandings: My pull request is not at all about silencing
exceptions. It is about customizing the output of the traceback module. (Just
like the introduction of capture_locals previously: #22936)
(-X capture_locals, on the other hand
Martin added the comment:
Could the participants of this issue please have a look at my pull request:
https://github.com/python/cpython/pull/29299
What do you like, what don't you like? Does it work for your use case?
--
___
Python tracker
Change by Martin :
--
nosy: +davin, pitrou
type: -> behavior
___
Python tracker
<https://bugs.python.org/issue41544>
___
___
Python-bugs-list mailing list
Un
Martin added the comment:
Could someone have a look at my pull request? I have trouble with the tests.
--
___
Python tracker
<https://bugs.python.org/issue41
Martin added the comment:
I see two scenarious discussed here:
Scenario 1 (Offline / Batch-Mode):
A system runs user-supplied jobs that may fail. In the case of an error, the
system shouldn't crash but rather store a maximally helpful message and carry
on with the next job. Most likely
Martin added the comment:
I submitted a pull request for the related issue43656:
https://github.com/python/cpython/pull/29299
It introduces a format_locals parameter that enables the customized formatting
of a FrameSummary.
This way, a user of traceback could provide a function
Martin added the comment:
Irit, I'm unsure about the wording. Something like ":meth:`__repr__` should
always succeed, even if errors prevent a full description of the object."? "...
even if the object is only partly initialized."?
Andrei, I think you can not simply omi
Martin added the comment:
In this pull request[1] I introduced a `format_locals` which can be provided to
customize the serialization of the local variables of each frame. This could be
used to filter out variables with certain names, for example. In this context,
you could use a certain
Martin Gfeller Martin Gfeller g...@comit.ch added
the comment:
Martin, we're running with this for years and with many extensions modules,
without an issue. What is 64-bit safe should be 32-bit safe, not only 31-bit
safe. But you're right, this is not a proof, and we
Martin Gfeller Martin Gfeller g...@comit.ch added
the comment:
Lukas, I'm afraid to admit you're right :-;.
Assuming that the Python code called under the not release the GIL
regime would not do anything that could be potentially blocking is
probably dangerous
New submission from Martin Budaj m.bu...@gmail.com:
The method Sniffer._guess_quote_and_delimiter() in the module csv.py contains a
bug in a regexp which checks for quotes around the last item of the line
(example: a,b,c,d\n).
the pattern
'(?Pdelim[^\w\n\'])(?Pspace ?)(?Pquote[\']).*?(?P
Martin Budaj m.bu...@gmail.com added the comment:
Units test and two patches for 2.7 are included.
p1.patch fixes testEnd case reported yesterday
After running unittest it seems that also other case is broken (testAl -- if
there is just one data item on the line, enclosed in quotes). Patch p2
Martin Budaj m.bu...@gmail.com added the comment:
I'm not sure about what the intended behavior for testAl should be, however I
think that the file should be recognized as having one column of data and no
delimiter (there is a test for this case in csv.py) and not raise an exception.
I attach
Martin Budaj m.bu...@gmail.com added the comment:
What do you mean by there is a test for this case in csv.py?
I meant test in regex on line 217 in python 2.7 and the following code (line
258ff):
# there is *no* delimiter, it's a single column of quoted data
delim = ''
skipinitialspace = 0
New submission from Martin Potthast martin.potth...@googlemail.com:
The title says it all; try the minimal example.
--
components: Library (Lib)
files: parser-fail.py
messages: 124506
nosy: Martin.Potthast
priority: normal
severity: normal
status: open
title: HTMLParser.unescape
Changes by Martin Potthast martin.potth...@googlemail.com:
--
title: HTMLParser.unescape() cannot handle HTML entities with incorrect syntax
(e.g. #hearts;) - HTMLParser.unescape() fails on HTML entities with incorrect
syntax (e.g. #hearts
Martin Potthast martin.potth...@googlemail.com added the comment:
I'd suggest to better verify the input and return such strings unchanged.
--
type: - behavior
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10759
Martin Potthast martin.potth...@googlemail.com added the comment:
Agreed. Here's a patch for HTMLParser. That was easy enough.
With regard to tests, there seems to be already one called
test_malformatted_charref in test_htmlparser.py. However, the test tests the
whole parser and not only
Martin Potthast martin.potth...@googlemail.com added the comment:
Why not simply remove the additional check in line 168 and leave the
responsibility to check the validity of its input to the unescape function (be
it explicitly or, like now, lazily). That way, the code changes are minimal
New submission from Georges Martin jrjsm...@gmail.com:
Both httplib.HTTPMessage and email.message.Message classes[1] implements
methods for RFC822 headers parsing. Unfortunately, they have different
implementations and they do not provide the same level of functionality.
One example
Georges Martin jrjsm...@gmail.com added the comment:
No problem. I thought important that the issue and a workaround were
documented somehow... :-)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11316
New submission from Martin Horcicka:
This patch makes os.environ.clear() to have the same effect as:
for name in os.environ.keys():
del os.environ[name]
I believe that most people expect the effects to be the same anyway.
The practical benefit is a simpler redefinition of the whole
New submission from Martin Horcicka:
Many people expect the match object from the re module to always be
true. They use it this way:
if regexp.match(string): do_something()
Some people do not expect it and use it differently:
if regexp.match(string) is not None: do_something()
Even
New submission from Martin Rinehart:
The tokenizer accepts '0x' as an integer zero. The documentation says:
hexinteger ::= 0x|Xhexdigit+
Stumbled on this testing a tokenizer I wrote in Python for another
language. Expected an Error on int( '0x', 16 ), but didn't get one
Martin Rinehart added the comment:
re 0x == 0
Thanks!
Added file: http://bugs.python.org/file9268/unnamed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1679
__re 0x == 0brbrThanks!br
Martin Wilck added the comment:
The recipe in its current form doesn't work with urllib2 in python 2.5
The reason it fails is that the HTTPConnection.request() method isn't
passed the request itself (with the proxy host and port info). No easy
solution to be seen.
--
nosy: +mwilck
New submission from Martin Geisler [EMAIL PROTECTED]:
The traceback message given when trying to hash unhashable objects has
changed from Python 2.5 to 2.6:
Python 2.5.2a0 (r251:54863, Feb 10 2008, 01:31:28)
hash([])
Traceback (most recent call last):
File stdin, line 1, in module
TypeError
1 - 100 of 9608 matches
Mail list logo
