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 tracker <
Changes by SilentGhost <ghost@gmail.com>:
--
stage: -> needs patch
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25810>
___
_
Changes by SilentGhost <ghost@gmail.com>:
--
nosy: +larry
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25810>
___
__
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 <rep...@bugs.python.org>
<http://bugs.python.org/i
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.
--
versions
Changes by SilentGhost <ghost@gmail.com>:
--
components: +Library (Lib)
nosy: +benjamin.peterson, brett.cannon, georg.brandl, ncoghlan
stage: -> test needed
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by SilentGhost <ghost@gmail.com>:
--
nosy: +SilentGhost
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue19475>
___
_
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: open -&g
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.peterson, br
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
&quo
Changes by SilentGhost <ghost@gmail.com>:
--
nosy: +alexandre.vassalotti, pitrou
type: crash -> behavior
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by SilentGhost <ghost@gmail.com>:
--
components: +Windows
keywords: +needs review -patch
nosy: +paul.moore, steve.dower
versions: +Python 3.6 -Python 3.5
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pytho
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 <ghost@gmail.com>:
--
components: +IDLE, Macintosh, Tkinter
nosy: +gpolo, ned.deily, ronaldoussoren, serhiy.storchaka
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
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/issue25852.diff
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: +Library (Lib) -Interpreter
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 sentences
SilentGhost added the comment:
The host ip needs to be supplied as a string:
telnetlib.Telnet(host='192.168.1.15', port=3490, timeout=5)
--
nosy: +SilentGhost
resolution: -> not a bug
stage: -> resolved
status: open -> closed
type: -&
Changes by SilentGhost <ghost@gmail.com>:
--
stage: patch review -> commit review
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by SilentGhost <ghost@gmail.com>:
Added file: http://bugs.python.org/file41466/issue25916_4.diff
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
SilentGhost added the comment:
Here is the updated patch.
--
Added file: http://bugs.python.org/file41465/issue25916_3.diff
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Changes by SilentGhost <ghost@gmail.com>:
--
components: +Interpreter Core -Argument Clinic
versions: -Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@gmail.com>:
--
nosy: +steven.daprano
versions: -Python 3.4
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
SilentGhost added the comment:
Could you provide us with a sample file that demonstrates this behaviour?
--
nosy: +SilentGhost
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
SilentGhost added the comment:
Arithmetic operations should not be used with booleans, they happen to work due
to boolean bean a subclass of int.
--
nosy: +SilentGhost
resolution: -> not a bug
stage: -> resolved
status: open -> closed
type: -&
SilentGhost added the comment:
Please use stackoverflow or python-tutor list to get help on this.
https://mail.python.org/pipermail/tutor/
What it looks like is the problem with your text editor not being able to
support EOL characters from a different OS.
--
nosy: +SilentGhost
SilentGhost added the comment:
Christof, you'd have to demonstrate the issue in more than just words. The
returned status code is hard-coded to be 2 in the error method and it does end
up being 2 when i run, could you post some output that led you to believe that
it is 1?
--
nosy
Changes by SilentGhost <ghost@gmail.com>:
--
nosy: +meador.inge
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25977>
___
_
Changes by SilentGhost <ghost@gmail.com>:
--
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bu
SilentGhost added the comment:
> It seems to me, that this change in python is not nessesary.
> I don't, know how to find the commit, message who has changed this and why.
It was done in issue 13598. It's a bit puzzling that IPython decided to depend
on behaviour of a private metho
SilentGhost added the comment:
It behaves exactly as described in documentation, the only thing I could
suggest is to re-read the following for details:
https://docs.python.org/3/library/os.path.html#os.path.split
--
nosy: +SilentGhost
resolution: -> not a bug
stage: -> re
Changes by SilentGhost <ghost@gmail.com>:
--
components: +Library (Lib) -IO
versions: +Python 3.5, Python 3.6 -Python 3.4
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
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 <rep...@bugs.python.org>
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 have
SilentGhost added the comment:
That was a testing issue, apparently test.test_httplib.FakeSocket is not fake
enough.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
SilentGhost added the comment:
Content of the article is in very reasonable shape, I have only couple of notes:
1. I don't think "production" is a good description of the python's repository
workflow, so I'd suggest changing it to "repository".
2. Lack of links: inst
Changes by SilentGhost <ghost@gmail.com>:
--
components: +Installation, Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
versions: +Python 3.5
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@gmail.com>:
--
nosy: +alex, christian.heimes, dstufft, giampaolo.rodola, janssen, pitrou
type: -> behavior
versions: +Python 3.5, Python 3.6 -Python 3.4
___
Python tracker <rep...@bugs.pytho
Changes by SilentGhost <ghost@gmail.com>:
--
components: +Library (Lib)
nosy: +yselivanov
versions: +Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
SilentGhost added the comment:
Well, at least on the surface of it, the fix seems pretty straightforward:
check for the group index. With this patch the behaviour is as expected, but I
get two tests erroring out since they're expecting differently worded error.
This probably needs adjustments
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
___
SilentGhost added the comment:
Martin, could you please escape * in Misc/NEWS, it causes a warning when
building documentation.
--
nosy: +SilentGhost
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
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
Changes by SilentGhost <ghost@gmail.com>:
--
resolution: -> duplicate
stage: -> resolved
superseder: -> TextIOWrapper: issues with interlaced read-write
type: -> behavior
___
Python tracker <rep...@bugs.python.org>
SilentGhost added the comment:
None of this warnings highlights a real issue. Furthermore, optparse module is
deprecated and you'd be better off using argparse instead.
--
components: +Library (Lib)
nosy: +SilentGhost
resolution: -> not a bug
stage: -> resolved
status: open -&g
SilentGhost added the comment:
The deprecation warning is clearly displayed at the top of the module
documentation: https://docs.python.org/3/library/optparse.html
Regarding variable names: it is not an issue and pychecker is simply mistaken
here
SilentGhost added the comment:
The code was introduced to solve issue 12494, so I'm adding Victor to weigh in.
--
nosy: +SilentGhost, haypo
versions: +Python 3.5, Python 3.6 -Python 3.3
___
Python tracker <rep...@bugs.python.org>
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 at all
SilentGhost added the comment:
OK, here is the patch with the test that I think is exercising the issue.
--
keywords: +needs review, patch
stage: -> patch review
Added file: http://bugs.python.org/file41403/issue25933.diff
___
Python tracker &
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 <rep...@bugs.python.org>
<http://bugs.python.org/i
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 are http->https redir
Changes by SilentGhost <ghost@gmail.com>:
--
stage: needs patch -> patch review
Added file: http://bugs.python.org/file41362/output.txt
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
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 tracker <
Changes by SilentGhost <ghost@gmail.com>:
--
components: +Interpreter Core
versions: +Python 3.5, Python 3.6 -Python 3.4
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@gmail.com>:
--
components: +Windows
nosy: +brett.cannon, eric.snow, steve.dower, tim.golden, zach.ware
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@gmail.com>:
--
components: +Build, Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
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 <rep...@bugs.python.
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 <rep...@bugs.python.
Changes by SilentGhost <ghost@gmail.com>:
--
nosy: +vinay.sajip
stage: -> patch review
versions: +Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
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-standard
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 replacing simple &
SilentGhost added the comment:
Here is the updated version of the patch that addresses Senthil's comments.
Besides re-flowing code, I've also added enforcement of --summary switch and
re-factored and expanded the test_failures. It probably would be good if
someone could test this on a real
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +pmoody
versions: -Python 3.3, Python 3.4
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Tests
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27277>
___
_
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +amaury.forgeotdarc, belopolsky, meador.inge
versions: +Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
SilentGhost added the comment:
test_format resulted in semi-failure due to this change. The attached patch
fixes the issue.
--
assignee: -> serhiy.storchaka
nosy: +SilentGhost
resolution: fixed ->
stage: resolved -> commit review
status: closed -> open
Adde
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +SilentGhost
versions: +Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +alex, christian.heimes, dstufft, giampaolo.rodola, janssen, pitrou
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@runbox.com>:
--
stage: -> needs patch
type: -> behavior
versions: -Python 3.2, Python 3.3, Python 3.4
___
Python tracker <rep...@bugs.python.org>
<http://bugs.
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +vinay.sajip
stage: -> test needed
type: -> behavior
versions: +Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http://bugs.
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +georg.brandl
stage: -> patch review
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by SilentGhost <ghost@runbox.com>:
--
versions: +Python 3.6 -Python 3.5
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +SilentGhost
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue20825>
___
_
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +loewis
stage: -> patch review
versions: -Python 2.7, Python 3.2, Python 3.3, Python 3.4
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by SilentGhost <ghost@runbox.com>:
--
stage: patch review -> commit review
versions: -Python 3.2, Python 3.3, Python 3.4
___
Python tracker <rep...@bugs.python.org>
<http://bugs.py
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Interpreter Core
nosy: +serhiy.storchaka
stage: -> patch review
type: enhancement -> behavior
___
Python tracker <rep...@bugs.python.org>
<http://bugs.
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +rhettinger, stutzbach
type: -> enhancement
versions: +Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
SilentGhost added the comment:
LGTM.
--
stage: needs patch -> commit review
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27306>
___
___
SilentGhost added the comment:
pip is not part of standard library, its issue tracker is at
https://github.com/pypa/pip/issues
--
nosy: +SilentGhost
resolution: -> third party
stage: -> resolved
status: open -> closed
___
Python tra
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +georg.brandl
type: crash -> behavior
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
SilentGhost added the comment:
I cannot reproduce this issue on 3.5, do you have a chance to test this on a
3.5 or some other version of python? Also, could you provide any more details
of your system?
--
nosy: +SilentGhost
___
Python tracker <
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +alanmcintyre, serhiy.storchaka, twouters
versions: +Python 3.6 -Python 2.7
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@runbox.com>:
--
resolution: -> works for me
stage: -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bu
SilentGhost added the comment:
There are more occurrences of "it is already exists" in the first table.
--
nosy: +SilentGhost
stage: -> needs patch
versions: +Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http://bugs
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Extension Modules -Interpreter Core
nosy: +larry
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Tests
title: Yury isn't sure comprehensions and await interact correctly ->
Comprehensions and await need more unittests
type: -> behavior
___
Python tracker <rep...@
SilentGhost added the comment:
Thanks for the patch, Dave. For whatever reason it doesn't seem to apply
cleanly to the current tip, would you mind preparing a new patch that does?
--
assignee: -> docs@python
components: +Documentation
nosy: +SilentGhost, berker.peksag, docs@pyt
SilentGhost added the comment:
There seems to be an issue with your patch, it does apply cleanly when doing
that manually, but Rietveld doesn't like it. The changes in Lib/posixpath.py
and Lib/test/test_posixpath.py don't show up.
--
nosy: +SilentGhost
SilentGhost added the comment:
This is behaviour introduced by issue 25548, it would make sense to me to
discuss this problem there if you think it's necessary. repr in error messages
has been a standard approach in Python for a very long time, however.
--
nosy: +SilentGhost
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Library (Lib)
nosy: +r.david.murray
stage: -> test needed
type: -> behavior
versions: -Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5
___
Python
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +steven.daprano
stage: -> patch review
type: -> behavior
___
Python tracker <rep...@bugs.python.org>
<http://bugs.
Changes by SilentGhost <ghost@runbox.com>:
--
stage: -> patch review
versions: -Python 3.2, Python 3.3, Python 3.4
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
SilentGhost added the comment:
I closed the issue because it's outdated: i) patch no longer applies cleanly;
ii) changes to cmd line parsing where done in issue 22642; iii) remaining
changes are largely cosmetic.
As for issue 10896, a much more trivial patch would have to be produced against
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +haypo, rhettinger
stage: -> patch review
versions: +Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by SilentGhost <ghost@runbox.com>:
--
assignee: -> yselivanov
stage: patch review -> commit review
___
Python tracker <rep...@bugs.python.org>
<http://bugs.
New submission from SilentGhost:
This could only go in 3.6, but it needs proper documentation and test(s).
--
nosy: +SilentGhost, yselivanov
stage: -> test needed
versions: -Python 3.5
___
Python tracker <rep...@bugs.python.org&
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +pitrou
type: -> behavior
versions: -Python 3.5
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +ezio.melotti, michael.foord, rbcollins
versions: +Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Library (Lib) -Demos and Tools
nosy: +vinay.sajip
versions: -Python 3.2, Python 3.3, Python 3.4, Python 3.5
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
301 - 400 of 1379 matches
Mail list logo
