New submission from A A :
Idle3 with python 3.7.3 on Debian Buster and XFCE.
Attempting to run the line 'print ("Hello World" * 8**8)' from either the Idle
shell window or Idle editor will cause Idle to hang and one CPU core runs
100%.(allowed it to run for several min
a added the comment:
Other quirks apparently caused by this bug:
msvcrt.getch() does not block and wait for a keypress in IDLE. Returns
immediately with b'\xff'.
Some of the suggested usage in the manual for sys.stdin does not work under
IDLE. E.g. sys.stdin.detach() doesn'
New submission from A :
When using elliptic curves in combination with the ssl module to wrap a socket,
the only curve the client accepts is prime256v1. Expected behavior is to accept
all curves that are on the default list and supported by the server.
We noticed the issue when connecting to
New submission from A-Shvedov :
Hello. Got an error with AFLplusplus, with crafted sample:
https://github.com/a-shvedov/res/blob/master/fuzzing/python/crashes/id:00%2Csig:11%2Csrc:009074%2Ctime:446401660%2Cexecs:16120011%2Cop:arith8%2Cpos:16%2Cval:-21
Compiled with: clang (version 6.0.0-3
Change by Jameel A. :
--
versions: +Python 3.10, Python 3.9
___
Python tracker
<https://bugs.python.org/issue38364>
___
___
Python-bugs-list mailing list
Unsub
New submission from Bithin A :
In the documentation 'HOWTO Fetch Internet Resources Using urllib2' there is a
correction under the heading 'Basic Authentication'
In the line 'The header looks like : ``Www-authenticate: SCHEME
realm="REALM"``. ' the word
New submission from Bithin A :
I am getting an Django error when I was trying to review a patch. This error
has occurred in the site as the DEBUG mode in the Django settings file is set
to True. It is a security issue and should be set to false. I am attaching the
screen shot of the error
Bithin A added the comment:
The bugs.python.org/review is a running application and it is very bad to see
debug error messages.
--
___
Python tracker
<http://bugs.python.org/issue13
A. Skrobov added the comment:
Joannah, I see that under #25314, the docs were updated to match the
implementation:
https://github.com/python/cpython/commit/b4912b8ed367e540ee060fe912f841cc764fd293
On the other hand, the discussion here (from 2015) and on #25314 (from 2016)
includes
Anj-A <2017...@gmail.com> added the comment:
Hi all, I'm a newcomer interested in doing a small fix. Wondering if anyone's
working on this at the moment?
------
nosy: +Anj-A
___
Python tracker
<https://bugs.py
Anj-A <2017...@gmail.com> added the comment:
Hey, I'm not exactly clear what the required fix is here and would appreciate
some guidance, is it in the documentation or in the way the error is handled?
--
___
Python tracker
<https://b
Change by Anj-A <2017...@gmail.com>:
--
keywords: +patch
pull_requests: +16560
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/17047
___
Python tracker
<https://bugs.python.or
Anj-A <2017...@gmail.com> added the comment:
Hey, I've done the change and opened a pull request for it (I'm working with
Ben and I've let him know)
--
nosy: +Anj-A
___
Python tracker
<https://bu
Change by Anj-A <2017...@gmail.com>:
--
keywords: +patch
pull_requests: +16563
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/17047
___
Python tracker
<https://bugs.python.or
New submission from A wilson :
0.01 + 273.15 should equal 273.16 but in python 3.9.5 or earlier report as
273.159997.
--
messages: 399550
nosy: afw2alan
priority: normal
severity: normal
status: open
title: Floating point issue
type: behavior
versions: Python 3.9
A wilson added the comment:
Eric,
I was unaware of this document and its implementation in python.
where
0.01+0.15 = 0.16 but 0.01+273.15=273.159997
the latter which should be 273.16 which is triple point temperature of water in
Kelvin.
This floating point variance explains some
Anj-A <2017...@gmail.com> added the comment:
Hey, if there is no bug here, could we get this issue closed?
Alternatively, I'd be interested in doing the required change in
documentation/error type if that's seen to be the right solution.
Personally, I think returning False in
New submission from Patrick A. :
This URL doesn't exist anymore. If you click on this URL you have a 404 not
found.
https://www.dcl.hpi.uni-potsdam.de/home/loewis/table-3131.html
The website was changed and Dr. Martin v. Löwis is not hosted on the new site.
Regards
--
assignee:
New submission from Muthu A :
Tamil locale (TA_IN, TA_SL, TA_SG, TA_MY) is using outdated encoding of TSCII.
Tamil community is widely using UTF-8 encoding.
Further, the 'locale' standard library package in Python3 should be updated
with these strings.
Should the maintain
New submission from Bithin A :
In urllib/parse.py the collections module is imported twice which is against
the PEP8-- Style Guide for Python Code.
--
components: Library (Lib)
files: multiple_imports.patch
keywords: patch
messages: 153780
nosy: Bithin.A
priority: normal
severity
Changes by Bithin A :
--
type: -> enhancement
___
Python tracker
<http://bugs.python.org/issue14064>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Bithin A :
Removed file: http://bugs.python.org/file24577/multiple_imports.patch
___
Python tracker
<http://bugs.python.org/issue14064>
___
___
Python-bug
New submission from Paul A. :
Shouldn't configure be able to arrive at that without me adding manually?
Anyway, after the build finishes thing soon come crashing down; my stack trace
is at the end...
running build_scripts
creating build/scripts-2.7
copying and adjusting /usr/local/src/P
Changes by Paul A. :
--
type: -> crash
___
Python tracker
<http://bugs.python.org/issue14524>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.p
New submission from Paul A. :
I can't help thinking that configure should be able to figure out the need for
this -- Modules/termios.c won't compile without adding -D_TERMIOS_INCLUDED by
hand. This is far from new, all 2.5+ versions I've tried to compile are like
that o
New submission from Paul A. :
Perhaps I'm not interpreting something happening earlier, but `make test' here
only seems to run a short time but doesn't actually finish. It appears not to
be using any cpu, or waiting for input, so I'm not sure what's happening.
...
New submission from Paul A. :
I trying to build python using an external libffi package I have installed --
is there some trick in directing --with-system-ffi to the path where it's
located. I don't see clues in config.log or anywhere to help.
--
messages: 157776
nosy: pd
Paul A. added the comment:
On Sun, Apr 08, 2012 at 02:01:05AM +, R. David Murray wrote:
>
> R. David Murray added the comment:
>
> Is this a bug report about configure, or a bug report about a crash during
> compilation after you've adjusted the configure parame
Paul A. added the comment:
On Sun, Apr 08, 2012 at 02:06:46AM +, R. David Murray wrote:
>
> R. David Murray added the comment:
>
> Can you suggest a patch? As I said on the other issue I don't believe any
> core developers have access to hpux.
Sure, once I figure
Paul A. added the comment:
On Sun, Apr 08, 2012 at 02:13:39AM +, R. David Murray wrote:
>
> R. David Murray added the comment:
>
> Oh, wait, I see you are testing the security RC. Is this a new problem, or
> does it also occur with the previous released version of 2.6?
Paul A. added the comment:
On Sun, Apr 08, 2012 at 05:58:29AM +, Ross Lagerwall wrote:
>
> Ross Lagerwall added the comment:
>
> If it is in a non-standard location, try setting the environment variables:
>
> LDFLAGS linker flags, e.g. -L if you have libraries i
Paul A. added the comment:
On Sun, Apr 08, 2012 at 04:16:39PM +, R. David Murray wrote:
>
> R. David Murray added the comment:
>
> Can you clarify? In what sense has the 2.7.3 rc regressed?
Shouldn't have left that out -- I was referring to the crash in that
other
New submission from Paul A. :
The following stack trace happened towards the end of a Python-2.7.3rc2 build,
but I also get much the same results with 2.7.2; one difference I noticed was I
didn't think I needed to add -DHAVE_USR_INCLUDE_MALLOC_H there.
running build_scripts
creating
Paul A. added the comment:
Apparently my memory was faulty the other day... 2.7.2 does crash the same way
as Python-2.7.3rc2 on this box. I opened a new bug report for that, so will
close this one. I'll also sign up for core-mentorship as you suggest, and see
what I can do to
Paul A. added the comment:
Will close this -- I'll try to help improve configure as I can get time.
--
resolution: -> postponed
status: open -> closed
___
Python tracker
<http://bugs.python.
Paul A. added the comment:
Yes, I think my libffi setup is okay, but python apparently doesn't (according
to the deeper-down log files I didn't initially know about). The following is
a suspicious-looking snippet from
build/temp.hp-ux-B.11.31-ia64-2.7/libffi/config.log... I have t
Paul A. added the comment:
I'd be more than happy to use my own installation of libffi instead, but it
seems the --with-system-ffi configure flag doesn't work. I've also opened a
different bug for that.
--
___
Python
Paul A. added the comment:
While this is no solution by any means, I think it'd be better for the scenario
to be a fatal configure error. After all, if I say --with-system-ffi, it means
I really, really want want to use my own l
Paul A. added the comment:
Yes indeed, sorry for not answering that question the first time.
The trace is complete, and is from python... although most of it is really in
the shared lib rather than the executable.
--
___
Python tracker
<h
A. Skrobov added the comment:
To bump this year-old issue, I have delivered a talk at EuroPython 2017,
explaining what my patch does, how it does what it does, and why it's a good
thing to do.
You can watch my talk at https://www.youtube.com/watch?v=dyRDmcsTwhE&t
A. Skrobov added the comment:
@Serhiy: incredibly, this patch from 2.5 years ago required very minor changes
to apply to the latest master. Shows how ossified the parser is :-)
Now posted as https://github.com/python/cpython/pull/10995
A. Skrobov added the comment:
I've run pyperformance (0.7.0) with my updated patch, and posted results at the
PR page. They look encouraging enough.
--
___
Python tracker
<https://bugs.python.org/is
Change by Tz a :
--
nosy: +Tz a
___
Python tracker
<https://bugs.python.org/issue11776>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
New submission from A. Skrobov :
Under #26526, I had optimised the validation code in parser module to use the
actual parser DFAs, but my code considers only the token types in the input,
and doesn't distinguish between different NAMEs (e.g. different keywords).
The result is this:
P
A. Skrobov added the comment:
> The major problem with the parser module is that is unsynchronized with the
> actual parser
The parser module is "sort of" synchronised with the actual parser, in that it
uses the same _PyParser_Grammar; this doesn't mean they always beha
Change by A. Skrobov :
--
keywords: +patch
pull_requests: +12510
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue36440>
___
___
Py
New submission from A. Skrobov :
Seeing that the implicit resolution at #36256 was to keep the parser module in
place, may I suggest that the diagnostics it produces be improved, so that
instead of "Expected node type 305, got 11", it would raise "Expected
namedexpr_
A. Skrobov added the comment:
> Nothing was really "decided", just that meanwhile is better not to ship a
> broken parser module.
Totally true, but the issue is closed and resolved, meaning that no one will
ever look at it again.
--
__
A. Skrobov added the comment:
Is it intentional that the fix is not backported to 3.6 as well?
--
___
Python tracker
<https://bugs.python.org/issue36
A Kaptur added the comment:
Here is a suggestion for updated documentation in this section. I've added the
description of __pycache__, included a very short description of what a .pyc
file is, and moved the troubleshooting to the end of the section. I'm not sure
whether the descr
A Hettinger added the comment:
There was a request on the python-dev to check this on windows 8.
I confirm the same behavior.
Windows 8.1 Pro 64bit
Python 3.4.0 32bit (release)
Installed current user:
Does not show up in Add/Remove Programs
Installer correctly sees installation and can remove
Changes by A Hettinger :
Added file: http://bugs.python.org/file34623/Client.py
___
Python tracker
<http://bugs.python.org/issue20469>
___
___
Python-bugs-list mailin
Changes by A Hettinger :
Added file: http://bugs.python.org/file34624/Server.py
___
Python tracker
<http://bugs.python.org/issue20469>
___
___
Python-bugs-list mailin
Changes by A Hettinger :
Added file: http://bugs.python.org/file34625/cert.pem
___
Python tracker
<http://bugs.python.org/issue20469>
___
___
Python-bugs-list mailin
A Hettinger added the comment:
The specific thing I'm interested in is the custom extension
"1.3.6.1.4.43167.0.0", but all of the X509 data should be imported.
Client shows both the openssl and python outputs. I would expect anything the
ssl system doesn't explicitly know
A Kaptur added the comment:
This patch adds tests demonstrating broken behavior inspect.getsource and
inspect.getsourcelines of decorators containing lambda functions, and modifies
inspect.getsourcelines to behave correctly.
We use co_lnotab to extract line numbers on all objects with a code
A Kaptur added the comment:
v2 of the patch incorporating the comments at
http://bugs.python.org/review/21217/
--
Added file: http://bugs.python.org/file34882/issue21217-v2.patch
___
Python tracker
<http://bugs.python.org/issue21
A Kaptur added the comment:
v3 of patch, including misc/news update, docstring for function, and removing
class decorator tests, since it sounds like those are better handled in
http://bugs.python.org/issue1764286.
--
Added file: http://bugs.python.org/file34885/issue21217-v3.patch
New submission from A Kaptur:
pdb.set_trace() is overwriting the actual traceback when exiting with an error.
See minimal recreation here: https://gist.github.com/4079971
--
messages: 175630
nosy: akaptur
priority: normal
severity: normal
status: open
title: pdb.set_trace() clobbering
Paul A. added the comment:
On Sun, Nov 18, 2012 at 08:01:39PM +, Terry J. Reedy wrote:
> I should have added 'please try compiling 3.x to make sure it has the same
> problem' since configure might behave differently.
I'm fairly sure I did, that was quite a few mon
Paul A. added the comment:
I believe this problem has been gone since around 2.7.5, so can I close this
myself?
--
resolution: -> out of date
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
New submission from A Kaptur:
The symbol table's syntax error about unqualified exec is missing the word
"because".
>>> def foo():
... exec "a = 1"
... def bar():
... print a
...
File "", line 2
SyntaxError: unqualified exec is
New submission from A Kaptur:
One of the error messages for __build_class__ has an extra underscore in the
middle.
--
files: build_class_typo.patch
keywords: patch
messages: 224874
nosy: akaptur
priority: low
severity: normal
status: open
title: Error message for __build_class__
New submission from A. Libotean:
There are significant memory leaks when multiple insert statements are executed
with distinct values.
sqlite3 version is 2.6.0
The attached file contains two variants:
* one which uses string interpolation to build the query: this generates severe
leakeage
A. Libotean added the comment:
> I'm not sure that it's a leak because it doesn't depend on the number of
> queries nor the number of run of the test. It's maybe an internal sqlite
> cache.
You're right, the "leak"
A. Libotean added the comment:
> Can we close this issue then?
Yes, please. Sorry for the false alarm.
--
___
Python tracker
<http://bugs.python.org/issu
New submission from A. Libotean:
The StreamHandler implementation uses hardcoded Unix/Linux line separators.
This generates inconveniences when running on Windows as the file viewers
expect DOS line terminators.
I've attached a fix that will use os.linesep as the line terminator thus m
New submission from A. Libotean:
Current implementation of RotatingFileHandler ignores the encoding when
computing the entry byte length.
I've attached a modified version that will compute the entry lenght in bytes.
--
components: Library (Lib)
files: rotatingfilehandler.py
mes
A. Libotean added the comment:
Sure, will come back shortly with a patch.
--
___
Python tracker
<http://bugs.python.org/issue20137>
___
___
Python-bugs-list mailin
A. Libotean added the comment:
Let me write also a test for this and come back with a reply.
--
___
Python tracker
<http://bugs.python.org/issue20136>
___
___
New submission from A Hettinger:
I have crafted an ssl cert which contains a custom extension, when I check the
cert using OpenSSL on the commandline, I clearly see the extension, but when I
have the server try to pprint.pprint(s.getpeercert()), I do not see these
fields.
Overall, I think it
Changes by A Hettinger :
--
type: -> enhancement
___
Python tracker
<http://bugs.python.org/issue20469>
___
___
Python-bugs-list mailing list
Unsubscrib
A. Libotean added the comment:
You can go ahead and close this.
I ran some tests and concluded that indeed the IO system will take care of the
line separators.
Sorry to have wasted your time.
--
___
Python tracker
<http://bugs.python.
A. Libotean added the comment:
> Which encoding are you using, such that the difference in length between
> encoded and decoded messages is significant?
I agree right off the bat that the error in size is not significant. Only the
length of the last appended line is computed erroneously
Changes by A Welch :
--
type: -> behavior
___
Python tracker
<http://bugs.python.org/issue7135>
___
___
Python-bugs-list mailing list
Unsubscri
A Welch added the comment:
Thank you for your response and my apologies for posting this in the
incorrect support forum. I thought that this forum was for all the
various versions of Python.
--
___
Python tracker
<http://bugs.python.
A. Skrobov added the comment:
Oh btw, the comment in the beginning of Grammar/Grammar
> # Note: Changing the grammar specified in this file will most likely
> #require corresponding changes in the parser module
> #(../Modules/parsermodule.c).
is no longer true: a
A. Skrobov added the comment:
Thank you Fred for your review!
I don't have commit access myself; can anybody please commit it for me?
--
___
Python tracker
<http://bugs.python.org/is
Changes by A. Skrobov :
--
keywords: +patch
Added file: http://bugs.python.org/file43069/issue26526_16704_63395.diff
___
Python tracker
<http://bugs.python.org/issue26
A. Skrobov added the comment:
Now that #26526 landed (thanks to everybody involved!), I'm requesting a review
on an updated version of my patch, which addresses the excessive memory
consumption by the parser.
The description of my original patch still applies:
> The attached patch
A. Skrobov added the comment:
An arena might help reclaim the memory once the parsing is complete, but it
wouldn't reduce the peak memory consumption by the parser, and so it wouldn't
prevent a MemoryError when parsing a 35MB source on a PC with
A. Skrobov added the comment:
My current patch avoids the memory peak *and* doesn't add any memory
fragmentation on top of whatever is already there.
In other words, it makes the parser better in this one aspect, and it doesn't
make it worse in
A. Skrobov added the comment:
(Updating the issue title, to avoid confusion between two orthogonal concerns)
--
title: Fragmentation of the heap memory in the Python parser -> Excessive peak
memory consumption by the Python parser
___
Python trac
A. Skrobov added the comment:
Fixing whitespace in the patch, and including an update for the docs
--
Added file: http://bugs.python.org/file43664/patch
___
Python tracker
<http://bugs.python.org/issue26
Changes by A. Skrobov :
Added file: http://bugs.python.org/file43665/devguide_patch
___
Python tracker
<http://bugs.python.org/issue26415>
___
___
Python-bugs-list mailin
Changes by A Kaptur :
--
nosy: +akaptur
___
Python tracker
<http://bugs.python.org/issue25571>
___
___
Python-bugs-list mailing list
Unsubscribe:
A. Skrobov added the comment:
Thanks Xavier! Yes, this is the same DFA that's used by the main Python parser.
For some reason, parsermodule didn't previously reuse it, but instead did its
own thing.
Any volunteers to review the other patch for Python parser, at
http://bugs.
A. Skrobov added the comment:
Xavier, the big picture description of my patch is in
http://bugs.python.org/file43665/devguide_patch
The heap fragmentation was observed by Victor, not by myself.
Victor, could you please create a new ticket for your python_memleak.py
reproducer
A Kaptur added the comment:
It looks like there's a related bug in call_args around __ne__:
>>> m = Mock()
>>> m(1,2)
>>> m.call_args
call(1, 2)
>>> m.call_args == call(1,2)
True
>>> m.call_args != call(1,2)
True
Any reason not to define __ne
A Kaptur added the comment:
Here's a simple patch + test for the original bug. I'll file the __ne__
question separately.
--
keywords: +patch
stage: needs patch -> patch review
Added file: http://bugs.python.org/file40348/issue24857.patch
_
New submission from A Kaptur:
mock.call_args can be both equal to and not equal to another object:
>>> m = Mock()
>>> m(1,2)
>>> m.call_args
call(1, 2)
>>> m.call_args == call(1,2)
True
>>> m.call_args != call(1,2)
True
This appears to be a recen
New submission from A. Skrobov:
Python 2.7.3 (default, Dec 18 2014, 19:10:20)
[GCC 4.6.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from argparse import ArgumentParser
>>> parser = ArgumentPa
A. Skrobov added the comment:
Thank you for confirming that the mismatch between the documentation and the
behaviour is preserved in Python 3!
Adding it to the list of affected versions.
--
versions: +Python 3.5
___
Python tracker
<h
New submission from A. Skrobov:
I have a one-line module that assigns a tuple->int dictionary:
holo_table = {(0, 0, 0, 0, 0, 0, 1, 41, 61, 66, 89): 9, (0, 0, 0, 70, 88, 98,
103, 131, 147, 119, 93): 4, [35MB skipped], (932, 643, 499, 286, 326, 338, 279,
200, 280, 262, 115): 5}
When I try
A. Skrobov added the comment:
A practical note: if, instead of importing crash.py, I do a json.loads, with a
few extra transformations:
with open("crash.py") as f: holo_table={tuple(int(z) for z in k.split(', ')):v
for k,v in
json.loads(f.readlines()[0][13:].repl
A. Skrobov added the comment:
Mine is on Windows. I've now installed both 2.7.10 and 3.4.3 to reconfirm, and
it's still the same, on both of them, except that on 3.4.3 it crashes with a
MemoryError much faster (within a couple minutes).
--
components: +Windows
nosy: +
A. Skrobov added the comment:
My Python is 64-bit, but my computer only has 2GB physical RAM.
--
___
Python tracker
<http://bugs.python.org/issue26415>
___
___
A. Skrobov added the comment:
Yes, I understand that this is a matter of memory consumption, which is why I
submitted this ticket as "resource usage".
What I don't understand is, what could possibly require gigabytes of memory
A. Skrobov added the comment:
OK, I've now looked into it with a fresh build of 3.6 trunk on Linux x64.
Peak memory usage is about 3KB per node:
$ /usr/bin/time -v ./python -c 'import ast; ast.parse("0,"*100,
mode="eval")'
Command being timed: &q
A. Skrobov added the comment:
@Serhiy: if your build is 32-bit, then every node is half the size, as it
mostly consists of pointers.
The amount of heap fragmentation can also depend on gcc/glibc version.
--
___
Python tracker
<h
1 - 100 of 2560 matches
Mail list logo
