SilentGhost added the comment:
your example actually produces '/abc//def/'.
However, I'm not sure where do you get the idea that it should clean up
internal directory separators or do anything at all with the strings in paths.
To me it reads like it's concatenating arg
Change by SilentGhost :
--
nosy: +alanmcintyre, serhiy.storchaka, twouters
___
Python tracker
<https://bugs.python.org/issue32170>
___
___
Python-bugs-list mailin
Change by SilentGhost :
--
nosy: +belopolsky
versions: +Python 3.7
___
Python tracker
<https://bugs.python.org/issue31839>
___
___
Python-bugs-list mailin
Change by SilentGhost :
--
nosy: +amaury.forgeotdarc, belopolsky, meador.inge
___
Python tracker
<https://bugs.python.org/issue31654>
___
___
Python-bugs-list m
SilentGhost added the comment:
> can I work on this and fix the remaining links?
Please do.
--
___
Python tracker
<http://bugs.python.org/issue25910>
___
_
SilentGhost added the comment:
Can't reproduce this on 3.7, can you supply additional information, such as
what exact revision you're trying to build and what gcc version you're using?
------
nosy: +SilentGhost
___
Python
SilentGhost added the comment:
The main message there is about the parsing of the two-digit year, so while it
might worth it to remove the mention of Y2K, it would only be a minor change.
--
nosy: +SilentGhost
___
Python tracker
<h
Changes by SilentGhost :
--
assignee: -> docs@python
components: +Documentation
nosy: +docs@python
stage: -> patch review
type: -> behavior
versions: +Python 3.5, Python 3.6, Python 3.7
___
Python tracker
<http://bugs.python.or
SilentGhost added the comment:
ContextBaseClass is meant to represent a user-defined class that is a parent of
mycontext.
--
nosy: +SilentGhost
___
Python tracker
<http://bugs.python.org/issue29
SilentGhost added the comment:
Cannot reproduce this with the tip on linux
--
___
Python tracker
<http://bugs.python.org/issue29097>
___
___
Python-bugs-list m
Changes by SilentGhost :
--
components: +Windows
nosy: +belopolsky, paul.moore, steve.dower, tim.golden, zach.ware
stage: -> needs patch
type: -> behavior
___
Python tracker
<http://bugs.python.org/i
SilentGhost added the comment:
This doesn't seem likely that it's anything to do with datetime, could you try
reproducing it in repl?
--
nosy: +SilentGhost
___
Python tracker
<http://bugs.python.o
Changes by SilentGhost :
--
nosy: +eric.smith
type: -> behavior
___
Python tracker
<http://bugs.python.org/issue29104>
___
___
Python-bugs-list mailing list
Un
SilentGhost added the comment:
This is the wrong bug tracker. The issue seems to have already been reported to
pypa https://github.com/pypa/pypi-legacy/issues/492
--
nosy: +SilentGhost
resolution: -> not a bug
stage: -> resolved
status: open -> closed
type: performance -&
SilentGhost added the comment:
The ResourceWarning that you've introduced need to be "fixed" in a few place in
test_urllib2
--
stage: -> needs patch
versions: +Python 3.7
___
Python tracker
<http://bugs.
SilentGhost added the comment:
> The point of ResourceWarning it tell you when you are depending on
> destructors for cleanup
But there is an explicit call in __del__ to .close(), it's looks like intended
behaviour and is ultimately the difference that Jon was see
SilentGhost added the comment:
It's part of the copyright notice, just removing it is probably not an option.
--
nosy: +SilentGhost
___
Python tracker
<http://bugs.python.org/is
SilentGhost added the comment:
Looking at the code it seems NamedTemporaryFile is closed on destruction of the
object, so there is no need for ResourceWarning, because the file descriptor is
not leaking.
You also don't need to involve unittest here. Just running python with -Wall
Changes by SilentGhost :
--
nosy: +orsenthil
versions: +Python 3.5, Python 3.6, Python 3.7 -Python 3.4
___
Python tracker
<http://bugs.python.org/issue28
SilentGhost added the comment:
You seem to be misunderstanding how the intersection/union/etc are supposed to
be used:
>>> ab = {'a', 'b'}
>>> ab.intersection('bc')
{'b'}
Using set.intersection (where set is a built-in class, rather th
Changes by SilentGhost :
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue28830>
___
___
SilentGhost added the comment:
Reads just fine to me.
--
nosy: +SilentGhost
___
Python tracker
<http://bugs.python.org/issue28830>
___
___
Python-bugs-list mailin
Changes by SilentGhost :
--
stage: -> resolved
___
Python tracker
<http://bugs.python.org/issue28819>
___
___
Python-bugs-list mailing list
Unsubscrib
SilentGhost added the comment:
What do you mean by "work" and "does not work"? Both versions raise TypeError,
because you're passing epoch to fromtimestamp, but once that's fixed both
versions return identical output. Python is not sensitive to empty lines in
Changes by SilentGhost :
--
resolution: -> out of date
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
Changes by SilentGhost :
--
resolution: not a bug -> third party
stage: -> resolved
___
Python tracker
<http://bugs.python.org/issue28772>
___
___
Pyth
SilentGhost added the comment:
I get either ('ec2-54-88-107-140.compute-1.amazonaws.com', [],
['54.88.107.140']) or ('ec2-54-84-80-173.compute-1.amazonaws.com', [],
['54.84.80.173']).
It indeed seems to be related to ISP, as I get a regular socket.gai
New submission from SilentGhost:
Couple of entries in Misc/NEWS are causing warnings due to use of double quotes
instead of backticks for code segments. This patches fixes the formatting.
--
assignee: docs@python
components: Documentation
files: escape.diff
keywords: patch
messages
SilentGhost added the comment:
> Does test_host_resolution still stably fails?
Yes.
--
___
Python tracker
<http://bugs.python.org/issue28728>
___
___
Python-
SilentGhost added the comment:
> My guess is you have a plugin which is resolving these ip-address lookalikes.
That probably is the reason. My hosts line looks like:
hosts: files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return]
dns
I guess there isn't much that
Changes by SilentGhost :
--
nosy: +michael.foord
versions: +Python 3.6, Python 3.7
___
Python tracker
<http://bugs.python.org/issue28735>
___
___
Python-bug
SilentGhost added the comment:
Of course, you're right, that was my mistake. The last three addresses fail to
raise, namely: '::1q', '::1::2' and '1:1:1:1:1:1:1:1:1'.
--
stage: patch review ->
title: test_host_resolution in
Changes by SilentGhost :
Removed file: http://bugs.python.org/file45524/test_socket.diff
___
Python tracker
<http://bugs.python.org/issue28728>
___
___
Python-bugs-list m
New submission from SilentGhost:
Commit 540a9c69c2ea introduced double assertRaises which now is failing on
ubuntu 16.10
If it is necessary, then it's not obvious why and there is no comment, but here
is the one-line patch that removes the duplicated line and makes the test pass
f
SilentGhost added the comment:
Ten subtest in test_re fail with
TypeError: unhashable type: '_sre.SRE_Pattern'
--
nosy: +SilentGhost
___
Python tracker
<http://bugs.python.o
SilentGhost added the comment:
Buildbots fail since _ANDROID_API_LEVEL could end up being None
--
nosy: +SilentGhost
status: closed -> open
___
Python tracker
<http://bugs.python.org/issu
Changes by SilentGhost :
--
stage: -> resolved
___
Python tracker
<http://bugs.python.org/issue28632>
___
___
Python-bugs-list mailing list
Unsubscrib
SilentGhost added the comment:
No, the module works exactly as advertised. The default value of quoting
parameter might not be suitable for this file, but it suits majority of files
out there. The fields in csv can contain line feed, so the line in your example
does not have a "missing&q
Changes by SilentGhost :
--
stage: -> resolved
___
Python tracker
<http://bugs.python.org/issue28642>
___
___
Python-bugs-list mailing list
Unsubscrib
SilentGhost added the comment:
so using quoting=csv.QUOTE_NONE should solve the immediate problem of "losing"
lines then, I'm not sure csv module ever supported dealing with corrupted files.
--
___
Python tracker
<http://bugs.pyt
SilentGhost added the comment:
Could you perhaps make the smaller file make available somewhere?
--
nosy: +SilentGhost
___
Python tracker
<http://bugs.python.org/issue28
Changes by SilentGhost :
--
nosy: +mark.dickinson
stage: -> patch review
___
Python tracker
<http://bugs.python.org/issue28621>
___
___
Python-bugs-list mai
Changes by SilentGhost :
--
nosy: +eric.smith
___
Python tracker
<http://bugs.python.org/issue28590>
___
___
Python-bugs-list mailing list
Unsubscribe:
SilentGhost added the comment:
That's how IEEE 754's NaN is defined. Seem to be behaving according to the
standard.
--
nosy: +SilentGhost
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Py
SilentGhost added the comment:
The same is on 3.5.2 on ubuntu 16.10
--
nosy: +SilentGhost, larry
versions: +Python 3.5
___
Python tracker
<http://bugs.python.org/issue28
Changes by SilentGhost :
--
components: -XML
___
Python tracker
<http://bugs.python.org/issue28513>
___
___
Python-bugs-list mailing list
Unsubscribe:
SilentGhost added the comment:
sys.version is a string, it's intended to be printed and it needs \n to be able
to output two lines. I'm not sure what exactly problem you're having, but if
you want special characters like \n not to show in output, you should use
>>>
SilentGhost added the comment:
And how exactly are you "hitting sys.version command"?
--
nosy: +SilentGhost
versions: -Python 3.4
___
Python tracker
<http://bugs.python.o
SilentGhost added the comment:
> Apparently (haven’t tried myself) if you put “.. program:: zipfile” before
> the :option: invocations, it changes the default context and you don’t need
> the bit.
Yes, moving program directive just after "Command Line Interface"
SilentGhost added the comment:
The fix could be as small as the attached patched, though I'm not sure that is
the correct way of handling 101 code.
--
keywords: +patch
nosy: +SilentGhost
Added file: http://bugs.python.org/file45296/28570
SilentGhost added the comment:
Serhiy, this needs .. program:: zipfile directive specified before cmdoption.
Without it :option:`-c` links to python's -c, rather than zipfile's. The -l and
-e are linked correctly, but the option links would have be be changed for all
three, i.e.
Changes by SilentGhost :
--
components: +macOS
nosy: +ned.deily, ronaldoussoren
___
Python tracker
<http://bugs.python.org/issue28567>
___
___
Python-bugs-list m
SilentGhost added the comment:
According to documentation %z is the only directive that would result in the
aware object. %Z is not capable of doing that, so what you're asking is a new
feature - that could only go in 3.7
--
components: +Library (Lib)
nosy: +SilentGhost
Changes by SilentGhost :
--
nosy: +loewis
___
Python tracker
<http://bugs.python.org/issue28563>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by SilentGhost :
--
resolution: wont fix -> rejected
stage: -> resolved
___
Python tracker
<http://bugs.python.org/issue28560>
___
___
Python-bugs-
SilentGhost added the comment:
Do you mean that /foo was just an arbitrary string, rather than one of the
parent directories? Because in that case it seems a perfectly correct way to go
about comparison. If /foo was one of the parents, there are plenty of options:
.parts, .parents
SilentGhost added the comment:
Patch (v3) is fine, except it no longer applies cleanly. I have a patch
against the tip which I could upload if needed.
I would also be in favour of disabling the unittest options directly, currently
no link is generated and it doesn't seem like there
SilentGhost added the comment:
Here is the patch that fixes warning in /Doc/howto/instrumentation.rst as well
as cleans up a few nits here and there. I've removed attempt at highlighting
using c since that doesn't work in practice.
--
keywords: +patch
nosy: +berker.pe
SilentGhost added the comment:
Building the documentation on Ubuntu 16.10, I started getting the following
warnings:
/Doc/howto/instrumentation.rst:58: WARNING: Could not lex literal_block as
"python3". Highlighting skipped.
/Doc/howto/instrumentation.rst:139: WARNING: Cou
Changes by SilentGhost :
--
status: open -> pending
___
Python tracker
<http://bugs.python.org/issue28514>
___
___
Python-bugs-list mailing list
Unsubscrib
SilentGhost added the comment:
Updated patch fixing the position issue.
--
Added file: http://bugs.python.org/file45194/25953_5.diff
___
Python tracker
<http://bugs.python.org/issue25
SilentGhost added the comment:
I've modified addgroup to take a pos argument, this seem to introduce minimal
disturbance.
--
Added file: http://bugs.python.org/file45187/25953_4.diff
___
Python tracker
<http://bugs.python.org/is
SilentGhost added the comment:
Updated patch taking Serhiy's comments into account.
There was another case on line 725 for when zero is used as a group number, I'm
not sure though if it falls within the scope of this issue, so it's not
included in the current patch.
Changes by SilentGhost :
--
stage: -> commit review
versions: +Python 3.5, Python 3.6, Python 3.7 -Python 3.4
___
Python tracker
<http://bugs.python.org/issu
Changes by SilentGhost :
--
components: +Build
type: -> behavior
versions: +Python 3.6
___
Python tracker
<http://bugs.python.org/issue28478>
___
___
Python-
Changes by SilentGhost :
--
resolution: -> duplicate
stage: -> resolved
status: open -> closed
superseder: -> Python -V and --version output to stderr instead of stdout
___
Python tracker
<http://bugs.python
SilentGhost added the comment:
Here is the updated patch with fixes to the test suite.
--
versions: +Python 3.7
Added file: http://bugs.python.org/file45113/25953_2.diff
___
Python tracker
<http://bugs.python.org/issue25
SilentGhost added the comment:
On python2 you should be able to use Cookie module to parse cookies, rather
than doing that manually. Commas are handled correctly there. On python3 the
same functionality can be found in http.cookies.
The SimpleCookie.load could be used directly to have the
Changes by SilentGhost :
--
nosy: +alexandre.vassalotti
___
Python tracker
<http://bugs.python.org/issue28416>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from SilentGhost:
Couple of headings in whatsnew/3.6.rst have wrong level. The patch fixes this.
--
assignee: docs@python
components: Documentation
files: headings.diff
keywords: patch
messages: 278296
nosy: SilentGhost, docs@python
priority: normal
severity: normal
stage
Changes by SilentGhost :
--
components: +Extension Modules
nosy: +christian.heimes
type: -> behavior
___
Python tracker
<http://bugs.python.org/issu
SilentGhost added the comment:
Could you please post an example of what you're being sent from the server and
how your code handles / fails to deal with it.
--
nosy: +SilentGhost
stage: -> test needed
versions: +Python 2.7
___
Python tracke
Changes by SilentGhost :
--
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
type: -> behavior
___
Python tracker
<http://bugs.python.org/issu
Changes by SilentGhost :
--
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
___
Python tracker
<http://bugs.python.org/issue28
Changes by SilentGhost :
--
stage: -> resolved
___
Python tracker
<http://bugs.python.org/issue28345>
___
___
Python-bugs-list mailing list
Unsubscrib
SilentGhost added the comment:
It doesn't matter what you're unpacking, *y will collect the unpacked elements
into a list.
--
components: +Interpreter Core -Regular Expressions
nosy: +SilentGhost
resolution: -> not a bug
stage: -> resolved
status
SilentGhost added the comment:
Serhiy, your patch doesn't seem to apply cleanly. Also, it's perhaps worth
opening the issue if you'd like to continue working on it.
------
nosy: +SilentGhost
___
Python tracker
<http://bugs.pyt
SilentGhost added the comment:
LGTM
--
assignee: -> docs@python
components: +Documentation
nosy: +SilentGhost, docs@python
stage: -> commit review
type: -> behavior
versions: +Python 3.6
___
Python tracker
<http://bugs.python.or
SilentGhost added the comment:
Jaysinh, you can upload your modified patch, so it can be reviewed.
--
___
Python tracker
<http://bugs.python.org/issue28
Changes by SilentGhost :
--
resolution: -> fixed
status: open -> closed
type: -> behavior
___
Python tracker
<http://bugs.python.org/issue17206>
___
SilentGhost added the comment:
It would be good to add a FAQ / HowTo entry for this question.
--
nosy: +SilentGhost
___
Python tracker
<http://bugs.python.org/issue28
Changes by SilentGhost :
--
stage: -> patch review
type: enhancement -> behavior
versions: +Python 3.6
___
Python tracker
<http://bugs.python.org/i
Changes by SilentGhost :
--
versions: +Python 3.7
___
Python tracker
<http://bugs.python.org/issue28197>
___
___
Python-bugs-list mailing list
Unsubscribe:
SilentGhost added the comment:
Neither of those fit under definition of "permissible" modules. So, I would
then suggest to close this issue and any further issues against CLI of those
modules.
--
___
Python tracker
<http://bu
SilentGhost added the comment:
Given that at present zipfile CLI has no test or docs, and along with Guido's
aversion for such tools in general, I'm not at all sure they should be added.
In any case, here is the patch for the main part of conversion.
--
keywords: +patch
st
Changes by SilentGhost :
--
stage: -> patch review
___
Python tracker
<http://bugs.python.org/issue28172>
___
___
Python-bugs-list mailing list
Unsubscrib
SilentGhost added the comment:
It's not an error. Read the docs, there's a longer and more detailed
explanation there. There is no chance of this being changed, not in a module
like getopt.
--
___
Python tracker
<http://bugs.python.o
SilentGhost added the comment:
It's a documented behaviour: "Long options on the command line can be
recognized so long as they provide a prefix of the option name that matches
exactly one of the accepted options"
------
nosy: +SilentGhost
resolution: -> not a bug
s
Changes by SilentGhost :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue28155>
___
___
Python-bugs-list mailing list
Unsubscrib
SilentGhost added the comment:
The space between -m switch and module name is not mandatory as you should be
able to see if you run those examples.
--
nosy: +SilentGhost
resolution: -> not a bug
stage: -> resolved
___
Python tracker
Changes by SilentGhost :
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
type: -> behavior
___
Python tracker
<http://bugs.python
Changes by SilentGhost :
--
nosy: -gukaar77
title: really and truly -> spam
___
Python tracker
<http://bugs.python.org/issue28133>
___
___
Python-bugs-list mai
Changes by SilentGhost :
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue28133>
___
___
Changes by SilentGhost :
--
Removed message: http://bugs.python.org/msg276324
___
Python tracker
<http://bugs.python.org/issue28133>
___
___
Python-bugs-list m
Changes by SilentGhost :
--
nosy: +yselivanov
___
Python tracker
<http://bugs.python.org/issue28121>
___
___
Python-bugs-list mailing list
Unsubscribe:
SilentGhost added the comment:
It seems to be also related to #23545 (Martin saw a similar warning about a
month ago).
--
nosy: +SilentGhost, martin.panter, serhiy.storchaka
___
Python tracker
<http://bugs.python.org/issue28
SilentGhost added the comment:
The status code in all those cases should have been 2.
--
nosy: +SilentGhost
___
Python tracker
<http://bugs.python.org/issue28
SilentGhost added the comment:
The commit didn't resolve the warning though.
--
nosy: +SilentGhost
___
Python tracker
<http://bugs.python.org/issue23545>
___
___
Changes by SilentGhost :
--
resolution: -> fixed
stage: -> resolved
___
Python tracker
<http://bugs.python.org/issue17884>
___
___
Python-bugs-list
SilentGhost added the comment:
Probably, not for a particularly good reason, but none of the near-by code in
_ssl.c seemed relevant on superficial inspection. The commit 02c8db9c255f which
modified Include/pymem.h didn't have an issue associated wi
501 - 600 of 1410 matches
Mail list logo
