Ned Deily added the comment:
Andrew, this is clearly a new feature, not a bug. What is your rationale for
adding it to the maintenance branches (2.7, 3.2, and 3.3)?
--
nosy: +ned.deily
___
Python tracker rep...@bugs.python.org
Changes by Georg Brandl ge...@python.org:
--
nosy: +georg.brandl
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1207589
___
___
Python-bugs-list
Hynek Schlawack added the comment:
Éric, what’s your take on this approach (not code)? We have time enough till
3.4 but it seems this doesn't really move forward. Any thoughts how to get this
moving? Unfortunately I'm not invested enough in this to make a educated
decision.
--
Changes by Hynek Schlawack h...@ox.cx:
--
nosy: +hynek
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16381
___
___
Python-bugs-list mailing list
Changes by Hynek Schlawack h...@ox.cx:
--
versions: +Python 3.4
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14794
___
___
Python-bugs-list
Hynek Schlawack added the comment:
Fun fact, on 2.7 3.2 I get infinite loops @ 100% CPU. 3.3 default crash.
Unless someone yells, I'll polish this up and commit next week.
--
stage: - commit review
versions: +Python 3.4 -Python 3.1
___
Python
Hynek Schlawack added the comment:
Any reason why this is still open?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15148
___
___
Changes by Hynek Schlawack h...@ox.cx:
--
nosy: -hynek
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15104
___
___
Python-bugs-list mailing list
Changes by Hynek Schlawack h...@ox.cx:
--
nosy: -hynek
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15490
___
___
Python-bugs-list mailing list
Changes by Hynek Schlawack h...@ox.cx:
--
nosy: +orsenthil
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16099
___
___
Python-bugs-list mailing
Fergus Noble added the comment:
Digging up an old issue but I am also interested in seeing this enhancement.
Specifically to represent GPS time which is (currently) 16 seconds ahead of UTC.
--
nosy: +Fergus.Noble
___
Python tracker
Christian Theune added the comment:
I pondered PyErr_NoMemory as well. However, I noticed not all locations in
Python use PyErr_NoMemory to raise a MemoryError, and I'm also afraid that
external libraries will have the same problem.
Can you explain why you consider PyErr_NoMemory to be the
Serhiy Storchaka added the comment:
This should be an issue on 64-bit too.
slice(0,1,None).indices(sys.maxsize+1)
--
nosy: +serhiy.storchaka
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14794
Jan Duzinkiewicz added the comment:
I agree this is unclear - If Match object always have a boolean value of True,
it actually prevents me from using simple if statement - what's the point of
if True: statement? - so the remark that matching functions do not always
return match objects has
Łukasz Langa added the comment:
Well, the inline comment syntax was awkward to start with, that's why inline
comments are now disabled by default since Python 3.2.
For a more predictable situation with regard to comment handling, consider
using the configparser 3.2+ backport for Python 2.6
Jan Duzinkiewicz added the comment:
I've referenced the kb article in the docs. Please let me know if the fix is ok
- maybe the whole registry change process should be included in the docs
directly?
--
keywords: +patch
nosy: +dhgmgn
Added file:
Serhiy Storchaka added the comment:
Patch updated. Added tests for onerror.
--
Added file: http://bugs.python.org/file27840/shutil_rmtree_3.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15872
Serhiy Storchaka added the comment:
Here are backported tests for 3.2 (they are passed).
--
Added file: http://bugs.python.org/file27841/shutil_rmtree_tests-3.2.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15872
Andrew Svetlov added the comment:
I thought it's desirable feature which cannot produce backward incompatibility
problems.
Can revert commits for 2.7-3.3 if needed.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1207589
Jan Duzinkiewicz added the comment:
The latest docs have a crossrefence at the end of the section:
http://docs.python.org/3/reference/simple_stmts.html#grammar-token-yield_stmt
I copied the reference to 2.7 docs
--
keywords: +patch
nosy: +dhgmgn
Added file:
Todd Rovito added the comment:
Ned,
I respectfully disagree that this is not a new feature. IDLE could always
copy/cut/paste from the edit menu and it had a right click menu. All this patch
does is add options to right click menu and call the same functions as the edit
menu does. I could
R. David Murray added the comment:
Doesn't look like it.
--
stage: - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15148
___
R. David Murray added the comment:
The reason for our no new features policy is that if a program works with
version x.y, it should work for all x versions (modulo failing on an earlier
version because of a bug...and conversely if it works on x.y, it should work on
all later versions of x,
New submission from Albert Ferras:
I normally use dictionaries for configuration purposes in python, but there's a
problem where I have a dictionary with many key-values and one of the keys is
repeated.
For example:
lives_in = { 'lion': ['Africa', 'America],
'parrot': ['Europe'],
New submission from Jan Duzinkiewicz:
quote from http://docs.python.org/3/library/imp.html#imp.find_module:
...on some systems some other places are looked in as well (on Windows, it
looks in the registry which may point to a specific file).
I actually didn't know the registry key is listed
Stefan Krah added the comment:
Ramchandra Apte rep...@bugs.python.org wrote:
Almost nobody knows that when using tkinter, code in .Tk.py is executed.
(readprofile is not even documented!)
While in your example, it is quite easy to see that it will run .bashrc
The point of the example is that
Benjamin Peterson added the comment:
Where it is now means raising a MemoryError in Python code will cause the fatal
error. I don't know if that's a good idea.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16381
Changes by Brett Cannon br...@python.org:
--
nosy: +brett.cannon
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16384
___
___
Python-bugs-list
Changes by Brett Cannon br...@python.org:
--
type: crash - behavior
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16384
___
___
Python-bugs-list
New submission from Stefan Krah:
test_cmd_line_script is failing on multiple buildbots:
==
FAIL: test_non_utf8 (test.test_cmd_line_script.CmdLineTest)
--
Guido van Rossum added the comment:
There used to be some places in the C code that raise MemoryError to
indicate that some parameter indicating a desired result size is out
of range, i.e. before even trying to allocate anything. I can't
confirm any, but these should probably be replaced with
Changes by Mark Dickinson dicki...@gmail.com:
--
nosy: +mark.dickinson
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14794
___
___
Lukas Lueg added the comment:
I have to say this feels like spooky action at a distance.
Wouldnt it be less intrusive - while achieving the same result - to make
MemoryError uncatchable if the flag is set?
--
nosy: +ebfe
___
Python tracker
Roundup Robot added the comment:
New changeset 0b5f00ccf907 by Stefan Krah in branch '3.3':
Issue #16145: Support legacy strings in the _csv module.
http://hg.python.org/cpython/rev/0b5f00ccf907
--
nosy: +python-dev
___
Python tracker
Christian Heimes added the comment:
MemoryError can be raised under two different circumstances that should be
handled differently. Either the program tries to allocate a rather large chunk
of memory for e.g. a string with a couple of hundred KB and more. Or Python
can't malloc() even small
Stefan Krah added the comment:
Andrew and Serhiy, thanks for the reviews. Should be fixed now.
--
assignee: - skrah
resolution: - fixed
stage: needs patch - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
Guido van Rossum added the comment:
Well, you can fix that, right? Just add a new function with a better
signature and use that for one of the two scenarios.
(I think third scenario might be when realloc fails -- IIRC it
doesn't guarantee that the original pointer is still valid either?)
Terry J. Reedy added the comment:
It it not a new library feature that anyone would use in other code. I have
been meaning to raise this issue on pydev to see what others think. There are
advantages to keeping the *human* interaction with IDLE consistent between
releases.
--
Ramchandra Apte added the comment:
This is an unavoidable behaviour of the hash tables (dictionaries)
I don't see much use cases of a warning.
--
nosy: +ramchandra.apte
title: evaluating dict with repeated keys gives no error/warnings - evaluating
dict with repeated keys gives no
Ramchandra Apte added the comment:
Retract earlier statement. I didn't read the comment fully.
--
title: evaluating dict with repeated keys gives no warnings - evaluating dict
with repeated keys gives no warnings/errors
___
Python tracker
Stefan Krah added the comment:
Some of the buildbots are failing with the new test:
==
FAIL: test_non_utf8 (test.test_cmd_line_script.CmdLineTest)
--
Traceback
Ramchandra Apte added the comment:
You should be using json for configuration purposes anyway.
This is low priority as only few programs use dictionaries with a gazillion
keys.
--
___
Python tracker rep...@bugs.python.org
Changes by Stefan Krah stefan-use...@bytereef.org:
--
resolution: - duplicate
stage: needs patch - committed/rejected
status: open - closed
superseder: - Python launcher does not support non ascii characters
___
Python tracker
Changes by Jesús Cea Avión j...@jcea.es:
--
nosy: +jcea
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16218
___
___
Python-bugs-list mailing list
Serhiy Storchaka added the comment:
Tests simplified. Thanks Hynek for review and advices.
--
Added file: http://bugs.python.org/file27844/shutil_rmtree_4.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15872
Changes by Serhiy Storchaka storch...@gmail.com:
Added file: http://bugs.python.org/file27845/shutil_rmtree_tests-3.2_2.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15872
___
Changes by Serhiy Storchaka storch...@gmail.com:
Removed file: http://bugs.python.org/file27840/shutil_rmtree_3.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15872
___
Changes by Serhiy Storchaka storch...@gmail.com:
Removed file: http://bugs.python.org/file27841/shutil_rmtree_tests-3.2.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15872
___
Lukas Lueg added the comment:
In any strategy only a heuristic could be used in order to decide wether or not
it's safe to raise MemoryError. How exactly is memory pressure expected for
x=[2]*200 but not for x=2*200 ?
I don't think a new function could ultimatly achieve it's goal. If
Albert Ferras added the comment:
I would use json, but it allows me to set list/strings, etc.. not python
objects like I'd want
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16385
___
Albert Ferras added the comment:
sorry: *it only allows me
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16385
___
___
Python-bugs-list mailing
Christian Heimes added the comment:
Of course it can be fixed. But it's going to be a long and tedious piece of
work. PyErr_NoMemory() is called 314 times. MemoryError is raised about 40
times in C code.
I'm not sure what your question about realloc() really is. Are you unsure how a
a
Albert Ferras added the comment:
also, it creates confusion when this happens
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16385
___
___
Jesús Cea Avión added the comment:
Reopening bug.
Quite a few buildbots are failing with this patch. Please, commit a new version
or revert.
--
resolution: fixed -
stage: committed/rejected - commit review
status: closed - open
___
Python tracker
R. David Murray added the comment:
It is a nice suggestion, but it is also probably a non-trivial change to the
parser. If you want to try coming up with a patch we would consider it, but I
suspect there is a limit to how much complexity we'd be willing to add to the
parser code for this.
Andrew Svetlov added the comment:
I see. Sorry, my fault.
Give me weekend to figure out why it fails.
Thanks.
--
assignee: - asvetlov
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16218
Changes by Brian Curtin br...@python.org:
--
nosy: -brian.curtin
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16218
___
___
Python-bugs-list
Christian Heimes added the comment:
We can create some kind of heuristic when the memory error handler knows the
size of the new block and the size difference on realloc(). It could be an
application specific threshold, too.
--
___
Python tracker
Lukas Lueg added the comment:
The heuristic basically has to decide if memory pressure is so high that it's
not save to return to the interpreter. Even if there is a chosen value (e.g.
failed allocation attempts below 1mb are considered fatal), there can always be
another OS-thread in the
Lukas Lueg added the comment:
This could be avoided by
lives_in_init = (('lion': ['Africa', 'America']), ('lion': ['Europe']))
lives_in = {}
for k, v in lives_in_init:
assert k not in lives_in
lives_in[k] = v
del lives_in_init
Which is fast enough if executed only during
Benjamin Peterson added the comment:
An error is out of the question for compatibility reasons. I think the idea for
a warning should be brought up on the python-ideas list. Silently rejecting
duplicates has a lot of precedent, though. For example, set literals and the
dict constructor:
Stefan Krah added the comment:
One of 13ebaa36d87d, 9f696742dbda or 6903f5214e99 causes test failures in
test_pep277:
==
FAIL: test_failures (test.test_pep277.UnicodeFileTests)
Stefan Krah added the comment:
Additionally, some of the changes cause a failure in test_subprocess:
==
ERROR: test_no_leaking (test.test_subprocess.ProcessTestCase)
Roger Serwy added the comment:
In a strict sense, the patch does break backward compatibility for third-party
IDLE extensions that modify the rmenu_specs contents. It is not a private
value since it lacks an initial underscore in its name. But given how
undocumented IDLE is, especially its
R. David Murray added the comment:
Ah. Well, we prefer to err on the side of strictness for backward
compatibility, so I think we should treat this as an enhancement, then.
--
___
Python tracker rep...@bugs.python.org
New submission from Calvin Owens:
Urllib encodes as: User-agent
The correct form is: User-Agent
This is quite important, as it makes this library totally unusable for scraping
moronic websites which require a recognized User-Agent string to work
correctly, of which there are many.
--
Changes by R. David Murray rdmur...@bitdance.com:
--
resolution: - duplicate
stage: - committed/rejected
status: open - closed
superseder: - urllib/httplib header capitalization
___
Python tracker rep...@bugs.python.org
Roundup Robot added the comment:
New changeset 969069d464bc by Stefan Krah in branch '3.3':
Issue #15814: Use hash function that is compatible with the equality
http://hg.python.org/cpython/rev/969069d464bc
--
___
Python tracker
Roundup Robot added the comment:
New changeset 969069d464bc by Stefan Krah in branch '3.3':
Issue #15814: Use hash function that is compatible with the equality
http://hg.python.org/cpython/rev/969069d464bc
--
___
Python tracker
Ned Deily added the comment:
I think it is clear that this is an enhancement. So then the question is: is
there a good reason to make an exception here to the no new features in
maintenance releases policy? David mentioned some considerations. I would add
testing and documentation. Testing
Changes by Stefan Krah stefan-use...@bytereef.org:
--
resolution: - fixed
stage: needs patch - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15814
Mark Dickinson added the comment:
For 2.7, I don't see any problem with raising OverflowError for a length that's
sys.maxsize, since it's hard to have sequences larger than that anyway.
For 3.x, I'd also see this behaviour as reasonable, and not a bug. If it's
raising OverflowError for
Mark Dickinson added the comment:
If it's raising OverflowError for lengths *smaller* than sys.maxsize,
that's a bug.
Ah, reading Ned's comment, it looks like that's exactly what it's doing.
--
___
Python tracker rep...@bugs.python.org
Éric Araujo added the comment:
This is due to the fact on the 64 bit they split lib and lib64 directories.
This depends on the specific multiarch implementation. Debian 64-bit only has
/usr/lib for instance.
I had a look at the patch but did not understand what it does.
--
nosy:
Changes by Jesús Cea Avión j...@jcea.es:
--
nosy: +jcea
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16385
___
___
Python-bugs-list mailing list
Calvin Owens added the comment:
2275 hasn't been touched for almost 2 years.
If there was a fix in v3.3, it ought to be backported. But it doesn't look like
they ever came up with one.
--
___
Python tracker rep...@bugs.python.org
Antonio Cavallo added the comment:
Hi,
the patch it is really simple, it adds the @LIB@ and @ARCH@ variables to the
configure machinery.
If you look into the Makefile.pre.in:
INCLUDEDIR=¬@includedir@
CONFINCLUDEDIR=¬$(exec_prefix)/include
SCRIPTDIR=¬…$(prefix)/lib
This hardcodes lib that
Serhiy Storchaka added the comment:
I was not able to reproduce this error, I got other errors. The issue not in
Python interpreter, the test is broken. Here is a patch that might solve the
issue on some platforms (need to test on Windows).
I guess failing of all command line tests when the
New submission from Philip Jenvey:
#9396 replaced a few caches in the stdlib w/ lru_cache, this made the mako_v2
benchmark on Python 3 almost 3x slower than 2.7
The benchmark results are good now that Mako was changed to cache the re
itself, but the problem still stands that lru_cache seems
Paul Upchurch added the comment:
For the concept of reasonable, it should be noted that this behaviour will
affect code that works with reasonably sized sequences despite the largeness of
the parameter.
Consider an extremely large array. To work with such an array, one would
typically break
Serhiy Storchaka added the comment:
I think the issue is than slice constructor accepts integer out of Py_ssize_t
range. And more, it accepts any objects, not only integers or None.
slice(3.4, 'a', {})
slice(3.4, 'a', {})
May be we should disallow creating of such doubtful slices and raise
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
keywords: +3.3regression
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16389
___
Antoine Pitrou added the comment:
I'm gonna point people to the discussion about the -s flag of the Python
interpreter (added as part of PEP 370), since the issue is conceptually
identical:
http://mail.python.org/pipermail/python-dev/2008-January/076130.html
Adding Christian to the discussion
Changes by Antoine Pitrou pit...@free.fr:
--
stage: - needs patch
versions: +Python 3.4
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16389
___
New submission from Brett Cannon:
The Mako developers discovered that under Python 3.3 their library under the
mako_v2 benchmark went from 2.95x slower than Python 2.7 to 1.25x slower by
simply avoiding an re compilation:
Philip Jenvey added the comment:
Sorry Brett, beat you to it w/ #16389 =P
--
resolution: - duplicate
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16390
___
Christian Heimes added the comment:
It's gonna take a while to read this ticket ...
Some comments:
The code in site.py already does some checks, for example getuid() ==
geteuid(). System code and code that is run with administrator privileges shall
be run with -Es to prevent code injection.
Mark Dickinson added the comment:
Paul: I think you make good arguments that this should be fixed for 3.4. I do
however think that for versions earlier than 3.4 this 'fix' would be bordering
on a new feature; it's also likely to require significant new code and tests,
and so I'd be wary of
Mark Dickinson added the comment:
I'll look at creating a patch for 3.4
--
assignee: - mark.dickinson
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14794
___
Antoine Pitrou added the comment:
lru_cache() seems to use a complicated make_key() function, which is invoked on
each cache hit. The LRU logic is probably on the slow side too, compared to a
hand-coded logic which would favour lookup cost over insertion / eviction cost.
--
nosy:
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16353
___
___
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16255
___
___
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
type: - enhancement
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16354
___
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti, ghaering
stage: - needs patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16379
___
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
stage: - patch review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16382
___
Changes by Georg Brandl ge...@python.org:
--
resolution: - works for me
status: open - pending
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16354
___
Stefan Krah added the comment:
Serhiy, your original example from msg173373 still fails on
FreeBSD:
$ name=$(printf \xff)
$ echo print('Hello, world') $name
$ ./python $name
UnicodeEncodeError: 'ascii' codec can't encode character '\xff' in position 0:
ordinal not in range(128)
[41257 refs]
Changes by Vinay Sajip vinay_sa...@yahoo.co.uk:
--
nosy: -vinay.sajip
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16218
___
___
Jim Pattee added the comment:
The problem is not file permissions nor the install. I did some further testing.
The problem actually occurs with the library calls at lines 23 and 25. I
changed these lines to eliminate the library call by just hard coding the file
path.
Change from:
line 23:
R. David Murray added the comment:
Well, I run linux, not Windows. I haven't even looked at your code, frankly,
since it is a zip file and includes third party stuff. Maybe a windows dev
will find time to look at it.
--
___
Python tracker
1 - 100 of 143 matches
Mail list logo
