New submission from Dima Tisnek:
Let's fetch extended error codes from SQLite, information contained is not
particularly interesting to the user, but may be invaluable in debugging!
http://www.sqlite.org/rescode.html
https://sqlite.org/c3ref/extended_result_codes.html
Changes by Ned Deily n...@acm.org:
--
nosy: -ned.deily
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24142
___
___
Python-bugs-list mailing list
Changes by Karl Richter krichter...@aol.de:
--
components: Build
nosy: krichter
priority: normal
severity: normal
status: open
title: Makefile in tarball don't provide make uninstall target
versions: Python 2.7
___
Python tracker
Mark Lawrence added the comment:
What if any harm can be done by applying the patch with Victor's work around?
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7267
___
Changes by Ned Deily n...@acm.org:
--
nosy: +georg.brandl
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24140
___
___
Python-bugs-list mailing
Ned Deily added the comment:
[Thanks for the headsup about the contributor agreement form, now reported as
https://github.com/python/pythondotorg/issues/747]
--
nosy: +ned.deily
___
Python tracker rep...@bugs.python.org
New submission from Ned Deily:
This has come up in the past (for example, Issue549764) but, AFAIK, no one has
shown much interest in pursuing such a feature by providing a patch. Note that
it would likely be very tricky to cover all the edge cases properly. As a
practical matter, one reason
Guido van Rossum added the comment:
I think it's fine. It collects all the keys and values and then calls
BUILD_MAP (a new opcode), rather than calling STORE_MAP for each key/value
pair. I think this is a reasonable strategy for compiling a dict display.
On Thu, May 7, 2015 at 11:40 AM, Joshua
Ethan Furman added the comment:
From Frank Woodall on python-ideas:
==
How to reproduce:
mkdir /tmp/path_test cd /tmp/path_test mkdir dir1 dir2 dir2/dir3 touch
dir1/file1 dir1/file2 dir2/file1 dir2/file2 dir2/dir3/file1
su
chmod 700 dir2/dir3/
chown root:root
Guido van Rossum added the comment:
I think you could help by (a) reviewing what's there, and (b) helping with
the implementation of __future__.
On Thu, May 7, 2015 at 1:16 PM, Yury Selivanov rep...@bugs.python.org
wrote:
Yury Selivanov added the comment:
You sure can! Take it, deploy it,
Changes by Ned Deily n...@acm.org:
--
nosy: +christian.heimes
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24111
___
___
Python-bugs-list mailing
Joshua Landau added the comment:
There is a change as part of this to make dict building more like list and set
building, which both have this behaviour.
The same changes have likely occurred before whenever BUILD_LIST and BUILD_SET
were introduced, and this behaviour seems particularly
Stefan Behnel added the comment:
I get a test failure in Cython's compatibility tests which seems to be
attributable to this change:
def sideeffect(x):
... L.append(x)
... return x
def unhashable(x):
... L.append(x)
... return [x]
L = []
Changes by Ethan Furman et...@stoneleaf.us:
--
nosy: +ethan.furman
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24120
___
___
Python-bugs-list
Changes by Ned Deily n...@acm.org:
--
priority: normal - low
stage: - needs patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24143
___
___
Geoff Shannon added the comment:
Okay, I just found another way to achieve the same effect of letting the _read
function ignore data but not inadvertantly close the stream. It relies on the
fact that terminals will ignore null bytes fed to them.
Now there are no code changes required, just
Yury Selivanov added the comment:
You sure can! Take it, deploy it, run the test suite, and then start writing
real code that uses it. When you find a problem, that's what needs help! :)
Thank you for this generic answer, Chris.
The reason I was asking is because issue #24017 depends on
Changes by Ned Deily n...@acm.org:
--
nosy: +ghaering
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24139
___
___
Python-bugs-list mailing list
Ned Deily added the comment:
Thanks for the report. This problem and solution was just reported recently in
Issue24111.
--
nosy: +ned.deily
resolution: - duplicate
stage: - resolved
status: open - closed
superseder: - Valgrind suppression file should be updated
Ned Deily added the comment:
[Note, this is in response to the opening of this issue by krichter; the
opening did not generate a message itself]
This has come up in the past (for example, Issue549764) but, AFAIK, no one has
shown much interest in pursuing such a feature by providing a patch.
Changes by Ned Deily n...@acm.org:
--
Removed message: http://bugs.python.org/msg242728
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24143
___
Yury Selivanov added the comment:
Third patch attached. Victor, it would be great if you can review it!
--
Added file: http://bugs.python.org/file39314/await_03.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24017
Changes by Ethan Furman et...@stoneleaf.us:
--
nosy: +ethan.furman
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24138
___
___
Python-bugs-list
Changes by Aaron Meurer asmeu...@gmail.com:
--
nosy: +Aaron.Meurer
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17697
___
___
Python-bugs-list
Berker Peksag added the comment:
23796_fix_with_tests.patch LGTM. I'll apply it this weekend. Thanks for the
patch, John.
--
stage: patch review - commit review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23796
Yury Selivanov added the comment:
Yury's patch mostly looks good to me, except:
Thanks!
* the check in contextlib should be against __cause__ rather than
__context__, and there should be a new test for this code handling path
Done. I've also added one test for correct handling of
Changes by Aaron Meurer asmeu...@gmail.com:
--
nosy: +Aaron.Meurer
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16482
___
___
Python-bugs-list
ssh added the comment:
Thanks for checking in the RFC. I had done that before I posted my
StackOverflow question, but should have mentioned it here for completeness.
I've addressed the comments.
--
Added file: http://bugs.python.org/file39315/mywork.patch
Jens Timmerman added the comment:
Wel, I can confirm that this is fixed in new libffi shipped with python now,
and the problem no longer occurs on 3.4.3 (only version I checked)
--
___
Python tracker rep...@bugs.python.org
Changes by Ma Lin wjss...@sohu.com:
Added file: http://bugs.python.org/file39319/forpy34.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24117
___
___
Changes by Ma Lin wjss...@sohu.com:
Added file: http://bugs.python.org/file39320/forpy35.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24117
___
___
Changes by Ma Lin wjss...@sohu.com:
Removed file: http://bugs.python.org/file39278/forpy3.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24117
___
Changes by Ma Lin wjss...@sohu.com:
Removed file: http://bugs.python.org/file39277/forpy27.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24117
___
Ma Lin added the comment:
I examined all Chinese codecs, here are the patches, please review them, feel
free to ask me your question.
Thanks to Hye-Shik, your framework is very easy to understand :)
--
Added file: http://bugs.python.org/file39318/forpy27.patch
Changes by Berker Peksag berker.pek...@gmail.com:
--
nosy: +berker.peksag
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23888
___
___
Ezio Melotti added the comment:
Do you have authoritative links that describe these standards?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24117
___
Berker Peksag added the comment:
A minor comment about the __future__ changes: 3.5.0a1 should probably be
3.5.0b1.
--
nosy: +berker.peksag
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22906
Chris Angelico added the comment:
The comment was general because I honestly had no idea what was needed still.
All I knew was that the patch seemed to work for me, all tests passing
(including the new one). Thanks for uploading the new patch; it compiles
happily, and I'm running tests now,
Ma Lin added the comment:
Good question.
GB2312:
I tested those programming languages one by one.
GBK/CP936/GB18030-2000:
I gathered data via Internet as much as I can, then compare them to Python3's
codecs. I check key points with authoritative source, and verify every appeared
conflicts.
R. David Murray added the comment:
It seems reasonable to provide as much error information as is available, one
way or another. Would you like to work on a patch?
--
nosy: +r.david.murray
versions: -Python 3.5
___
Python tracker
Yury Selivanov added the comment:
Hi,
Please find attached an updated patch.
Summary of changes:
1. Most of feedback from Nick Coghlan and Serhiy Storchaka is applied;
2. Changes in difflib.py were reverted (unless we add the __future__ import
there right now there is no need to fix it);
New submission from Devin Jeanpierre:
Maybe the functions should be split up into those you shouldn't need to call
directly, and those you should? I find it unlikely that you're supposed to use
codecs.encode(..., 'hex') and codecs.decode(..., 'hex') instead of binascii
(the only other thing,
R. David Murray added the comment:
No, actually, using codecs would be the most straightforward way to achieve
portability. The usual way to get hex in python2 was encode('hex'), which uses
the codec. But if you want to use hexlify instead, I don't see any reason not
to. There's no reason
Changes by Yury Selivanov yseliva...@gmail.com:
--
assignee: - yselivanov
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22906
___
___
Nick Coghlan added the comment:
This could likely stand to be clarified in the language reference, though
(as well as in the 3.5 porting notes)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2292
Nick Coghlan added the comment:
Yury's patch mostly looks good to me, except:
* the check in contextlib should be against __cause__ rather than
__context__, and there should be a new test for this code handling path
* there should be a new test for the __future__ flag itself (independently
of
Guido van Rossum added the comment:
Or, if it's perfect (or good enough :-), just check it in.
On Thu, May 7, 2015 at 1:18 PM, Guido van Rossum rep...@bugs.python.org
wrote:
Guido van Rossum added the comment:
I think you could help by (a) reviewing what's there, and (b) helping with
the
Changes by Brian Curtin br...@python.org:
--
nosy: -brian.curtin
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2122
___
___
Python-bugs-list
New submission from Florian Höch:
If a ParsingError occurs while reading a config file, the multi-line values
collected while reading will never be joined because the error is raised before
this can happen. This leads to very unexpected results, e.g. consider the
following config.ini:
Florian Höch added the comment:
[Btw, you might want to fix the contributor agreement form - I can't sign it
because it shows no text, so I don't know what I'm supposed to enter in the
fields (Firefox 37.0.2)]
--
___
Python tracker
Changes by Michael Ensslin michael.enss...@googlemail.com:
--
title: Python 3 ships an outdated valgrind suppresison file. - Python 3 ships
an outdated valgrind suppressison file.
___
Python tracker rep...@bugs.python.org
Mark Lawrence added the comment:
I think we should be properly handling errors. If people agree I'll provide a
new patch to cover code and doc changes, but I've no idea how to provide any
form of unit test for the change.
--
nosy: +BreamoreBoy, paul.moore, steve.dower, zach.ware
Michael Ensslin added the comment:
Note:
Additionally replacing
PyObject_Free - _PyObject_Free
and
PyObject_Realloc - _PyObject_Realloc
appears to fix the issue.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24141
New submission from Michael Ensslin:
The suppression file that is shipped in Misc/valgrind-python.supp of the
CPython 3(.x) source tarball only works with CPython 2.
This was tested on Debian Sid, with Python 3.4.3 and Python 2.7.9, both
presumably not compiled with --valgrind.
Since Debian
Changes by Serhiy Storchaka storch...@gmail.com:
--
nosy: +christian.heimes, haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24141
___
___
Changes by R. David Murray rdmur...@bitdance.com:
--
nosy: +lukasz.langa
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24142
___
___
Demian Brecht added the comment:
I left a small comment around indentation in Rietveld.
Also, for the sake of completeness (and for others taking part in this
review/commit), I dug through the relevant RFCs and none of them seem to define
time as having sub-section resolution.
--
New submission from vyktor:
When using pdb -m pdb test.py and entering:
(Pdb) b A.f
Breakpoint 1 at d:\tmp\stack\test.py:8
(Pdb) commands 2
(com) disable 2
(com) until 13
(com) end
Until doesn't seem to have any effect. When statement is executed manually,
everything works as expected
Jens Timmerman added the comment:
yep, newer versions of python with newer libffi do not longer have this issue,
confirmed with python 3.4.3
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4130
59 matches
Mail list logo