SilentGhost added the comment:
Why does your __len__ method returns 1? Shouldn't it be 0 since this is an
empty iterator? Changing it to zero seems to fix the "issue" too.
------
nosy: +SilentGhost
___
Python tracker
<http://bugs.pyt
SilentGhost added the comment:
The question is why are you defining __len__ if you don't know the size of your
final object? Or at least, why are you starting with a potentially wrong
initial value? This issue doesn't exist if you either don't define the method
or retur
SilentGhost added the comment:
Seems like the issue is caused by pip installation, so you should be able to
fix it using --without-ensurepip switch for configure.
--
nosy: +SilentGhost
___
Python tracker
<http://bugs.python.org/issue27
SilentGhost added the comment:
I wouldn't consider that an issue to be honest, the zlib is a dependency of pip
and this failure is not unexpected.
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python
SilentGhost added the comment:
Well, there isn't anything to build in case of pip. I presume that was the
decision made during the PEP implementation, so I'm adding the two core
developers responsible.
--
nosy: +dstufft, ncoghlan
___
Pyth
Changes by SilentGhost :
--
assignee: -> docs@python
components: +Documentation
nosy: +SilentGhost, docs@python
stage: -> patch review
type: enhancement -> behavior
versions: +Python 3.5
___
Python tracker
<http://bugs.python.or
SilentGhost added the comment:
LGTM
--
assignee: -> docs@python
components: +Documentation
nosy: +SilentGhost, docs@python
stage: -> commit review
___
Python tracker
<http://bugs.python.org/i
SilentGhost added the comment:
bytearray is a mutable object and the behaviour is compatible with behaviour of
any mutable object in Python. You're passing a into the yuke_bpe function and
the original object is being modified (emptied) there. To work around this you
could copy the o
Changes by SilentGhost :
--
nosy: +SilentGhost
___
Python tracker
<http://bugs.python.org/issue27661>
___
___
Python-bugs-list mailing list
Unsubscribe:
SilentGhost added the comment:
It is quoting the values when line terminator contains any of the special
characters. Exactly like documented.
https://docs.python.org/3/library/csv.html#csv.QUOTE_MINIMAL
--
nosy: +SilentGhost
resolution: -> not a bug
stage: -> resolved
status
Changes by SilentGhost :
--
components: +Extension Modules -Library (Lib)
nosy: +twouters
___
Python tracker
<http://bugs.python.org/issue27666>
___
___
Python-bug
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
SilentGhost added the comment:
Cannot reproduce this on Linux
--
nosy: +SilentGhost
___
Python tracker
<http://bugs.python.org/issue27594>
___
___
Python-bug
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:
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 advan
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
_
Changes by SilentGhost :
--
stage: needs patch -> patch review
___
Python tracker
<http://bugs.python.org/issue27566>
___
___
Python-bugs-list mailing list
Un
Changes by SilentGhost :
--
stage: -> resolved
___
Python tracker
<http://bugs.python.org/issue27694>
___
___
Python-bugs-list mailing list
Unsubscrib
SilentGhost added the comment:
JW, could you submit a minimal reproducer for this?
--
___
Python tracker
<http://bugs.python.org/issue26945>
___
___
Python-bug
Changes by SilentGhost :
--
components: +Interpreter Core
nosy: +haypo, serhiy.storchaka
versions: +Python 3.6 -Python 2.7
___
Python tracker
<http://bugs.python.org/issue27
Changes by SilentGhost :
--
type: compile error -> resource usage
versions: +Python 2.7
___
Python tracker
<http://bugs.python.org/issue27695>
___
___
Python-
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 :
--
components: +Demos and Tools, Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
stage: -> patch review
___
Python tracker
<http://bugs.python.org/issu
Changes by SilentGhost :
--
components: +Windows
nosy: +paul.moore, pitrou, steve.dower, tim.golden, zach.ware
stage: -> needs patch
type: -> behavior
___
Python tracker
<http://bugs.python.org/i
Changes by SilentGhost :
--
Removed message: http://bugs.python.org/msg272092
___
Python tracker
<http://bugs.python.org/issue27699>
___
___
Python-bugs-list m
Changes by SilentGhost :
--
nosy: -drkirkby
resolution: -> not a bug
stage: -> resolved
status: open -> closed
title: very important news -> spam
___
Python tracker
<http://bugs.python
Changes by SilentGhost :
Removed file: http://bugs.python.org/file44031/image001.jpg
___
Python tracker
<http://bugs.python.org/issue27699>
___
___
Python-bugs-list mailin
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, then a
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
s
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:
> 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
<http://bugs.python.org/issu
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&
Changes by SilentGhost :
Removed file: http://bugs.python.org/file44049/donttrim.diff
___
Python tracker
<http://bugs.python.org/issue27709>
___
___
Python-bugs-list m
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-for
SilentGhost added the comment:
LGTM
--
stage: -> commit review
___
Python tracker
<http://bugs.python.org/issue27721>
___
___
Python-bugs-list mailing list
Un
Changes by SilentGhost :
--
components: +Interpreter Core
nosy: +facundobatista, mark.dickinson, rhettinger, skrah
___
Python tracker
<http://bugs.python.org/issue27
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
<http://bugs.python.org/issue27
Changes by SilentGhost :
--
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
stage: -> needs patch
type: compile error -> behavior
versions: +Python 3.6
___
Python tracker
<http://bugs.python.org/i
SilentGhost added the comment:
Why is that an issue?
--
nosy: +SilentGhost
___
Python tracker
<http://bugs.python.org/issue27728>
___
___
Python-bugs-list mailin
Changes by SilentGhost :
--
resolution: not a bug -> wont fix
stage: patch review -> resolved
___
Python tracker
<http://bugs.python.org/issue27721>
___
___
Changes by SilentGhost :
--
nosy: +barry, r.david.murray
stage: -> needs patch
type: -> behavior
versions: -Python 3.2, Python 3.3
___
Python tracker
<http://bugs.python.org/i
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:
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.
--
ti
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
Changes by SilentGhost :
--
components: +Documentation
versions: +Python 3.5
___
Python tracker
<http://bugs.python.org/issue27745>
___
___
Python-bugs-list mailin
SilentGhost added the comment:
LGTM
--
stage: -> commit review
type: -> behavior
___
Python tracker
<http://bugs.python.org/issue27745>
___
___
Pyth
SilentGhost added the comment:
Thanks, Lele.
--
resolution: -> fixed
stage: commit review -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
Changes by SilentGhost :
--
stage: -> resolved
___
Python tracker
<http://bugs.python.org/issue27742>
___
___
Python-bugs-list mailing list
Unsubscrib
SilentGhost added the comment:
Could anyone could have a look at this fairly trivial patch?
--
___
Python tracker
<http://bugs.python.org/issue25805>
___
___
Pytho
Changes by SilentGhost :
--
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.dobrogost, pitrou, r.david.murray
Changes by SilentGhost :
--
Removed message: http://bugs.python.org/msg272583
___
Python tracker
<http://bugs.python.org/issue3244>
___
___
Python-bugs-list mailin
Changes by SilentGhost :
--
Removed message: http://bugs.python.org/msg272582
___
Python tracker
<http://bugs.python.org/issue13691>
___
___
Python-bugs-list m
Changes by SilentGhost :
--
nosy: +Cubky, Devin Jeanpierre, eric.araujo, ezio.melotti, jairotrad, jbitcm-,
mikehoy, r.david.murray, terry.reedy -lissacoffeyx
___
Python tracker
<http://bugs.python.org/issue13
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
<http://bugs.pytho
SilentGhost added the comment:
Do you care to propose an improved wording?
--
___
Python tracker
<http://bugs.python.org/issue27753>
___
___
Python-bugs-list m
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 argume
Changes by SilentGhost :
--
resolution: -> out of date
stage: -> resolved
___
Python tracker
<http://bugs.python.org/issue22395>
___
___
Python-bugs-list
Changes by SilentGhost :
--
stage: -> resolved
___
Python tracker
<http://bugs.python.org/issue27755>
___
___
Python-bugs-list mailing list
Unsubscrib
SilentGhost added the comment:
Brett, Misc/NEWS entry needs a # before issue number.
--
nosy: +SilentGhost
___
Python tracker
<http://bugs.python.org/issue27
Changes by SilentGhost :
--
stage: patch review -> resolved
___
Python tracker
<http://bugs.python.org/issue27558>
___
___
Python-bugs-list mailing list
Un
Changes by SilentGhost :
--
stage: -> needs patch
type: -> behavior
versions: -Python 3.4
___
Python tracker
<http://bugs.python.org/issue27797>
___
___
Changes by SilentGhost :
--
components: +Interpreter Core -Windows
stage: -> resolved
___
Python tracker
<http://bugs.python.org/issue27813>
___
___
Python-
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
<http://bugs.python.org/issu
SilentGhost added the comment:
Also, these would need documentation changes.
--
___
Python tracker
<http://bugs.python.org/issue27814>
___
___
Python-bugs-list m
SilentGhost added the comment:
Spaces around '=' sign in function definitions/calls.
--
___
Python tracker
<http://bugs.python.org/issue27814>
___
___
SilentGhost added the comment:
Ethan, in Misc/NEWS it says "compatibility ship"
--
nosy: +SilentGhost
___
Python tracker
<http://bugs.python.o
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
resolutio
Changes by SilentGhost :
--
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
___
Python tracker
<http://bugs.python.org/issue27
Changes by SilentGhost :
--
nosy: +ezio.melotti
stage: -> patch review
versions: +Python 3.6
___
Python tracker
<http://bugs.python.org/issue27835>
___
___
Py
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 t
Changes by SilentGhost :
--
nosy: +pmoody
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue27860>
___
___
Python-bugs-list mai
Changes by SilentGhost :
--
stage: -> needs patch
versions: -Python 3.2, Python 3.3, Python 3.4
___
Python tracker
<https://bugs.python.org/issue27859>
___
_
Changes by SilentGhost :
--
nosy: +eli.bendersky, scoder
type: -> behavior
___
Python tracker
<https://bugs.python.org/issue27863>
___
___
Python-bugs-list mai
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 :
--
components: +Extension Modules
nosy: +jafo
stage: -> needs patch
versions: +Python 3.5, Python 3.6
___
Python tracker
<https://bugs.python.org/issu
Changes by SilentGhost :
--
resolution: -> not a bug
stage: -> resolved
type: -> behavior
___
Python tracker
<https://bugs.python.org/issue27887>
___
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 :
--
stage: -> resolved
___
Python tracker
<http://bugs.python.org/issue27895>
___
___
Python-bugs-list mailing list
Unsubscrib
New submission from SilentGhost:
If you run attached file w/ 3.2 and 3.3 (and later) versions, you'll notice
that the new version of parser doesn't handle empty argument list:
$ python3.2 test.py
usage: test.py [-h] {demo} ...
test.py: error: too few arguments
$ python3.3 test.py
Changes by SilentGhost :
--
title: argparse subparsers break without without argument -> argparse
subparsers break without arguments
___
Python tracker
<http://bugs.python.org/issu
SilentGhost added the comment:
Hi Henning,
this is not a bug. This is to do with how floating point numbers represented in
computers. I'd suggest https://en.wikipedia.org/wiki/IEEE_floating_point as a
starting point. Briefly, due to binary base that the computers operate on, not
every n
SilentGhost added the comment:
This seem like an issue with numpy, not python. Perhaps installing using binary
would be a better option for you? In any case, this need further elaborating at
what the actual problem and the solution could be.
--
nosy: +SilentGhost
resolution: -> no
Changes by SilentGhost :
--
resolution: -> duplicate
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue23118>
___
___
Python-bugs-list
SilentGhost added the comment:
Closed issue23118 as identical issue to this one.
--
nosy: +SilentGhost
___
Python tracker
<http://bugs.python.org/issue23
Changes by SilentGhost :
--
components: +Macintosh
nosy: +ned.deily, ronaldoussoren
versions: +Python 2.7
___
Python tracker
<http://bugs.python.org/issue23
SilentGhost added the comment:
As explained in the docs[1] integer is a valid argument for the open function
in the python3. It is also noted that the file descriptor is going to be
closed, unless closefd argument to the open function was False, when f.close()
is called. This is the behaviour
Changes by SilentGhost :
--
components: +Library (Lib) -Installation
nosy: +gregory.p.smith
___
Python tracker
<http://bugs.python.org/issue23223>
___
___
Pytho
SilentGhost added the comment:
Perhaps I'm missing something here, but it doesn't seem to be a problem with
valid links. Only invalid symlinks are causing this issue.
--
nosy: +SilentGhost
___
Python tracker
<http://bugs.python.o
SilentGhost added the comment:
Couple of things:
1. "chosen chosen"
2. double space needed before "You can invoke..."
--
nosy: +SilentGhost
___
Python tracker
<http://bug
Changes by SilentGhost :
--
keywords: +easy
versions: +Python 3.5 -Python 3.6
___
Python tracker
<http://bugs.python.org/issue23304>
___
___
Python-bugs-list m
SilentGhost added the comment:
It seems, if I read https://docs.python.org/3/reference/expressions.html#calls
correctly that the evaluation order of the function arguments is not defined in
general, as it depends on your use of keyword argument and exact function
signature. Naturally, f(a
SilentGhost added the comment:
Looks like it works exactly as the docs[1] describe:
>>> re.split(r'\s*[+/&;,]\s*|\s+and\s+', string)
['Dave', 'Sam', 'Jane', 'Zoe']
You're using capturing groups (parentheses) in your ori
SilentGhost added the comment:
Correct me if I'm wrong but this seem as a very unlikely use case. Why would
you need to ensure content of the defaultdict (i.e., why would you ever use its
fromkeys method)? And, perhaps, having to implicitly assign default factory is
not such a bad tra
SilentGhost added the comment:
Raymond, but Alec talks about
defaultdict.fromkeys(constants, factory=list)
as opposed to current solution
d = defaultdict.fromkeys(constants)
d.default_factory = list
for i in d:
d[i] = []
I wouldn't think that the dict.fromkeys shou
SilentGhost added the comment:
Looks like some sort of race condition. Sleeping for a second before
import_module seem to solve the problem.
--
components: +Interpreter Core
nosy: +SilentGhost, brett.cannon, eric.snow, ncoghlan
___
Python tracker
Changes by SilentGhost :
--
versions: +Python 3.5
___
Python tracker
<http://bugs.python.org/issue23412>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by SilentGhost :
--
components: +Macintosh
nosy: +hynek, ned.deily, ronaldoussoren
___
Python tracker
<http://bugs.python.org/issue23431>
___
___
Pytho
Changes by SilentGhost :
--
components: +Windows
nosy: +steve.dower, tim.golden, zach.ware
___
Python tracker
<http://bugs.python.org/issue23463>
___
___
Pytho
SilentGhost added the comment:
Perhaps I'm misinterpreting your message, but this doesn't seem like a problem
with datetime module. The issue is with dateutil module, which is not the part
of the standard library and is not developed here. Also, I can reproduce this
issue on 3.4
SilentGhost added the comment:
This is the page: https://docs.python.org/3/download.html also true about the
3.5 at https://docs.python.org/3.5/download.html
All the links in the table result in 404. Clearly the files are not at
https://docs.python.org/3/archives/
--
nosy
801 - 900 of 1410 matches
Mail list logo
