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
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:
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
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:
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:
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:
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:
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:
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
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 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
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:
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:
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
Change by Zachary Ware :
--
pull_requests: +19050
pull_request: https://github.com/python/cpython/pull/19728
___
Python tracker
<https://bugs.python.org/issue38
Change by Zachary Ware :
--
pull_requests: +19049
pull_request: https://github.com/python/cpython/pull/19727
___
Python tracker
<https://bugs.python.org/issue38
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
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:
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:
Thanks for the patch :)
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
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:
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:
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:
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:
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 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:
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 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:
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 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 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:
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 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:
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:
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 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:
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 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:
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:
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:
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:
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:
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 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
Change by Zachary Ware :
--
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Zachary Ware added the comment:
With no other context, I'm going to assume this was specific to 2.7, which is
now out of support.
--
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python t
Zachary Ware added the comment:
As all versions using the MSI installer are now out of support, I'm closing the
issue.
--
nosy: +zach.ware
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python t
Zachary Ware added the comment:
It's not entirely clear from a quick read whether this was actually fixed or
not (probably?), but as 2.7 is out of support it no longer matters :)
--
nosy: +zach.ware
resolution: -> out of date
status: open -
Zachary Ware added the comment:
As 2.7 is now out of support, I'm going to go ahead and close this issue.
--
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.pyth
Zachary Ware added the comment:
As 2.7 is now out of support, 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 t
Zachary Ware added the comment:
Sorry I missed this one! This was actually addressed in bpo-30342 (GH-1544),
but it would have been fixed 7 months sooner if this one hadn't fallen off my
radar. Thanks for the patch anyway!
--
resolution: -> fixed
stage: -> resolved
s
Zachary Ware added the comment:
As this appears to be a 2.7-only issue, I'm going to go ahead and close it.
--
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.pyth
Change by Zachary Ware :
--
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Zachary Ware added the comment:
Hi Sven,
I'm sorry this issue never got attention before the end of 2.7, but as we have
now reached that point I'm going to go ahead and close this issue. I hope it
didn't cause you too much trouble! If you can also reproduce this with a
cur
Zachary Ware added the comment:
Looks like we forgot to close this one; as far as I can tell it was fixed.
Being 2.7-only, it's time to be closed anyway :)
--
resolution: -> fixed
stage: test needed -> resolved
status: open -> closed
Zachary Ware added the comment:
As this issue is specific to 2.7, I'm closing it.
--
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.pyth
Zachary Ware added the comment:
With no activity here in over 5 years and no confirmation on any version but
2.7, I'm closing the issue. If it can be confirmed on 3.8, the issue can be
reopened.
--
nosy: +zach.ware
resolution: -> out of date
stage: -> resolved
s
Change by Zachary Ware :
--
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue38601>
___
___
Python-bugs-list
Zachary Ware added the comment:
Lacking followup from the OP, I'm closing the issue. If more information is
brought forward later, it can be reopened.
--
___
Python tracker
<https://bugs.python.org/is
Change by Zachary Ware :
--
resolution: -> out of date
stage: needs patch -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Zachary Ware added the comment:
Are you quite sure you're converting your times correctly, particularly in the
C code? The units in the Python version should be seconds; does the C version
actually take 23 seconds to execute? What kind of timing do you get if you
time both programs
Change by Zachary Ware :
--
nosy: +alanmcintyre, serhiy.storchaka, twouters
___
Python tracker
<https://bugs.python.org/issue40301>
___
___
Python-bugs-list m
Zachary Ware added the comment:
This has been done in the macOS installer since
9625bf520e08828e36bc3b1d043af679eb5f993d, so this is now done. I won't
backport it due to the inevitable confusion over which patch version of which
branch started including it on Windows; it's much
Zachary Ware added the comment:
New changeset 58d6f2ee3aeb699156d4784acccd2910d27982e7 by Ammar Askar in branch
'master':
bpo-40270: Enable json extension in Windows sqlite extension (GH-19528)
https://github.com/python/cpython/commit/58d6f2ee3aeb699156d4784acccd29
Change by Zachary Ware :
--
nosy: -zach.ware
___
Python tracker
<https://bugs.python.org/issue39598>
___
___
Python-bugs-list mailing list
Unsubscribe:
Zachary Ware added the comment:
Maybe I'm just paranoid, but this whole issue reads like spam to me. It's at
least a spam magnet; changing the title accordingly and clearing the nosy list.
--
nosy: -Sahurkhan, gustavoxo, judiction, nows, paul.moore, steve.dower,
tim.gold
Change by Zachary Ware :
--
components: +Library (Lib) -Distutils
nosy: +rhettinger -dstufft, eric.araujo
stage: -> test needed
___
Python tracker
<https://bugs.python.org/issu
Zachary Ware added the comment:
Feel free to backport PR19404 as needed, but mark versions here appropriately
to make sure the *real* fix makes it where it needs to go.
--
___
Python tracker
<https://bugs.python.org/issue40
Zachary Ware added the comment:
Assuming I implemented my checks correctly (see PR19413), I think I've just
debunked both of our leading theories.
Results here:
https://dev.azure.com/Python/cpython/_build/results?buildId=60764&view=logs&j=d554cd63-f8f4-5b2d-871b-33e4ea76e915&am
Change by Zachary Ware :
--
pull_requests: +18773
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/19413
___
Python tracker
<https://bugs.python.org/issu
Change by Zachary Ware :
--
stage: patch review -> needs patch
___
Python tracker
<https://bugs.python.org/issue40214>
___
___
Python-bugs-list mailing list
Un
Zachary Ware added the comment:
New changeset f407e209c1e35b64835f73e7e7ca23e33817e9fe by Zachary Ware in
branch 'master':
bpo-40214: Temporarily disable a ctypes test (GH-19404)
https://github.com/python/cpython/commit/f407e209c1e35b64835f73e7e7ca23
Change by Zachary Ware :
--
stage: -> patch review
type: -> behavior
___
Python tracker
<https://bugs.python.org/issue40214>
___
___
Python-bugs-list
Zachary Ware added the comment:
My best guess at the moment is that something changed in the underlying Windows
image, particularly given the comment above the failing line that "insecure
load flags should succeed" (though that could easily be a red herring). Until
someone wh
Change by Zachary Ware :
--
keywords: +patch
nosy: +zach.ware
nosy_count: 1.0 -> 2.0
pull_requests: +18768
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/19404
___
Python tracker
<https://bugs.python.org/i
Zachary Ware added the comment:
How about `python3 -c 'import
sysconfig;print(sysconfig.get_config_vars()["CONFIG_ARGS"])'`?
--
nosy: +zach.ware
___
Python tracker
<https://bug
Zachary Ware added the comment:
12 years later, we finally landed your fix :). Thanks for the patch, and for
bearing with us (and me in particular for the past couple months).
As mentioned in the PR, there is probably opportunity to clean up the cleanup
code in the new test a bit, and as
Zachary Ware added the comment:
New changeset e0b8101492f6c61dee831425b4d3dae39a953599 by Peter Donis in branch
'master':
bpo-1812: Fix newline conversion when doctest.testfile loads from a package
whose loader has a get_data method (GH-17385)
https://github.com/python/cpyt
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:
New changeset 59c644eaa72b0cc48302f59d66852c4ea8332eba by Lahfa Samy in branch
'master':
bpo-39879: Update datamodel docs to include dict ordering (GH-19006)
https://github.com/python/cpython/commit/59c644eaa72b0cc48302f59d66852c
Change by Zachary Ware :
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue40008>
___
___
Change by Zachary Ware :
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue40009>
___
___
Change by Zachary Ware :
--
nosy: -Jack Reigns
title: Best Mac Cleaner Apps to Optimize and Speed up your Mac -> Spam
type: performance ->
___
Python tracker
<https://bugs.python.org/i
Change by Zachary Ware :
--
Removed message: https://bugs.python.org/msg364572
___
Python tracker
<https://bugs.python.org/issue40009>
___
___
Python-bugs-list m
Change by Zachary Ware :
Removed file: https://bugs.python.org/file48981/MacOptimizerPro.jpg
___
Python tracker
<https://bugs.python.org/issue40009>
___
___
Python-bug
Change by Zachary Ware :
--
Removed message: https://bugs.python.org/msg364570
___
Python tracker
<https://bugs.python.org/issue40008>
___
___
Python-bugs-list m
Change by Zachary Ware :
Removed file: https://bugs.python.org/file48980/MacOptimizerPro.jpg
___
Python tracker
<https://bugs.python.org/issue40008>
___
___
Python-bug
Change by Zachary Ware :
--
nosy: -Jack Reigns
title: Best Mac Cleaner Software and Optimization Utilities -> Spam
type: performance ->
___
Python tracker
<https://bugs.python.org/i
Zachary Ware added the comment:
Hi Furkan. Please note that Lahfa Samy had already submitted a PR for this
issue after "claiming" it with a note here; proper "netiquette" suggests not
jumping in with your own PR in such a situation.
Fortuitously though, it looks like
Zachary Ware added the comment:
I'm personally still in favor of the change. This wouldn't be the first big
movement of files in our repo and likely not the last, and I don't think
git/GitHub's support (or lack thereof) for file moves is a good enough reason
to not or
Zachary Ware added the comment:
(FTR, removing yourself from the "nosy list" means you won't get any responses
to your issue, so I've added you back :))
This appears to be a problem with building Tcl/Tk. If you don't need the
tkinter module, you can try adding t
Zachary Ware added the comment:
Is this not a Sphinx issue?
--
nosy: +zach.ware
___
Python tracker
<https://bugs.python.org/issue39814>
___
___
Python-bug
Zachary Ware added the comment:
That almost certainly means you were installing the 32-bit version of Python.
32-bit processes see `C:\Program Files (x86)\` as `C:\Program Files\`; I no
longer remember whether they can actually see the real `C:\Program Files\` at
all
Zachary Ware added the comment:
Agreed with Eric.
--
nosy: +zach.ware
resolution: -> rejected
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Change by Zachary Ware :
--
nosy: +zach.ware
___
Python tracker
<https://bugs.python.org/issue1812>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Zachary Ware :
--
nosy: +eric.smith
___
Python tracker
<https://bugs.python.org/issue39601>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Zachary Ware :
--
components: -2to3 (2.x to 3.x conversion tool)
___
Python tracker
<https://bugs.python.org/issue39601>
___
___
Python-bugs-list m
Zachary Ware added the comment:
What result are you expecting here?
--
nosy: +zach.ware
___
Python tracker
<https://bugs.python.org/issue39601>
___
___
Pytho
Change by Zachary Ware :
--
stage: -> resolved
status: pending -> closed
___
Python tracker
<https://bugs.python.org/issue39597>
___
___
Python-bugs-list
301 - 400 of 2740 matches
Mail list logo