Changes by Steve Dower steve.do...@microsoft.com:
--
stage: needs patch - resolved
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24181
___
___
Mark Dickinson added the comment:
[Tim]
I suspect, but have not proved, that 1. - 2.**-53 is the only
random.random() result for which it's possible that double-rounding
can cause int(i * random.random()) == i.
I'm sure this is true. Any other random value is at most 1 - 2**-52, and we're
Steve Dower added the comment:
I don't see any crash in that log, though the importlib tests appeared to time
out.
Assert messages appear on the buildbots because they use debug builds and we
don't suppress them completely. Provided the tests keep running without
failure, it's fine.
To
Nick Coghlan added the comment:
I've attached the patch for my initial attempt at addressing this, but I think
my results show I went down completely the wrong path.
Specifically, the three new tests are failing:
FAIL: test_protocol_sslv23_not_available (test.test_ssl.ThreadedTests)
STINNER Victor added the comment:
My rationale is more general than datetime. But problems araise when
different API use different rounding methods.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23517
New submission from Jakub Wilk:
Misc/NEWS reads:
Fix free-after-use bug
It should be use-after-free, not free-after-use.
--
assignee: docs@python
components: Documentation
messages: 246310
nosy: docs@python, jwilk
priority: normal
severity: normal
status: open
title: Misc/NEWS:
Jacek Kołodziej added the comment:
In any case it is too late for 3.5.
Ok, next round of patches is based on default branch.
Jacek: If we used the ModuleType check, and somebody adds a module-level
constant (like logging.CRITICAL = 50), the test will automatically detect if
they forget
Antoine Pitrou added the comment:
There was probably an informal best effort ABI compatibility in 2.x that we
de facto dropped in 3.x. Otherwise, as Amaury points out, several
Py_TPFLAGS_HAVE_XXX flags would have no purpose.
--
nosy: +pitrou
___
STINNER Victor added the comment:
Le vendredi 3 juillet 2015, Alexander Belopolsky rep...@bugs.python.org a
écrit :
UNIX doesn't like timestamps in the future
I don't think this is a serious consideration. The problematic scenario
would be obtaining high-resolution timestamp (from say
Nick Coghlan added the comment:
The attached patch creates a TLSv1 context at test_ssl import time to see if
SSLv2 and SSLv3 peers are disallowed by default.
The test expectations for context options, SSLv23 and SSLv3 are then adjusted
accordingly.
The context options tests are also updated
Changes by Vedran Čačić ved...@gmail.com:
--
type: - behavior
versions: +Python 3.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24569
___
___
bee13oy added the comment:
I have just tested python 2.7.10 on Windows 7 x86 with the poc code, it will
also result in python crash.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24566
Antoine Pitrou added the comment:
Patch looks fine to me, assuming the tests don't fail, of course.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23965
___
Mark Dickinson added the comment:
IEEE 745
IEEE 754. Stupid fingers.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24567
___
___
Mark Dickinson added the comment:
Note that this affects other Random methods, too. There are several places in
the source where something of the form `int(i * random.random())` is used to
select an integer in the half-open range [0, i).
And a nitpick: it's a stretch to describe
Serge Anuchin added the comment:
Serge, you'll have to find some way to get more information on exactly what
is failing in order for this issue to make progress.
This exception occurred only once and I can't reproduce it.
Additional system specs in attachment.
--
Added file:
Antoine Pitrou added the comment:
As Christian, I suspect that SSLv3 is progressively getting disabled in distro
builds of OpenSSL.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23965
STINNER Victor added the comment:
There is a simple fix. If the result is invalid, drop it and generate a new
number. It should keep the distribution uniform.
Another fix is to only use integers. Why do we use float in choice by the
way?
--
___
New submission from Vedran Čačić:
It seems the consequences of PEP 0448 weren't really thought through. :-/ (And
BTW why isn't it in What's new in Python 3.5? I know there is a file with
full details, but I guess this really should be notable enough.)
{0:1, **{0:2}, 0:3, 0:4}
Do you know
Stefan Krah added the comment:
I've finally gotten hold of a gcc (5.1.0) that produces the unwanted code.
For a *different* test case, even the -O0 and -O2 results differ, since
with -O2 gcc uses mpfr (I think!) for constant folding, which produces
the correct result.
Using -mfpmath=sse seems
Stefan Krah added the comment:
Nick, this may be a misunderstanding, but you mentioned issues
that PEP 489 did not address yet. The only issue left for _decimal
is the speed issue. Sub-interpreter tests run fine even with the
existing module state API, *if* one is willing to take a speed hit.
Changes by Jacek Kołodziej kolodzi...@gmail.com:
Added file:
http://bugs.python.org/file39867/Issue23883_support_check__all__.v4.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23883
___
Changes by Jacek Kołodziej kolodzi...@gmail.com:
Added file: http://bugs.python.org/file39868/Issue23883_test_gettext.v3.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23883
___
Stefan Krah added the comment:
Any chance that another program (C-extension) had set the FPU control
word to an unusual value (24bit prec?).
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24546
bee13oy added the comment:
I didn't test that path, I just found this bug in python3.4.3 by fuzzing re
module, and tested Python 3.5.0b2 on windows 7 x86, It has the same problem.
--
___
Python tracker rep...@bugs.python.org
Adam Bartoš added the comment:
I've also run into this issue (see
https://mail.python.org/pipermail/python-list/2015-July/693496.html and the
following thread). I'm adding some small examples showing the behavior.
import asyncio
async def wait():
await asyncio.sleep(5)
loop =
Nick Coghlan added the comment:
Yeah, I belatedly realised I was overcomplicating things, and the test failures
really are just due the change in the context options to disallow SSLv3 peers
by default.
I have an idea for how to fix that, and I think it will make the handling of
the NO_SSLv2
Serhiy Storchaka added the comment:
Unfortunately can't reproduce the issue in 2.7.6, 2.7.10+, 3.4.0, 3.4.3+,
3.5.0b2+, 3.6.0a0 with Tcl/Tk 8.6.1.
The only output is:
Traceback (most recent call last):
File stdin, line 1, in module
File /usr/lib/python2.7/lib-tk/tkFileDialog.py, line 125,
Vedran Čačić added the comment:
Ah, so it was broken _only_ on 3.5. That should teach me not to uninstall Py3.x
as soon as Py3.x+1 comes out. :-)
Ok, thank you very much.
--
___
Python tracker rep...@bugs.python.org
Christian Heimes added the comment:
ping
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23239
___
___
Python-bugs-list mailing list
Unsubscribe:
Jakub Wilk added the comment:
Uh, use-after-use is not a bug either. :)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24568
___
___
Benjamin Peterson added the comment:
Python 3.3.5 (default, Aug 19 2014, 23:45:33)
[GCC 4.7.3] on linux
Type help, copyright, credits or license for more information.
{0:1, 0:2}
{0: 2}
Python 2.7.9 (default, Dec 24 2014, 23:52:11)
[GCC 4.8.3] on linux2
Type help, copyright, credits or
Serhiy Storchaka added the comment:
Not having Windows I can't reproduce the crash. Someone should test if the
patch for issue18684 fixes this issue and doesn't introduce other regressions.
--
___
Python tracker rep...@bugs.python.org
Serhiy Storchaka added the comment:
May be issue24566 has a reproducer, but not having Windows I can't test this.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18684
___
Matthew Havard added the comment:
Also, this typo is present in all versions anyway.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24540
___
Vedran Čačić added the comment:
Benjamin, you're my hero. :-)
I'm not really at home in C source... is it possible that you have also changed
{0:1, 0:2}
to be {0:2} (as opposed to {0:1} as it is now)? I'm completely fine with that
and find it more logical (and as I said in the previous
Matthew Havard added the comment:
It's in the actual code in the docstring:
https://hg.python.org/cpython/file/6905a7f8c7ac/Lib/json/__init__.py#l187
I'm really new to Mercurial, so I'm not quite sure how to link to the 2.7
version of the Mercurial repo, but here is the link to
Roundup Robot added the comment:
New changeset 5097c91cdc2d by Benjamin Peterson in branch '2.7':
'free-after-use' is not a bug :) (closes #24568)
https://hg.python.org/cpython/rev/5097c91cdc2d
--
nosy: +python-dev
resolution: - fixed
stage: - resolved
status: open - closed
Roundup Robot added the comment:
New changeset a4df0fe62b46 by Benjamin Peterson in branch '3.5':
set items in dict displays from left to right (closes #24569)
https://hg.python.org/cpython/rev/a4df0fe62b46
New changeset 75852d90c225 by Benjamin Peterson in branch 'default':
merge 3.5 (#24569)
Roundup Robot added the comment:
New changeset 803520a8db94 by Ned Deily in branch '2.7':
Issue #24540: fix typo in json.dumps docstring
https://hg.python.org/cpython/rev/803520a8db94
New changeset 0deca75537ec by Ned Deily in branch '3.4':
Issue #24540: fix typo in json.dumps docstring
Ned Deily added the comment:
Thanks, I overlooked the docstring. Now fixed.
--
resolution: - fixed
stage: - resolved
status: open - closed
title: Documentation about skipkeys parameter for json.dumps is incorrect -
Docstring for json.dumps skipkeys parameter is incorrect
versions:
Tim Peters added the comment:
Thanks, Mark! That's convincing. Just as a sanity check, I tried all ints in
1 through 4 billion (inclusive) against 1. - 2.**-52, with no failures.
Although that was with ad hoc Python code simulating various rounding methods
using scaled integers, so may
Changes by Raymond Hettinger raymond.hettin...@gmail.com:
--
assignee: rhettinger -
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24546
___
___
New submission from Alessandro Rosa:
I recently upgraded to Python 2.7.10 on my MacOSX Yosemite computer. I also
added a Python 3.4.3 installation. At the time I upgraded Tcl/Tk with ActiveTcl
8.5.18 as was suggested on the Python for MacOSX installation page.
At this point, Autocomplete and
Tomas Nordin added the comment:
I have not experienced this problem on windoze. The problem seem to have
appeared when upgrading my operating system from Debian wheezy to jessie, I
think with python going from 2.7.3 to 2.7.9. And I have a stomach feeling it is
related to the environment. I
Mark Shannon added the comment:
If type.coroutine is not the first and only decorator, then things may be even
worse.
Code objects are currently immutable.
This change would mean that a call to types.coroutine in one place in the code
would change the semantics of another piece of code in a
Mark Lawrence added the comment:
The reproducer from issue24566 consistently crashed the code. Applied the
patch from here and couldn't reproduce the problem. Then ran test_re for both
32 and 64 bit debug and release builds with no problems.
--
nosy: +BreamoreBoy
Mark Lawrence added the comment:
Fixed by the patch on issue18684, see also my comments there.
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24566
___
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24467
___
Matthew Havard added the comment:
Great! Glad to be of service.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24540
___
___
Python-bugs-list
Alexander Belopolsky added the comment:
I'll let others fight this battle. In my view, introducing floating point
timestamp method for datetime objects was a mistake. See issue #2736.
Specifically, I would like to invite Velko Ivanov to rethink his rant at
msg124197.
If anyone followed
Changes by Alexander Belopolsky alexander.belopol...@gmail.com:
--
nosy: -belopolsky
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23517
___
___
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24462
___
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24552
___
Ned Deily added the comment:
Thanks for the report. Taking a quick look at it, it appears that the problem
was introduced with the most recently releases of ActiveTcl on OS X, 8.5.18 and
8.6.4. The autocomplete popups seem to work fine with the previous OS X
release of ActiveTcl 8.5
Tim Peters added the comment:
I suppose the simplest fix would be to replace relevant instances of
int(random() * N)
with
min(int(random() * N), N-1)
That would be robust against many kinds of arithmetic quirks, and ensure that
platforms with and without such quirks would, if forced to the
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24456
___
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24457
___
Alessandro Rosa added the comment:
Thank you for the reply. I raised a bug with ActiveState. I am a Community
User, so I can't access prior builds of ActiveTcl, and I am no where near
competent enough to build up a framework.
--
___
Python tracker
Serhiy Storchaka added the comment:
Thank you Mark.
--
stage: patch review - commit review
versions: +Python 2.7, Python 3.4, Python 3.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18684
New submission from Nick Coghlan:
Based on a current python-dev discussion, I'd like to suggest a high level
convenience API in asyncio to dispatch a blocking call out to a separate thread
or process:
# Call blocking operation from asynchronous code
def blocking_call(f, *args, **kwds):
Martin Panter added the comment:
See also Issue 23220, specifically about the backspace control code.
I understand the only control codes that Idle handles are newlines (line feed,
\n) and tabs (\t).
--
nosy: +vadmium
title: IDLE Text Output With ASCII Codes Not Working - IDLE Text
Changes by Kevin Phillips (kmecpp) kme...@gmail.com:
--
title: IDLE Bug - IDLE Text Output Bug with ASCII Codes
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24572
___
New submission from Kevin Phillips (kmecpp):
This appears to be a bug with IDLE that happens when printing out ASCII codes.
I posted the issue to stackoverflow when I came accross it because I didn't
know what the problem was, so there is a more detailed description of the
there:
New submission from Topher Kessler:
There may be a bug in how tkinter frames are handled when called in multiple
processes in OS X.
I am trying to run a simple script that defines a new Frame subclass and then
attempts to call it multiple times in separate processes using the
multiprocessing
Kevin Walzer added the comment:
Where in the IDLE source code tree is this code housed? Is it possible to
provide a Python script that reproduces the issue?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24570
Changes by Kevin Phillips (kmecpp) kme...@gmail.com:
--
title: IDLE Text Output Bug with ASCII Codes - IDLE Text Output With ASCII
Codes Not Working
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24572
bee13oy added the comment:
I tested this path, and It really fixed this issue. But I'm wondering Python
2.7.10 was released at May 23, 2015, and this path was created at March
22,2015. So does it mean, Python 2.7.10/3.5.0b2 was compiled and released
without applying this path?
--
68 matches
Mail list logo
