[issue16058] ConfigParser no longer deepcopy compatible in 2.7

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 ___

[issue26665] pip is not bootstrapped by default on 2.7

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

[issue26697] tkFileDialog crash on askopenfilename Python 2.7 64-bit Win7

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 status: open -> closed ___ Pyth

[issue26652] Cannot install Python 2.7.11 on Windows Server 2008 R2

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 status: open -> closed ___ Pyt

[issue40394] difflib.SequenceMatcher.find_longest_match default arguments

Tim Peters added the comment: Sounds good to me, Lewis - thanks! Note, though, that alo and blo should default to 0. `None` is best reserved for cases where the default value needs to be computed at runtime. But alo == blo == 0 apply to all possible instances. --

[issue26326] Named entity "vertical line" missed in 2.7 htmlentitydefs.py

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 tracker

[issue14418] Document differences in SocketServer between Python 2.6 and 2.7

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

[issue34884] Python may load incorrect libraries when embedding the macOS system python 2.7

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 tracker

[issue27435] ctypes library loading and AIX - also for 2.7.X (and later)

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

[issue31297] Unpickleable ModuleImportError in unittest patch not backported to 2.7

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

[issue18493] make profile-opt fails with pre-existing python2.7 in path

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: -> fixed stage: -> resol

[issue30967] Crash in PyThread_ReInitTLS() in the child process after os.fork() on CentOS 6.5 (Python 2.7.13)

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: open -> closed ___ Pyth

[issue29640] _PyThreadState_Init and fork race leads to inconsistent key list

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 ___

[issue11955] 3.3 : test_argparse.py fails 'make test'

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 ___ Python tracker

[issue15192] test_bufio failures on Win64 buildbot

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 tracker

[issue40404] Python quit unexpectedly

New submission from Joseph : Process: Python [91080] Path: /usr/local/Cellar/python/3.7.7/Frameworks/Python.framework/Versions/3.7/Resources/Python.app/Contents/MacOS/Python Identifier:Python Version: 3.7.7 (3.7.7) Code Type:

[issue8940] *HTTPServer need a summary page with API inheritance table

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 "languishing" statu

[issue15426] On a x86_64 Linux workstation, the build-from-source is borked.

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

[issue22866] ssl module in 2.7 should provide a way to configure default context options

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 __

[issue7101] tarfile: OSError with TarFile.add(..., recursive=True) about non-existing file

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

[issue15028] PySys_SetArgv escapes quotes in argv[]

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 _

[issue40404] Python quit unexpectedly

Ned Deily added the comment: I'm sorry you are seeing that crash but I'm afraid it is difficult to know exactly what is going here without more information. It appears you are using a Python 3.7.7 from Homebrew along with NumPy and other similar third-party packages from somewhere. The macOS

[issue40404] Python quit unexpectedly

Joseph added the comment: Sorry I should've added more context. I recently re-installed python on my computer and started getting these errors. It's hard to pinpoint when I get the error exactly, but I find it happens when I shutdown a Jupyter notebook. I'm wondering if this may be alluded t

[issue40404] Python quit unexpectedly

Ned Deily added the comment: Thanks for the additional info but that still does not really narrow things down much. You don't say how you upgraded Python (from where, from what previous version) nor how you obtained NumPy or Juypter. If you didn't already, I would suggest trying to upgrade a

[issue40272] ModuleNotFoundEror thrown by system python while accessing it specifically via venv python

Ned Deily added the comment: Without more information, in particular, a reproducible test case, we can only speculate what might be going on. Suggest you try using some of the debugging tools Python includes, starting with invoking your virtualenv python with the -vv flag. As described here

[issue39966] mock 3.9 bug: Wrapped objects without __bool__ raise exception

Chris Withers added the comment: I'd go with your instincts on what to do next, I'd have a slight preference to keeping behaviour the same as it was in 3.8 if the changes for 3.9 cause more problems. That leaves us no worse off than we were before, and with the opportunity to improve from th

<    1   2