SilentGhost added the comment:
If you run the command in your interpreter you'll see that the output is
correct.
--
assignee: -> docs@python
components: +Documentation -Demos and Tools
nosy: +SilentGhost, docs@python
resolution: -> not a bug
status: ope
SilentGhost added the comment:
I suggest you add this information to issue21167 as it's exactly the same
behaviour you're seeing. There really is no need to have a separate issue.
--
nosy: +SilentGhost
status: open -> closed
superseder: -> float('nan') retu
Changes by SilentGhost :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue23495>
___
___
Python-bugs-list mailing list
Unsubscribe:
SilentGhost added the comment:
Shouldn't the line above read "now accepts" rather than "how accepts"?
--
nosy: +SilentGhost
___
Python tracker
<http:
Changes by SilentGhost :
--
nosy: +rhettinger
___
Python tracker
<http://bugs.python.org/issue25435>
___
___
Python-bugs-list mailing list
Unsubscribe:
SilentGhost added the comment:
This seems like a change for the sake of change. I think any module that
requires argparse features can be moved in its own time.
--
nosy: +SilentGhost
resolution: -> rejected
status: open -> closed
___
Python t
Changes by SilentGhost :
--
nosy: +jnoller, sbt
___
Python tracker
<http://bugs.python.org/issue25469>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by SilentGhost :
--
versions: -Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5
___
Python tracker
<http://bugs.python.org/issue25469>
___
___
Changes by SilentGhost :
--
versions: +Python 3.6 -Python 3.4
___
Python tracker
<http://bugs.python.org/issue18973>
___
___
Python-bugs-list mailing list
Unsub
SilentGhost added the comment:
This probably needs test
--
nosy: +SilentGhost
___
Python tracker
<http://bugs.python.org/issue25485>
___
___
Python-bugs-list m
SilentGhost added the comment:
That's fine as a code change, but that's not the kind of test I meant. There is
a Lib/test/test_ftplib.py and it basically needs test_with_statement added to
one or few test cases. Have a look at how the similar functions implemented in
SilentGhost added the comment:
Modules that use optparse: calendar (issue18973 has patch), uu (seems trivial
to change), test_decimal (trivial too), profile, cprofile
Tools: strginbench, ccbench, iobench
Neither of the changes are particularly tricky it seems.
--
nosy: +SilentGhost
Changes by SilentGhost :
--
components: +Regular Expressions
nosy: +mrabarnett
versions: +Python 3.6
___
Python tracker
<http://bugs.python.org/issue25
SilentGhost added the comment:
>>> keyword.iskeyword('pass')
True
There doesn't seem anything particular about def, none of the keywords have
"keyword" type, because there doesn't seem to be one:
https://docs.python.org/3.6/library/token.html
--
New submission from SilentGhost:
With introduction of async and await tokens in 3.5 the token documentation
needs updating.
--
assignee: docs@python
components: Documentation
files: token.diff
keywords: patch
messages: 254281
nosy: SilentGhost, docs@python
priority: normal
severity
SilentGhost added the comment:
Perhaps, my example wasn't as self-explanatory as I hoped. def is not DEF in
the token list, because there isn't such a token DEF, as there isn't a token
PASS or a token for any other keyword. The fact that there is an ASYNC and
AWAIT toke
Changes by SilentGhost :
--
components: +Windows -Interpreter Core, Regular Expressions
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
___
Python tracker
<http://bugs.python.org/issue25
Changes by SilentGhost :
--
components: +Unicode
nosy: +haypo
___
Python tracker
<http://bugs.python.org/issue25581>
___
___
Python-bugs-list mailing list
Unsub
SilentGhost added the comment:
> Interesting, I didn't even know (remember?) about the -U flag, and it isn't
> documented.
https://docs.python.org/2/using/cmdline.html#cmdoption-U
It isn't clear when this broken or why, but I think existing documentation
could be adju
Changes by SilentGhost :
--
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
___
Python tracker
<http://bugs.python.org/issue25
New submission from SilentGhost:
In enum docs[0], there is a suggestion that the attribute access on members
should raise an AttributeError:
>>> Color.red.blue
Traceback (most recent call last):
...
AttributeError: 'Color' object has no attribute 'blue'
which is
SilentGhost added the comment:
Here is the test, it seems to have been 2545bfe0d273 that caused it
(issue23486): test passes prior to it and fails on it (and I assume uniformly
after).
--
keywords: +patch
Added file: http://bugs.python.org/file41003/test_issue25594.diff
Changes by SilentGhost :
--
components: -Documentation
stage: test needed -> needs patch
title: enum docs outdated re attribute access -> enum instance attribute access
possible
___
Python tracker
<http://bugs.python.org/i
SilentGhost added the comment:
I've added versionchanged, since this is what's done in os, for similar lists.
--
___
Python tracker
<http://bugs.python.o
SilentGhost added the comment:
Hm, not sure why the file didn't get uploaded, I clearly remember attaching it.
Yury, what is the implication for this issue? Are you suggesting that the note
should state that these two are temporary? Or is this information available
somewhere else, in W
SilentGhost added the comment:
Here is the updated wording. I'm not familiar with other such cases in the
stdlib, if any one knows of another similar case, I'd be glad to correct the
language to match previous usage.
--
Added file: http://bugs.python.org/file41031/issue25
SilentGhost added the comment:
Yes. It follows from definition of bytes in python3
https://docs.python.org/3/library/functions.html#bytes
Some useful information is also available in 3.0 release notes:
https://docs.python.org/3/whatsnew/3.0.html#text-vs-data-instead-of-unicode-vs-8-bit
SilentGhost added the comment:
It doesn't seem docstring-specific, docstring is a regular Python object and
ast.literal_eval would fail if you have more than one literals of any kind. Put
two integers in your file and the literal_eval will fail.
--
nosy: +Silent
SilentGhost added the comment:
Can you provide a test?
--
nosy: +SilentGhost, serhiy.storchaka, tarek
versions: +Python 3.6
___
Python tracker
<http://bugs.python.org/issue25
Changes by SilentGhost :
--
nosy: +pitrou
versions: +Python 3.6 -Python 3.5
___
Python tracker
<http://bugs.python.org/issue25625>
___
___
Python-bugs-list mailin
Changes by SilentGhost :
--
components: +Library (Lib)
nosy: +nadeem.vawda, twouters
versions: +Python 3.6
___
Python tracker
<http://bugs.python.org/issue25
SilentGhost added the comment:
This also seem to affect python 3, there os.popen implemented using
subprocess.Popen, but that one is called with shell=True. So basically the
string that's passed to os.popen should be quoted. The attached patch seem to
be sufficient when applied on the de
SilentGhost added the comment:
No further comments re the latest patch.
--
___
Python tracker
<http://bugs.python.org/issue25594>
___
___
Python-bugs-list mailin
Changes by SilentGhost :
--
components: +IO, Windows
keywords: +3.5regression
nosy: +benjamin.peterson, paul.moore, pitrou, steve.dower, stutzbach,
tim.golden, zach.ware
stage: -> test needed
___
Python tracker
<http://bugs.python.org/issu
SilentGhost added the comment:
Re msg233465: it doesn't seem like a particularly good justification to remove
something that is not hurting anyone. The problem now is that because
http.HTTPStatus is an enumeration, it cannot be extended, therefore when
someone encounters these non-sta
Changes by SilentGhost :
--
nosy: +vinay.sajip
stage: -> patch review
versions: +Python 3.6
___
Python tracker
<http://bugs.python.org/issue25685>
___
___
Py
New submission from SilentGhost:
Just a minor fix, removing the following: "Here is a sample on how using it:"
--
assignee: docs@python
components: Documentation
files: ftplib_docs.diff
keywords: patch
messages: 255056
nosy: SilentGhost, docs@python
priority: normal
severi
Changes by SilentGhost :
--
components: +Tests
nosy: +ezio.melotti, michael.foord, rbcollins
stage: -> patch review
___
Python tracker
<http://bugs.python.org/issu
SilentGhost added the comment:
test_support has this line:
TESTDIRN = os.path.basename(tempfile.mkdtemp(dir='.'))
Which is the culprit. The reason it gets so far as to import the module is due
to the "fuzzy logic" check looking for __all__
What I'd suggest is rep
Changes by SilentGhost :
--
components: +Windows
nosy: +brett.cannon, eric.snow, steve.dower, tim.golden, zach.ware
___
Python tracker
<http://bugs.python.org/issue25
Changes by SilentGhost :
--
components: +Build, Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
___
Python tracker
<http://bugs.python.org/issue25
SilentGhost added the comment:
I tried re-writing that bit using subprocess.Popen but since the 2.7 support is
needed I genuinely don't see any benefit that would add on top of the submitted
patch.
--
___
Python tracker
<http://bugs.py
SilentGhost added the comment:
Yeah, it would be great, Martin, if only that code worked in python2. Anyway,
here is an alternative patch.
--
Added file: http://bugs.python.org/file41189/issue25627_3.diff
___
Python tracker
<http://bugs.python.
Changes by SilentGhost :
--
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
type: performance -> behavior
___
Python tracker
<http://bugs.python.org/issu
SilentGhost added the comment:
OK, here is seemingly python2-proof patch. At least it shouldn't have glaring
syntax errors on python2 (as the previous one did). But I'd appreciate if some
RPM people could actually run the test.
--
Added file: http://bugs.python.org
SilentGhost added the comment:
Updated version of the patch including Martin's suggestions.
--
Added file: http://bugs.python.org/file41197/issue25627_5.diff
___
Python tracker
<http://bugs.python.org/is
Changes by SilentGhost :
--
components: +Library (Lib)
nosy: +stutzbach
stage: -> test needed
___
Python tracker
<http://bugs.python.org/issue25778>
___
___
Py
Changes by SilentGhost :
--
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
___
Python tracker
<http://bugs.python.org/issue25
Changes by SilentGhost :
--
nosy: +pitrou
___
Python tracker
<http://bugs.python.org/issue25780>
___
___
Python-bugs-list mailing list
Unsubscribe:
SilentGhost added the comment:
Anshul, it's attached to this issue, before messages start under Files heading.
Here is the direct link https://bugs.python.org/file41208/nullcheck.py
--
nosy: +SilentGhost
___
Python tracker
<http://bugs.py
SilentGhost added the comment:
Perhaps I'm wrong, but a superficial inspection of the ipaddress.py seem to
indicate that it's not affected by the same issue. _find_address_range is
implemented as a generator, it doesn't restart comparison on every iteration.
Alexander, did you
Changes by SilentGhost :
--
components: +Library (Lib)
nosy: +vinay.sajip
type: behavior -> enhancement
___
Python tracker
<http://bugs.python.org/issu
Changes by SilentGhost :
--
nosy: +SilentGhost
___
Python tracker
<http://bugs.python.org/issue25790>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from SilentGhost:
Running:
./python Lib/test/test_capi.py
I got EmbeddingTests erroring out in setUp: first line of which (a triple
application of os.path.dirname) creates an empty string which cannot be used as
an argument to os.chdir afterwards. I'm to be honest not a
New submission from SilentGhost:
Running test_zipfile64 from command line (i.e., ./python
Lib/test/test_zipfile64.py) I get two ResourceWarnings:
» ./python Lib/test/test_zipfile64.py
..Lib/test/test_zipfile64.py:82: ResourceWarning
SilentGhost added the comment:
Thanks, Serhiy. Running the test with test module: ./python -m test -v
test_zipfile64
doesn't produce the same warning. With this patch the warning is gone in
command-line mode too.
I haven't looked to verify that it's not an issue on 3.5 or e
New submission from SilentGhost:
Running ./python Lib/test/test_pkgutil.py I got one test failing:
test.support.TestFailed: Traceback (most recent call last):
File "Lib/test/test_pkgutil.py", line 346, in
test_get_loader_handles_missing_loader_attribute
self.asser
Changes by SilentGhost :
--
nosy: +georg.brandl
___
Python tracker
<http://bugs.python.org/issue25804>
___
___
Python-bugs-list mailing list
Unsubscribe:
SilentGhost added the comment:
It would be good to add test for this.
--
nosy: +SilentGhost
___
Python tracker
<http://bugs.python.org/issue25804>
___
___
Pytho
Changes by SilentGhost :
--
stage: -> test needed
___
Python tracker
<http://bugs.python.org/issue25804>
___
___
Python-bugs-list mailing list
Unsubscrib
New submission from SilentGhost:
When running ./python Lib/test/test_asyncio/test_tasks.py I get a
ResourceWarning:
Lib/asyncio/base_events.py:379: ResourceWarning: unclosed event loop
<_UnixSelectorEventLoop running=False closed=False debug=False>
When running using test machinery: ./
Changes by SilentGhost :
--
nosy: +giampaolo.rodola, pitrou
___
Python tracker
<http://bugs.python.org/issue25806>
___
___
Python-bugs-list mailing list
Unsub
SilentGhost added the comment:
Indeed it's one of those posted in the msg255490
--
resolution: -> duplicate
stage: -> resolved
status: open -> closed
superseder: -> asyncio tests are getting noisy
___
Python tracker
<ht
Changes by SilentGhost :
--
keywords: +needs review -patch
___
Python tracker
<http://bugs.python.org/issue25801>
___
___
Python-bugs-list mailing list
Unsub
New submission from SilentGhost:
When running either of the test_multiprocessing_fork,
test_multiprocessing_spawn or test_multiprocessing_forkserver I get error in
test_mymanager that leads to hanging. Here is the fragment:
test_mymanager
SilentGhost added the comment:
No, what this piece of code shows is that trying to assign a value to a tuple
element will cause an error. Of course, the same error would be raise when
using the the value 12345, but it's more instructive to use a different value
to not confuse the r
Changes by SilentGhost :
--
nosy: +lemburg, loewis
___
Python tracker
<http://bugs.python.org/issue25809>
___
___
Python-bugs-list mailing list
Unsubscribe:
SilentGhost added the comment:
I think this is the case where hard-coded strings where not updated in the C
files.
--
nosy: +SilentGhost
versions: -Python 3.5, Python 3.6
___
Python tracker
<http://bugs.python.org/issue25
Changes by SilentGhost :
--
stage: -> needs patch
___
Python tracker
<http://bugs.python.org/issue25810>
___
___
Python-bugs-list mailing list
Unsubscrib
SilentGhost added the comment:
Yes, whatever Andre's posted is not an output from 3.5. It's 3.4 or earlier.
Also it's a wider problem because the same issue exists for exec: built-in help
shows keyword arguments, while docs and implementation require only positional.
SilentGhost added the comment:
I'm not sure how the people are supposed to discover this convention according
to pep 436. Or is this now intended as two separate incompatible conventions
for online docs and built-in help?
--
___
Python tr
Changes by SilentGhost :
--
nosy: +larry
___
Python tracker
<http://bugs.python.org/issue25810>
___
___
Python-bugs-list mailing list
Unsubscribe:
SilentGhost added the comment:
No further comments from me. I haven't run the test, but I trust it passes
without any warnings.
--
nosy: +SilentGhost
___
Python tracker
<http://bugs.python.org/is
SilentGhost added the comment:
Hm, after doing "make clean" and rebuilding anew I'm not able to reproduce the
bug myself. I guess I just had a stale version of the module still hanging
around. Sorry for the mistaken report.
--
resolution: -> not a bug
stage: ->
Changes by SilentGhost :
--
components: +Windows
keywords: +needs review -patch
nosy: +paul.moore, steve.dower
versions: +Python 3.6 -Python 3.5
___
Python tracker
<http://bugs.python.org/issue9
SilentGhost added the comment:
Here is a usable patch, there doesn't seem to be a test for starttls, but it's
still would be a good idea to add a test for this issue.
--
nosy: +SilentGhost
versions: +Python 3.6 -Python 3.3
Added file: http://bugs.python.org/file41293/issue
SilentGhost added the comment:
I'm not sure what problem exactly you're trying to report / solve here. I'd
suggest you add an explanation of an issue you're experiencing. In any case
your current change seem to be breaking too many things.
--
components: +Librar
Changes by SilentGhost :
--
nosy: +alexandre.vassalotti, pitrou
type: crash -> behavior
___
Python tracker
<http://bugs.python.org/issue25861>
___
___
Python-
SilentGhost added the comment:
This seems fully covered in the What's new for 3.5:
https://docs.python.org/3/whatsnew/3.5.html#unsupported-operating-systems
--
nosy: +SilentGhost
resolution: -> not a bug
stage: -> resolved
status: ope
SilentGhost added the comment:
Hm, may be I'm seeing things, but the content of the current what's new section
is this:
Windows XP is no longer supported by Microsoft, thus, per :PEP:`11`, CPython
3.5 is no longer officially supported on this OS.
The proposed patch adds two se
Changes by SilentGhost :
--
nosy: +SilentGhost
___
Python tracker
<http://bugs.python.org/issue19475>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by SilentGhost :
--
components: +Library (Lib)
nosy: +benjamin.peterson, brett.cannon, georg.brandl, ncoghlan
stage: -> test needed
___
Python tracker
<http://bugs.python.org/issu
SilentGhost added the comment:
Hm, I'm going to close this as duplicate since a commenter in your previous
issue clearly stated: "I don't think the AST module makes any guarantee about
being able to reproduce the original source".
--
nosy: +SilentGhost, benjamin.pe
SilentGhost added the comment:
Even that produces 3 failures on my setup, though the full list would be
available when running: ./python -m test -v test_datetime
It is obvious, however, that the tests would fail: you've changed "if us:" to
SilentGhost added the comment:
I think what David was trying to say is that you could do
try:
user_input.encode(encoding)
except UnicodeError:
do_my_error_handling()
since UnicodeError is a super class of UnicodeDecodeError and
UnicodeEncodeError.
--
nosy: +SilentGhost
Changes by SilentGhost :
--
components: +IDLE, Macintosh, Tkinter
nosy: +gpolo, ned.deily, ronaldoussoren, serhiy.storchaka
___
Python tracker
<http://bugs.python.org/issue25
SilentGhost added the comment:
Martin, could you please escape * in Misc/NEWS, it causes a warning when
building documentation.
--
nosy: +SilentGhost
___
Python tracker
<http://bugs.python.org/issue19
New submission from SilentGhost:
I've run 'make linkcheck' on Doc and it highlighted a number of faulty links in
documentation. I've tried fixing some of them and here is the resulting patch.
It's a bit too long and touches many files, so to summarise:
* Most changes
Changes by SilentGhost :
--
stage: needs patch -> patch review
Added file: http://bugs.python.org/file41362/output.txt
___
Python tracker
<http://bugs.python.org/issu
SilentGhost added the comment:
Perhaps, I'm looking in the wrong place, but there doesn't seem be any test for
bytes filenames.
--
keywords: +3.5regression
nosy: +SilentGhost
stage: -> test needed
type: -> behavior
versions: +Python 3.6
__
Changes by SilentGhost :
--
resolution: -> duplicate
stage: -> resolved
superseder: -> TextIOWrapper: issues with interlaced read-write
type: -> behavior
___
Python tracker
<http://bugs.python
SilentGhost added the comment:
Here is the patch.
--
keywords: +needs review, patch
nosy: +SilentGhost
stage: -> patch review
type: -> behavior
versions: +Python 3.3, Python 3.5, Python 3.6
Added file: http://bugs.python.org/file41368/issue2591
New submission from SilentGhost:
This patch changes links from wiki to howto part of docs.
--
assignee: docs@python
components: Documentation
files: howto.diff
keywords: needs review, patch
messages: 256761
nosy: SilentGhost, docs@python
priority: normal
severity: normal
stage: patch
SilentGhost added the comment:
Here is the patch replacing exact match 'string of bytes' with :class:`bytes`
where appropriate. No match was found in base64.
--
Added file: http://bugs.python.org/file41375/issue25916_2.diff
___
Python trac
Changes by SilentGhost :
--
components: +Library (Lib) -IO
versions: +Python 3.5, Python 3.6 -Python 3.4
___
Python tracker
<http://bugs.python.org/issue25
SilentGhost added the comment:
I think the patch is nearly finalised, but I'd appreciate if someone else would
carefully go over the new C code. After that, I think, the patch could be
committed.
--
___
Python tracker
<http://bugs.py
SilentGhost added the comment:
There is a test suite which can be run to test for breakages:
./python -m test test_httplib
If you do that you'll notice that some things are broken, I got error in 5
different tests related to you select.select call:
TypeError: argument must be an int, or
SilentGhost added the comment:
That was a testing issue, apparently test.test_httplib.FakeSocket is not fake
enough.
--
___
Python tracker
<http://bugs.python.org/issue25
SilentGhost added the comment:
All the tests pass now, not sure why your patch doesn't get associated rietveld
link, it applies cleanly using hg patch --no-commit
--
___
Python tracker
<http://bugs.python.org/is
SilentGhost added the comment:
With the default branch I get regular TypeError exception, without any extras.
To me it seems that its responsibility of the caller to provide the correct
callback for the type of data being retrieved. So, I'm not exactly sure that
this is a bug a
901 - 1000 of 1410 matches
Mail list logo
