Change by Zachary Ware :
--
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Zachary Ware added the comment:
As 2.7 has now reached end-of-life and with it the last version to support
Windows XP, I'm closing the issue.
--
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python t
Zachary Ware added the comment:
Hi Willie,
Sorry this never got attention before 2.7 reached end-of-life, but as that has
now happened, I'm closing the issue.
That said, I suspect your issue here was with library search path; it wasn't
actually 2.7.5 that was installed by the
Zachary Ware added the comment:
As 2.7 has reached end-of-life, I'm closing the issue.
--
nosy: +zach.ware
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.pyth
Zachary Ware added the comment:
In the intervening 8 years since there was last activity in this issue, zlib
1.2.11 has been released and probably has even more new features. However, I
think rather than looking for new features to implement, we should create
specific issues to implement
Zachary Ware added the comment:
Given that you both nearly agreed to "wont fix" 8 years ago and 2.7 is now EOL,
I'm going to go ahead and close the issue that way :)
--
nosy: +zach.ware
resolution: -> wont fix
stage: -> resolved
s
Zachary Ware added the comment:
As 2.7 has reached EOL, I'm going to go ahead and close the issue.
--
nosy: +zach.ware
resolution: -> out of date
stage: needs patch -> resolved
status: open -> closed
___
Python tracker
<https:
Zachary Ware added the comment:
As 2.7 has now reached EOL, I'm going to go ahead and close the issue. Sorry
this never got attention, but I'm glad you found a workaround!
--
nosy: +zach.ware
resolution: -> out of date
stage: -> resolved
status
Zachary Ware added the comment:
Sorry this issue never got attention, but Python 2.7 has now reached
end-of-life and with it the _bsddb module. As such, I'm going to go ahead and
close this issue.
--
nosy: +zach.ware
resolution: -> out of date
stage: -> resolved
s
Zachary Ware added the comment:
As 2.7 is now EOL, I'm closing the issue.
--
nosy: +zach.ware
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.pyth
Zachary Ware added the comment:
Given that #18976 was said to have fixed this and is now closed as "fixed", and
every tagged version is now EOL, I'm closing the issue.
--
nosy: +zach.ware
resolution: -> out of date
stage: test needed -> resolved
s
Zachary Ware added the comment:
As Python 2.7 is now EOL and was the last remaining version to support OS/2,
I'm closing the issue.
--
nosy: +zach.ware
resolution: -> out of date
stage: test needed -> resolved
status: open -> closed
Zachary Ware added the comment:
As 2.7 is EOL and the bundled copy of libffi no longer exists, I'm closing the
issue.
--
nosy: +zach.ware
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python t
Zachary Ware added the comment:
Hi Richard, sorry it too so long for anyone to respond to this issue! It's
been long enough that I'm going to assume that this has long since been fixed
or worked around. However, if you can still reproduce this with a modern
version of Python (3.
Zachary Ware added the comment:
As 2.7 has now reached EOL, I'm closing the issue.
--
nosy: +zach.ware
resolution: -> out of date
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.pyth
Zachary Ware added the comment:
As 2.7 is now EOL, I'm closing this issue.
--
nosy: +zach.ware
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.pyth
Zachary Ware added the comment:
As 2.7 has reached EOL, I'm closing this issue.
--
nosy: +zach.ware
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.pyth
Zachary Ware added the comment:
As 2.7 has reached EOL, I'm closing this issue.
--
nosy: +zach.ware
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.pyth
Zachary Ware added the comment:
As 2.7 is EOL and 3.x use Tcl/Tk 8.6.x, I'm closing this issue.
--
nosy: +zach.ware
resolution: -> out of date
stage: needs patch -> resolved
status: open -> closed
___
Python tracker
<https:
Zachary Ware added the comment:
At a guess, the version of `make` used in your environment was not able to
handle a comment. However, Python 2.7 has now reached end-of-life and as such
I'm closing this issue. If you can still reproduce the issue with a modern
version of Python (3.
Zachary Ware added the comment:
As Python 2.7 is now at end-of-life, I'm closing this issue. If you can still
reproduce the problem with a modern version of Python (3.6-3.8), please reopen
it.
--
nosy: +zach.ware
resolution: -> out of date
stage: -> resolved
s
Zachary Ware added the comment:
Hi Jiebin,
Sorry that nobody was able to respond to this before the end of support for
2.7. However, that version is now EOL, and as such I'm closing this issue.
--
nosy: +zach.ware
resolution: -> out of date
stage: -> resolved
s
Zachary Ware added the comment:
As 2.7 is now EOL, I'm closing the issue.
--
nosy: +zach.ware
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.pyth
Zachary Ware added the comment:
As Python 2.7 has reached EOL, I'm closing this issue. However, if you can
reproduce the problem with a modern version of Python (3.6-3.8), please reopen
it and adjust the versions field appropriately.
--
nosy: +zach.ware
resolution: -> out
Zachary Ware added the comment:
With 2.7 now EOL, I'm closing the issue.
--
nosy: +zach.ware
resolution: -> out of date
stage: test needed -> resolved
status: open -> closed
___
Python tracker
<https://bugs.pyth
Zachary Ware added the comment:
New changeset a494caa14bfa412af77792007c34274902fabb7b by Ammar Askar in branch
'master':
bpo-40401: Remove duplicate pyhash.h include from pythoncore.vcxproj (GH-19725)
https://github.com/python/cpython/commit/a494caa14bfa412af77792007c3427
Zachary Ware added the comment:
Thanks for the patch :)
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Zachary Ware added the comment:
As Python 2.7 has now reached end-of-life, I'm closing the issue. If you can
still reproduce this issue in a modern version of Python (3.6-3.8), please
reopen it and hopefully we can get someone who understands what's going on to
actually
Zachary Ware added the comment:
New changeset b54e46cb57ebac5c525a9a6be241412cd57bc935 by Brad Solomon in
branch 'master':
bpo-38387: Formally document PyDoc_STRVAR and PyDoc_STR macros (GH-16607)
https://github.com/python/cpython/commit/b54e46cb57ebac5c525a9a6be24141
Zachary Ware added the comment:
Thanks for the patch!
--
resolution: -> fixed
stage: -> resolved
status: open -> closed
title: Document PyDoc_STRVAR -> Document PyDoc_STRVAR and PyDoc_STR macros
versions: +Python 3.7, Python 3.8
Change by Zachary Ware :
--
pull_requests: +19049
pull_request: https://github.com/python/cpython/pull/19727
___
Python tracker
<https://bugs.python.org/issue38
Change by Zachary Ware :
--
pull_requests: +19050
pull_request: https://github.com/python/cpython/pull/19728
___
Python tracker
<https://bugs.python.org/issue38
Zachary Ware added the comment:
As Python 2.7 has reached end-of-life and the bsddb module is not shipped with
Python 3, I'm closing the issue.
--
nosy: +zach.ware
resolution: -> out of date
stage: needs patch -> resolved
status: ope
Zachary Ware added the comment:
New changeset ca5649c4c1ab260c8ceb8a57ec703c06e2707986 by Zachary Ware in
branch '3.8':
[3.8] bpo-38387: Formally document PyDoc_STRVAR and PyDoc_STR macros (GH-16607)
(GH-19727)
https://github.com/python/cpyt
Zachary Ware added the comment:
New changeset 70ba81459eeb5818848f86b65cdf78feb86f9612 by Zachary Ware in
branch '3.7':
[3.7] bpo-38387: Formally document PyDoc_STRVAR and PyDoc_STR macros (GH-16607)
(GH-19728)
https://github.com/python/cpyt
Zachary Ware added the comment:
As Python 2.7 has reached end-of-life, I'm closing this issue. As Martin
mentioned, this looks likely to be a duplicate of bpo-17126 anyway.
--
nosy: +zach.ware
___
Python tracker
<https://bugs.py
Change by Zachary Ware :
--
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Zachary Ware added the comment:
As Python 2.7 has now reached end-of-life, I'm closing the issue. gdb support
has seen some significant changes in the interim anyway; it's entirely possible
that this was actually fixed in 2.7 before it died :)
--
nosy: +zach.ware
Zachary Ware added the comment:
As `linux_distribution` was removed in 3.8 (bpo-28167), I'm closing the issue.
Thanks for the patch anyway, Elizabeth, and I'm sorry it didn't end up better!
--
nosy: +zach.ware
resolution: -> out of date
stage: patch review
Zachary Ware added the comment:
With PEP 546 withdrawn/rejected and 2.7 at EOL, I'm closing the issue.
--
nosy: +zach.ware
resolution: -> rejected
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.pyth
Zachary Ware added the comment:
This seems to have been fixed but never closed? Closing it now anyway due to
EOL :)
--
nosy: +zach.ware
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracke
Zachary Ware added the comment:
Superseded by the pythondotorg issue.
--
nosy: +zach.ware
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/i
Zachary Ware added the comment:
As far as I can tell from the commit history associated with this issue this
seems to have not been a bug, so I'm closing it. If anyone disagrees, please
reopen :)
--
nosy: +zach.ware
resolution: -> not a bug
stage: needs patch -> reso
Zachary Ware added the comment:
This seems to have been fixed, so I'm closing it as such. With 2.7 at EOL,
this would be closed anyway, but "fixed" sounds nicer :)
--
nosy: +zach.ware
resolution: -> fixed
stage: patch review -> resolved
s
Change by Zachary Ware :
--
keywords: +newcomer friendly
versions: +Python 3.9 -Python 3.7
___
Python tracker
<https://bugs.python.org/issue31391>
___
___
Pytho
Zachary Ware added the comment:
Hi Gibson,
I'm sorry this issue didn't get any attention before Python 2.7 reached EOL,
but as that milestone has now passed I'm closing the issue. Thank you for the
report anyway!
--
nosy: +zach.ware
resolution: -> out of date
s
Zachary Ware added the comment:
As Python 2.7 has now reached end-of-life, I'm closing the issue.
--
nosy: +zach.ware
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.pyth
Zachary Ware added the comment:
As Python 2.7 has now reached end-of-life, I'm closing the issue.
--
nosy: +zach.ware
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.pyth
Zachary Ware added the comment:
As this appears to be specific to Python 2.7 which has now reached end-of-life,
I'm closing the issue. Thanks for the report anyway, and I'm sorry we couldn't
get it a bit more straightened out before EOL!
--
nosy: +zach.ware
resolut
Zachary Ware added the comment:
With 2.7 now EOL, I'm closing the issue.
--
nosy: +zach.ware
resolution: fixed -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.pyth
Zachary Ware added the comment:
As 2.7 is now EOL, I'm closing the issue. Thanks for the report anyway, Axel!
--
nosy: +zach.ware
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<https:
Zachary Ware added the comment:
As 2.7 is now EOL, I'm closing the issue. Thanks for the report anyway, Eric,
and I'm sorry we didn't get it looked into before now.
--
resolution: -> out of date
stage: -> resolved
s
Zachary Ware added the comment:
Sorry this didn't get any attention before now, but as 2.7 is now EOL there's
nothing we could fix for this, so I'm closing the issue.
--
resolution: -> out of date
stage: -> resolved
s
Zachary Ware added the comment:
With 2.7 now at end-of-life, I'm closing the issue. Thanks for the report
anyway!
--
nosy: +zach.ware
resolution: -> out of date
stage: test needed -> resolved
status: open -> closed
___
Python t
Zachary Ware added the comment:
Since Python 2.7 is now at end-of-life, I'm closing the issue.
--
nosy: +zach.ware
resolution: -> out of date
stage: needs patch -> resolved
status: open -> closed
___
Python tracker
<https:
Zachary Ware added the comment:
With 2.7 now at end-of-life, I'm closing this issue. Thanks for the report
anyway, Tim!
--
nosy: +zach.ware
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python t
Zachary Ware added the comment:
Thanks Michael, finally getting it closed :)
--
nosy: +zach.ware
resolution: -> out of date
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Zachary Ware added the comment:
With 2.7 now EOL, I'm closing the issue.
--
nosy: +zach.ware
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.pyth
Zachary Ware added the comment:
This was fixed in 3.x in 2015 and later backported to 2.7 in 2017. Thanks for
the report, Claudio, and I'm sorry nobody noticed this earlier or we could have
fixed the issue two years earlier!
--
nosy: +zach.ware
resolution: -> fix
Zachary Ware added the comment:
Sorry we didn't really reach a conclusion here, Thomas, but as 2.7 is now EOL
I'm going ahead and closing the issue.
--
nosy: +zach.ware
resolution: -> out of date
stage: -> resolved
status
Zachary Ware added the comment:
As 2.7 is now EOL, I'm closing the issue.
--
nosy: +zach.ware
resolution: -> out of date
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.pyth
Zachary Ware added the comment:
As we've not seen any issues with this on the buildbots, I'm going ahead and
closing it.
--
nosy: +zach.ware
resolution: -> fixed
stage: needs patch -> resolved
status: pending -> closed
___
Pyt
Zachary Ware added the comment:
I've not seen this issue on that worker for a very long time; closing the issue.
--
nosy: +zach.ware
resolution: -> out of date
stage: -> resolved
status: pending -> closed
___
Python t
Zachary Ware added the comment:
Lacking a clearer description of exactly what should be changed and with an
official warning in the docs against using the http.server module in
production, I'm going to go ahead and close the issue (which happened to be the
last issue with "l
Zachary Ware added the comment:
This appears to have likely been addressed by bpo-1294959 and/or other issues
over the years.
--
nosy: +zach.ware
stage: patch review -> resolved
status: pending -> closed
___
Python tracker
Zachary Ware added the comment:
With 2.7 now EOL, I'm closing the issue.
--
nosy: +zach.ware
resolution: -> out of date
stage: needs patch -> resolved
status: pending -> closed
___
Python tracker
<https://bugs.pyth
Zachary Ware added the comment:
I agree with Sandro; this should be handled at application level.
--
nosy: +zach.ware
resolution: -> not a bug
stage: -> resolved
status: languishing -> closed
___
Python tracker
<https://bugs.python.o
Zachary Ware added the comment:
Lacking a response from the OP, I'm closing the issue.
--
nosy: +zach.ware
resolution: -> not a bug
stage: -> resolved
status: languishing -> closed
___
Python tracker
<https://bugs.pyth
Zachary Ware added the comment:
With 2.7 out of support, closing.
--
nosy: +zach.ware
resolution: -> out of date
stage: needs patch -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.o
Zachary Ware added the comment:
I say merge it :)
--
nosy: +zach.ware
___
Python tracker
<https://bugs.python.org/issue40517>
___
___
Python-bugs-list mailin
Zachary Ware added the comment:
Just a note to add my full support for what Steve said. PATH is frequently
abused on Windows, and we only have the option at all because people become
unreasonably upset if it's not there. I wouldn't be against adding a "you
don't act
Zachary Ware added the comment:
That redirect just didn't exist yet :). It now does, and I went ahead and
added it for 3.9 ahead of time.
--
nosy: +zach.ware
___
Python tracker
<https://bugs.python.org/is
Zachary Ware added the comment:
This can be accomplished already by just including newlines in the string:
$ cat multiline_python_bash_script.sh
#!/bin/bash
python3 -c '
from math import *
print(e**(1j * pi))
import sys
print(sys.argv)'
echo "here's some random
Change by Zachary Ware :
--
nosy: +jaraco, lemburg
___
Python tracker
<https://bugs.python.org/issue40570>
___
___
Python-bugs-list mailing list
Unsubscribe:
Zachary Ware added the comment:
This looks like a simple reference cycle, as far as I can tell; I don't see an
actual refleak. Reproducing using Mark's code from StackOverflow (adjusted):
$ ./python.exe -X showrefcount
Python 3.9.0a6+ (heads/master-dirty:d10091aa17, May 8 2020
Change by Zachary Ware :
--
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Change by Zachary Ware :
--
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Zachary Ware added the comment:
I'm in favor of this.
I especially want this with the self-name-checking that Eryk mentioned, and
even more if each installed Python adds its own symlink to `py.exe` with its
own version (i.e. the Python 3.9 installer adds `python3.9.exe -> py.exe`
Zachary Ware added the comment:
`hashlib` is part of the standard library and thus does not need to be (and
should not be :)) installed via pip.
--
nosy: +zach.ware
resolution: -> not a bug
stage: -> resolved
status: open -> closed
_
Zachary Ware added the comment:
Thanks for the report, bazwal; for the patch, Zackery; and for the ping Ammar :)
--
nosy: +zach.ware
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
type: enhancement -&
Zachary Ware added the comment:
It seems possible that the fetch of the Tcl/Tk binaries failed somehow; you can
try removing the entire `externals` directory (or just anything in it that
includes `tcl` or `tk`); you can use `PCbuild\get_externals.bat --clean` to do
so
Zachary Ware added the comment:
That line on its own will cause an IndentationError, which is a subclass of
SyntaxError. However, out of context, without the full traceback, and without
a description of your environment, the only thing I have to go on here is the
fact that the vast
Change by Zachary Ware :
--
nosy: +eric.araujo, zach.ware
___
Python tracker
<https://bugs.python.org/issue43049>
___
___
Python-bugs-list mailing list
Unsub
Zachary Ware added the comment:
Looks like that link could be safely removed from our docs. Would you like to
submit a pull request doing so?
--
nosy: +berker.peksag, erlendaasland, zach.ware
___
Python tracker
<https://bugs.python.
Change by Zachary Ware :
--
assignee: -> steve.dower
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
___
Python tracker
<https://bugs.python.org/issu
Change by Zachary Ware :
--
nosy: +paul.j3, rhettinger
___
Python tracker
<https://bugs.python.org/issue43169>
___
___
Python-bugs-list mailing list
Unsubscribe:
Zachary Ware added the comment:
Can reproduce on Linux:
$ for python in /usr/bin/python3.? /usr/local/bin/python3.?
do
$python -VV
$python -m timeit -r 10 -n 100_000 -u usec -s 'S = set(range(10_000))'
'S.remove(5000);S.add(5000)'
done
Python 3.8.5 (default, J
Zachary Ware added the comment:
That looks more like `_sqlite3.pyd` is missing. You're sure no changes have
been to the installation directory? Does repairing the installation help at
all?
I imagine we would have been flooded with issue reports if the installer was
missing this m
Change by Zachary Ware :
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue43211>
___
___
Zachary Ware added the comment:
New changeset b36349a647b2bf8174f0e736a4fc347e92ae204e by Peter Donis in branch
'master':
bpo-43049: Use io.IncrementalNewlineDecoder for doctest newline conversion
(GH-24359)
https://github.com/python/cpython/commit/b36349a647b2bf8174f0e736a4fc34
Zachary Ware added the comment:
Thanks for the patch!
--
components: +Library (Lib) -Tests
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
versions: -Python 3.7, Python 3.8, Python 3.9
___
Python tracke
Zachary Ware added the comment:
New changeset b36349a647b2bf8174f0e736a4fc347e92ae204e by Peter Donis in branch
'master':
bpo-43049: Use io.IncrementalNewlineDecoder for doctest newline conversion
(GH-24359)
https://github.com/python/cpython/commit/b36349a647b2bf8174f0e736a4fc34
Change by Zachary Ware :
Removed file: https://bugs.python.org/file49847/tac.eml
___
Python tracker
<https://bugs.python.org/issue36480>
___
___
Python-bugs-list mailin
Change by Zachary Ware :
--
keywords: +easy -easy (C), patch
___
Python tracker
<https://bugs.python.org/issue43075>
___
___
Python-bugs-list mailing list
Unsub
Change by Zachary Ware :
--
keywords: +patch
___
Python tracker
<https://bugs.python.org/issue43075>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Zachary Ware :
--
nosy: +berker.peksag, erlendaasland
___
Python tracker
<https://bugs.python.org/issue43440>
___
___
Python-bugs-list mailin
Zachary Ware added the comment:
I don't see anything broken here: `__file__` is "scripts/test.py",
`Path(__file__).parent` is "scripts", and `__file__` doesn't change just
because the working directory changed (it's a static string set at import time,
wh
Zachary Ware added the comment:
Absent anyone showing me where a proper refleak is here, I'm closing the issue.
--
resolution: -> works for me
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.pyth
Zachary Ware added the comment:
Adding multiprocessing and concurrent.futures experts.
--
components: -Tests
nosy: +bquinlan, davin, pitrou
versions: +Python 3.10 -Python 3.9
___
Python tracker
<https://bugs.python.org/issue40
Change by Zachary Ware :
--
components: +Library (Lib), Tests -asyncio
___
Python tracker
<https://bugs.python.org/issue40692>
___
___
Python-bugs-list mailin
401 - 500 of 2740 matches
Mail list logo