Changes by SilentGhost <ghost@runbox.com>:
--
resolution: fixed ->
stage: patch review ->
status: closed -> open
___
Python tracker <rep...@bugs.python.org>
<http://bu
SilentGhost added the comment:
I get the following compiler warning now:
In file included from ./Include/Python.h:66:0,
from /cpython/Modules/_ssl.c:19:
/cpython/Modules/_ssl.c: In function ‘_setup_ssl_threads’:
./Include/pymem.h:136:18: warning: comparison is always false due
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: -SilentGhost
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25478>
___
_
Changes by SilentGhost <ghost@runbox.com>:
--
Removed message: http://bugs.python.org/msg275998
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
SilentGhost added the comment:
Floats are also not fully supported by the Counter class, for example,
sorted(Counter(a=1.0).elements()) results in TypeError.
--
nosy: +SilentGhost
___
Python tracker <rep...@bugs.python.org>
<http://bugs.p
Changes by SilentGhost <ghost@runbox.com>:
Removed file: http://bugs.python.org/file44538/28068.diff
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
SilentGhost added the comment:
Given that it's a Windows issue, I'm sure Windows core developers in the nosy
list would find a way to verify the fix. For the record, this bug was
introduced in issue 11824.
--
nosy: +meador.inge
___
Python tracker
SilentGhost added the comment:
Sure, that was just a typo. While "no errors" is good news, does the code is
actually doing what it's supposed to do? Are you sure there aren't any hidden
issue related to the potentially incorrect paths?
--
Added file: http://bugs.python.org
SilentGhost added the comment:
I get normal behaviour on e3dbe8b7279a
--
nosy: +SilentGhost
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
SilentGhost added the comment:
Here is the patch, I'm not sure if any more changes are needed there, so it
would be good to test.
--
components: +Windows
keywords: +patch
nosy: +SilentGhost, paul.moore, steve.dower, tim.golden, zach.ware
stage: -> patch review
type: compile er
Changes by SilentGhost <ghost@runbox.com>:
--
stage: -> resolved
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue28063>
___
__
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +michael.foord
versions: +Python 3.7 -Python 3.3
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
SilentGhost added the comment:
Cannot reproduce this either on stock 3.5.2 or 3.6 on Ubuntu.
--
nosy: +SilentGhost
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Changes by SilentGhost <ghost@runbox.com>:
--
resolution: -> not a bug
stage: test needed -> resolved
___
Python tracker <rep...@bugs.python.org>
<http://bugs.
SilentGhost added the comment:
I get the following warning in Firefox's Developer console:
This site appears to use a scroll-linked positioning effect. This may not work
well with asynchronous panning; see
https://developer.mozilla.org/docs/Mozilla/Performance/ScrollLinkedEffects
SilentGhost added the comment:
Just the least intrusive patch. Also, to me PyPy behaviour doesn't seem correct.
--
nosy: +SilentGhost
stage: needs patch -> patch review
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.or
Changes by SilentGhost <ghost@runbox.com>:
--
keywords: +patch
Added file: http://bugs.python.org/file44477/issue28029.diff
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Interpreter Core
stage: -> needs patch
versions: +Python 3.5, Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by SilentGhost <ghost@runbox.com>:
--
stage: patch review -> commit review
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by SilentGhost <ghost@runbox.com>:
--
stage: -> patch review
versions: -Python 3.3, Python 3.4
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by SilentGhost <ghost@runbox.com>:
--
resolution: -> duplicate
stage: -> resolved
status: open -> closed
superseder: -> TypeError in logging.HTTPHandler.emit; possible python 2 to 3
conversion issue
___
P
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +vinay.sajip
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27935>
___
_
Changes by SilentGhost <ghost@runbox.com>:
--
stage: patch review -> resolved
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by SilentGhost <ghost@runbox.com>:
--
stage: -> resolved
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27909>
___
__
SilentGhost added the comment:
Since there are more than a quarter of all characters changed between two
sequences, they are considered sufficiently different and no by-character
comparison is shown.
--
nosy: +SilentGhost
resolution: -> not a bug
stage: -> resolved
status
SilentGhost added the comment:
LGTM.
--
nosy: +SilentGhost
stage: patch review -> commit review
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.or
Changes by SilentGhost <ghost@runbox.com>:
--
stage: -> patch review
type: -> behavior
___
Python tracker <rep...@bugs.python.org>
<http://bugs.
Changes by SilentGhost <ghost@runbox.com>:
--
resolution: fixed ->
stage: resolved -> patch review
status: closed -> open
type: performance -> behavior
___
Python tracker <rep...@bugs.python.org>
<http:/
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +amaury.forgeotdarc, belopolsky, meador.inge
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Library (Lib)
nosy: +giampaolo.rodola, gvanrossum, haypo, yselivanov
stage: -> patch review
versions: +Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Extension Modules
nosy: +brett.cannon
type: -> behavior
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +vinay.sajip
stage: -> patch review
versions: +Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by SilentGhost <ghost@runbox.com>:
--
stage: -> resolved
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27895>
___
__
SilentGhost added the comment:
This seems to be a consequence of issue 26513. Would you mind re-posting your
message there.
--
components: +Windows
keywords: +3.5regression
nosy: +SilentGhost, paul.moore, steve.dower, tim.golden, zach.ware
Changes by SilentGhost <ghost@runbox.com>:
--
resolution: -> not a bug
stage: -> resolved
type: -> behavior
___
Python tracker <rep...@bugs.python.org>
<https://bu
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Extension Modules
nosy: +jafo
stage: -> needs patch
versions: +Python 3.5, Python 3.6
___
Python tracker <rep...@bugs.python.org>
<https://bugs.pyt
SilentGhost added the comment:
regex module is not in standard library, on the latest 3.6 branch re module
breaks on curly apostrophe just fine. Perhaps, try reporting this issue on the
bitbucket tracker?
--
nosy: +SilentGhost
resolution: -> not a bug
stage: -> resolved
status
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +eli.bendersky, scoder
type: -> behavior
___
Python tracker <rep...@bugs.python.org>
<https://bugs.pyt
Changes by SilentGhost <ghost@runbox.com>:
--
stage: -> needs patch
versions: -Python 3.2, Python 3.3, Python 3.4
___
Python tracker <rep...@bugs.python.org>
<https://bugs.pyt
SilentGhost added the comment:
Guido doesn't like the idea in general[0].
[0] https://bugs.python.org/issue26488#msg273329
--
nosy: +SilentGhost
resolution: -> rejected
stage: -> resolved
status: open -> closed
___
Python tra
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +pmoody
stage: -> patch review
___
Python tracker <rep...@bugs.python.org>
<https://bugs.pyt
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +ezio.melotti
stage: -> patch review
versions: +Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
SilentGhost added the comment:
The change was implemented in issue22796 and is listed in the what's new
document. Any RFC I'm looking at says that the value is required, so your
syntax is simply not valid and is rejected by the parser.
--
nosy: +SilentGhost, pitrou
resolution
SilentGhost added the comment:
Ethan, in Misc/NEWS it says "compatibility ship"
--
nosy: +SilentGhost
___
Python tracker <rep...@bugs.python.org>
<http://bugs.py
SilentGhost added the comment:
Spaces around '=' sign in function definitions/calls.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
SilentGhost added the comment:
Also, these would need documentation changes.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
SilentGhost added the comment:
Could you please produce a patch that conforms to PEP-8.
--
nosy: +SilentGhost
stage: -> patch review
versions: +Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.or
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Interpreter Core -Windows
stage: -> resolved
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by SilentGhost <ghost@runbox.com>:
--
stage: -> needs patch
type: -> behavior
versions: -Python 3.4
___
Python tracker <rep...@bugs.python.org>
<http://bugs.
Changes by SilentGhost <ghost@runbox.com>:
--
stage: patch review -> resolved
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
SilentGhost added the comment:
Brett, Misc/NEWS entry needs a # before issue number.
--
nosy: +SilentGhost
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Changes by SilentGhost <ghost@runbox.com>:
--
stage: -> resolved
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27755>
___
__
Changes by SilentGhost <ghost@runbox.com>:
--
resolution: -> out of date
stage: -> resolved
___
Python tracker <rep...@bugs.python.org>
<http://bugs.
SilentGhost added the comment:
I don't see how this is an improvement. Before it clearly said that the first
argument must be file name, now it's an oddly confusing statement. Also,
typically we don't list all the possibilities of what the arguments must
SilentGhost added the comment:
Do you care to propose an improved wording?
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
SilentGhost added the comment:
It says "The source code is loaded from the file name *file*". That seems
unambiguous enough to me.
--
nosy: +SilentGhost
type: -> behavior
___
Python tracker <rep...@bugs.python.org>
<
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +Cubky, Devin Jeanpierre, eric.araujo, ezio.melotti, jairotrad, jbitcm-,
mikehoy, r.david.murray, terry.reedy -lissacoffeyx
___
Python tracker <rep...@bugs.python.org>
<http://
Changes by SilentGhost <ghost@runbox.com>:
--
Removed message: http://bugs.python.org/msg272582
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@runbox.com>:
--
Removed message: http://bugs.python.org/msg272583
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pytho
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +Chris.Waigl, Johannes.Hoff, ajaksu2, alexz, atommixz, barry, bgamari,
catalin.iacob, catlee, cco3, checat, daniel.ugra, eric.araujo, forest_atq,
fsteinel, gotgenes, guettli, jnoller, martin.panter, orsenthil,
piotr.dob
SilentGhost added the comment:
Could anyone could have a look at this fairly trivial patch?
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Changes by SilentGhost <ghost@runbox.com>:
--
stage: -> resolved
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27742>
___
__
SilentGhost added the comment:
Thanks, Lele.
--
resolution: -> fixed
stage: commit review -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
SilentGhost added the comment:
LGTM
--
stage: -> commit review
type: -> behavior
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Documentation
versions: +Python 3.5
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
SilentGhost added the comment:
Then I guess all the changes to Modules/_sqlite.c are there by mistake? Would
you mid refreshing your patch to remove them?
--
assignee: -> docs@python
components: +Documentation
nosy: +SilentGhost, docs@python
versions: +Python
SilentGhost added the comment:
> There seems to be more to it
I'm not sure what "it" are you referring to. The output of randint is not
guaranteed to be the same across versions, the seeded sequence is still the
same between python2 and 3 - as documented.
--
title:
SilentGhost added the comment:
The rnd.random is still producing the same sequence, between versions. randint
evidently doesn't, but that must be happening elsewhere.
--
components: +Extension Modules
nosy: +SilentGhost, mark.dickinson, rhettinger
type: -> behavior
versions: +Pyt
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +barry, r.david.murray
stage: -> needs patch
type: -> behavior
versions: -Python 3.2, Python 3.3
___
Python tracker <rep...@bugs.python.org>
<http://bugs.
Changes by SilentGhost <ghost@runbox.com>:
--
resolution: not a bug -> wont fix
stage: patch review -> resolved
___
Python tracker <rep...@bugs.python.org>
<http://bugs.
SilentGhost added the comment:
Why is that an issue?
--
nosy: +SilentGhost
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27728>
___
__
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
stage: -> needs patch
type: compile error -> behavior
versions: +Python 3.6
___
Python tracker <rep...@
SilentGhost added the comment:
For the record, according to http://ctags.sourceforge.net/news.html that option
was removed in version 2.0.1 released over 18 years ago.
--
nosy: +SilentGhost
___
Python tracker <rep...@bugs.python.org>
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Interpreter Core
nosy: +facundobatista, mark.dickinson, rhettinger, skrah
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
SilentGhost added the comment:
LGTM
--
stage: -> commit review
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27721>
___
___
P
SilentGhost added the comment:
Couple of things: your patch doesn't seem to apply cleanly for whatever reason
(most likely because it's a patch against python2); the change from lowercasing
to casefolding doesn't seem justified to me; the formatted value needs to be
repr-formatted - though
Changes by SilentGhost <ghost@runbox.com>:
Removed file: http://bugs.python.org/file44049/donttrim.diff
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
SilentGhost added the comment:
The degenerate behaviour appears ultimately due to the autojunk heuristic.
Given that autojunk defaults to True and there isn't any way to change via most
user-facing functions, I don't think there is an easy resolution that can be
found here. I'm going
SilentGhost added the comment:
> nor do I see any mention of socketpair in the 3.5 whatsnew
socket.socketpair has a versionchanged 3.5: Windows support added.
--
nosy: +SilentGhost
___
Python tracker <rep...@bugs.python.org>
<http://bug
New submission from SilentGhost:
msg264842 in issue26945 reports an odd results of HtmlDiff.make_file, digging
into it I've noticed couple of things: different output to one generated
directly from difflib.ndiff and underlying issue further up the stack that
generates same faulty output
SilentGhost added the comment:
JW, this doens't seem anything to do with the original issue. I'm going to
close this issue and open a new one that's dealing with your case, I have a fix
for it.
--
resolution: -> not a bug
stage: -> resolved
status: open -&g
SilentGhost added the comment:
At the time the len function in list comprehension is called .append has not
executed, the len call in list comprehension operates on object as it is,
whereas the object itself is only referenced rather than copied. If you were to
copy the yielded list
Changes by SilentGhost <ghost@runbox.com>:
Removed file: http://bugs.python.org/file44031/image001.jpg
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: -drkirkby
resolution: -> not a bug
stage: -> resolved
status: open -> closed
title: very important news -> spam
___
Python tracker <rep...@bugs.python.org>
<http:/
Changes by SilentGhost <ghost@runbox.com>:
--
Removed message: http://bugs.python.org/msg272092
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Windows
nosy: +paul.moore, pitrou, steve.dower, tim.golden, zach.ware
stage: -> needs patch
type: -> behavior
___
Python tracker <rep...@bugs.python.org>
<h
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Demos and Tools, Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
stage: -> patch review
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
SilentGhost added the comment:
On 3.6 it takes a very long time, but it does finish.
time ./python -c "raise ValueError ; 2 ** 12345678912345"
Traceback (most recent call last):
File "", line 1, in
ValueError
real1m35.673s
user1m18.952s
sys 0m16.6
Changes by SilentGhost <ghost@runbox.com>:
--
type: compile error -> resource usage
versions: +Python 2.7
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Interpreter Core
nosy: +haypo, serhiy.storchaka
versions: +Python 3.6 -Python 2.7
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
SilentGhost added the comment:
JW, could you submit a minimal reproducer for this?
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Changes by SilentGhost <ghost@runbox.com>:
--
stage: -> resolved
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27694>
___
__
Changes by SilentGhost <ghost@runbox.com>:
--
stage: needs patch -> patch review
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
SilentGhost added the comment:
You should be able to request re-opening in your message in that issue, no need
to open a new issue for that.
--
nosy: +SilentGhost
resolution: -> not a bug
stage: -> resolved
status: open -> closed
_
SilentGhost added the comment:
I'm not suggesting your reviewing code, I've referenced issue where this change
was discussed and implemented so that you can familiarize yourself with the
arguments. Your code worked by accident, the workaround seems trivial.
If you wish to advance further
SilentGhost added the comment:
It's not an accidental change (so it's not "broken" by any definition), see
issue 19995 for details.
--
nosy: +SilentGhost
resolution: -> wont fix
stage: -> resolved
status: open -> closed
___
SilentGhost added the comment:
Cannot reproduce this on Linux
--
nosy: +SilentGhost
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
SilentGhost added the comment:
Because elements of the tab list are the same list. And since list is a mutable
type, modifying list object will be visible to via all the reference / names
that point to that object. There are various ways to work around this
behaviour, typically a list
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Extension Modules -Library (Lib)
nosy: +twouters
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
601 - 700 of 1379 matches
Mail list logo
