[issue38351] Modernize email example from %-formatting to f-string

Fred L. Drake, Jr. added the comment: I'd like to see consistent usage by default, with specific examples using the older forms as appropriate. The use cases Raymond identified are worth discussing (and the tutorial may be a good place for this), and well as mentioned in the reference docs

[issue38351] Modernize email example from %-formatting to f-string

Kyle Stanley added the comment: > For the most part, templating examples can be switched to the .format() style > but shouldn't be switched to f-strings. Is there no specific use case for the older "%s" % sub template that .format() doesn't have? > The former technique is still necessary

[issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode

Terry J. Reedy added the comment: The revised PR appears to fix this and other issues, although the presence of astral chars in code being edited messes up tk's cursor positioning. Assuming that this cannot be changed, we could add the the ability to replace astral chars with \U escapes.

[issue38356] test_asyncio: SubprocessThreadedWatcherTests leaks threads

Change by Kyle Stanley : -- keywords: +patch pull_requests: +16140 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16552 ___ Python tracker ___

[issue38333] add type signatures to library function docs

paul rubin added the comment: abs takes any value that understands the __abs__ method and returns something of the same type. In fact there is already a type protocol for it: https://mypy.readthedocs.io/en/stable/protocols.html#supportsabs-t So abs's signature would be (x : Abs[T]) -> T

[issue38351] Modernize email example from %-formatting to f-string

Raymond Hettinger added the comment: > (Not that I can think of others off the top of my head.) For the most part, templating examples can be switched to the .format() style but shouldn't be switched to f-strings. The former technique is still necessary if someone wants to move templates

[issue38356] test_asyncio: SubprocessThreadedWatcherTests leaks threads

Kyle Stanley added the comment: > Another consideration is if we want this method to join the threads to be > called in `ThreadedChildWatcher.close()`. An additional benefit of having the method called from `close()` is that it means we don't have to modify the tests directly. Also,

[issue38356] test_asyncio: SubprocessThreadedWatcherTests leaks threads

Kyle Stanley added the comment: First I'll work on adding a new method. Here's a few potential names, ordered roughly by my preferences: 1) join_threads() 2) shutdown_threads() 3) shutdown_threadpool() The first and second options are roughly equal, but I think join_threads() is a bit

[issue38333] add type signatures to library function docs

Vedran Čačić added the comment: In that case, I'm pretty sure you'd never be able to document almost _any_ function signature. Python is simply not a statically typed language, and we love it because of that. Ok, go to the list of builtins, and start alphabetically. First is abs. What type

[issue38350] ./configure --with-pydebug should use -O0 rather than -Og

Charalampos Stratakis added the comment: It seems that it's still being worked on from gcc's side: https://gcc.gnu.org/bugzilla//show_bug.cgi?id=78685 -- ___ Python tracker

[issue38357] print adding extra bytes in hex above x7F

Artificial added the comment: Thanks, Arfrever Seems unnecessarily complicated for what worked in Python2. -- ___ Python tracker ___

[issue38351] Modernize email example from %-formatting to f-string

Fred L. Drake, Jr. added the comment: Definitely agree with Eric on this; code modernization is definitely on the risky side, so judicious updates are important. (Of course, not updating is also a risk, eventually. But not much of one in this case.) This issue is really about whether the

[issue38357] print adding extra bytes in hex above x7F

Arfrever Frehtes Taifersar Arahesis added the comment: However print() called with non-str argument would firstly call str() on it, which is most likely not what reporter wanted: >>> print(b'\x80') b'\x80' >>> str(b"\x80") "b'\\x80'" >>> print(str(b"\x80")) b'\x80' $ python -c

[issue38350] ./configure --with-pydebug should use -O0 rather than -Og

Benjamin Peterson added the comment: If -Og is breaking debugging, isn't that a compiler bug? The GCC manpage claims " -Og enables optimizations that do not interfere with debugging." -- nosy: +benjamin.peterson ___ Python tracker

[issue38351] Modernize email example from %-formatting to f-string

Eric V. Smith added the comment: >> I definitely think we should not modify any code in the stdlib just to >> switch to f-strings. > Does this also apply to updating code to use f-strings in an area that's > already being modified for a functional purpose? No. As I said, not just to

[issue38357] print adding extra bytes in hex above x7F

Ammar Askar added the comment: If you're trying to get raw bytes, you need to use print(b'\x80') what's happening right now is that the '\x80' is treated as a unicode code point (see https://docs.python.org/3/howto/unicode.html#the-string-type), and when Python goes to print it, it

[issue38352] In typing docs, note explicit import needed for IO and Pattern/Match

Change by Karthikeyan Singaravelan : -- nosy: +gvanrossum, levkivskyi ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue38357] print adding extra bytes in hex above x7F

Artificial added the comment: python3 -c "print('\x7F')" > test.txt && xxd test.txt : 7f0a .. python3 -c "print('\x80')" > test.txt && xxd test.txt : c280 0a ... --

[issue38354] Fix for bug 30378 regressed SysLogHandler by making it resolve addresses at initialization instead of in `.emit()`

Change by Karthikeyan Singaravelan : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38350] ./configure --with-pydebug should use -O0 rather than -Og

Charalampos Stratakis added the comment: Correction, not fail, just a ton of warnings. The same is true for -D_FORTIFY_SOURCE=1 -- ___ Python tracker ___

[issue38351] Modernize email example from %-formatting to f-string

Kyle Stanley added the comment: > I definitely think we should not modify any code in the stdlib just to switch > to f-strings. Does this also apply to updating code to use f-strings in an area that's already being modified for a functional purpose? I agree that that we shouldn't update

[issue38357] print adding extra bytes in hex above x7F

New submission from Artificial : Any hex str of value above \x7F causes an extra byte to printed. -- files: Screenshot from 2019-10-02 20-31-50.png messages: 353796 nosy: Artificial priority: normal severity: normal status: open title: print adding extra bytes in hex above x7F type:

[issue38350] ./configure --with-pydebug should use -O0 rather than -Og

Charalampos Stratakis added the comment: Do note though that if the -D_FORTIFY_SOURCE=2 hardening flag is used, the compilation will fail with an optimization level less than -Og. Haven't tried yet with -D_FORTIFY_SOURCE=1 to see if it works with -O0. -- nosy: +cstratak

[issue38342] ImportError: cannot import name 'MetadataPathFinder' from 'importlib.metadata'

Change by Dima Tisnek : -- nosy: +Dima.Tisnek ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38351] Modernize email example from %-formatting to f-string

Eric V. Smith added the comment: I definitely think we should not modify any code in the stdlib just to switch to f-strings. I think the code examples in the docs would benefit from a consistent style, and since f-strings are the least verbose way to format strings, I'd endorse using them

[issue19683] test_minidom has many empty tests

karl added the comment: @zach.ware @r.david.murray So I was looking at that issue. There is a lot of work. I had a couple of questions, because there are different categories # Empty tests for existing functions. This seems to be straightforward as they would complete the module.

[issue38356] test_asyncio: SubprocessThreadedWatcherTests leaks threads

Kyle Stanley added the comment: I can try to work on fixing this. -- nosy: +aeros167 ___ Python tracker ___ ___ Python-bugs-list

[issue38351] Modernize email example from %-formatting to f-string

Kyle Stanley added the comment: > so it would be a good candidate for the "newcomer friendly" label Never mind, just noticed this was already labeled as newcomer friendly. I only saw the "easy" label at first. (: If consensus is reached for this, we can open a separate issue for addressing

[issue38351] Modernize email example from %-formatting to f-string

Kyle Stanley added the comment: Welcome back from the OOOS break Mariatta! > My question (and it's just that) is whether we've made a decision to prefer > one formatting syntax over others (outside of examples discussing the > formatting approaches themselves). I agree that we should reach

[issue38318] Issues linking with ncurses and tinfo (cannot resolve symbols)

Michael Everitt added the comment: Attached patch seems to fix build with python3.6 withh uclibc-ng. Tested on x86_64 and ARMv6zk. -- Added file: https://bugs.python.org/file48640/fix-tinfo-probably-python-3_6.patch ___ Python tracker

[issue38318] Issues linking with ncurses and tinfo (cannot resolve symbols)

Michael Everitt added the comment: Attached patch seems to fix build failure for python2.7 with uclibc-ng. -- keywords: +patch Added file: https://bugs.python.org/file48639/fix-tinfo-probably-python-2_7.patch ___ Python tracker

[issue38351] Modernize email example from %-formatting to f-string

Fred L. Drake, Jr. added the comment: I agree that it's less invasive and easier to review. My question (and it's just that) is whether we've made a decision to prefer one formatting syntax over others (outside of examples discussing the formatting approaches themselves). If a decision is

[issue36670] regrtest: win_utils decodes typeperf output from the wrong encoding (test suite broken due to cpu usage feature on win 10/ german)

STINNER Victor added the comment: New changeset 3e04cd268ee9a57f95dc78d8974b21a6fac3f666 by Victor Stinner in branch 'master': bpo-36670, regrtest: Fix WindowsLoadTracker() for partial line (GH-16550) https://github.com/python/cpython/commit/3e04cd268ee9a57f95dc78d8974b21a6fac3f666

[issue37631] EXTRA_CFLAGS get overrided by CFLAGS_NODIST

Charalampos Stratakis added the comment: Also this is due to an expected behaviour from gcc. From the documentation: "If you use multiple -O options, with or without level numbers, the last such option is the one that is effective. " -- ___

[issue38356] test_asyncio: SubprocessThreadedWatcherTests leaks threads

Change by STINNER Victor : -- nosy: +pablogsal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38356] test_asyncio: SubprocessThreadedWatcherTests leaks threads

New submission from STINNER Victor : Warning seen o AMD64 Ubuntu Shared 3.x buildbot: https://buildbot.python.org/all/#/builders/141/builds/2593 test_devnull_output (test.test_a=syncio.test_subprocess.SubprocessThreadedWatcherTests) ... Warning -- threading_cleanup() failed to cleanup 1

[issue38355] ntpath.realpath() fails on sys.executable

Change by Steve Dower : -- keywords: +patch pull_requests: +16139 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16551 ___ Python tracker ___

[issue36670] regrtest: win_utils decodes typeperf output from the wrong encoding (test suite broken due to cpu usage feature on win 10/ german)

STINNER Victor added the comment: Ok, I managed to reproduce the bug using this change: diff --git a/Lib/test/libregrtest/win_utils.py b/Lib/test/libregrtest/win_utils.py index f0c17b906f..78429faa89 100644 --- a/Lib/test/libregrtest/win_utils.py +++ b/Lib/test/libregrtest/win_utils.py @@

[issue36670] regrtest: win_utils decodes typeperf output from the wrong encoding (test suite broken due to cpu usage feature on win 10/ german)

Change by STINNER Victor : -- pull_requests: +16138 pull_request: https://github.com/python/cpython/pull/16550 ___ Python tracker ___

[issue38355] ntpath.realpath() fails on sys.executable

New submission from Steve Dower : The change to error handling did not include ERROR_CANT_ACCESS_FILE, but this error occurs in the Store package install. After suppressing this error, it then occurs again when stripping the prefix - we should just check for the same error here to determine

[issue37631] EXTRA_CFLAGS get overrided by CFLAGS_NODIST

Charalampos Stratakis added the comment: Dug a bit further here. The issue is that CFLAGS_NODIST will always come after normal CFLAGS (which are subsets of PY_CFLAGS and PY_CFLAGS_NODIST) [0][1]. The EXTRA_CFLAGS variable is appended at the end of PY_CFLAGS [2], hence as reported here,

[issue38354] Fix for bug 30378 regressed SysLogHandler by making it resolve addresses at initialization instead of in `.emit()`

Enji Cooper added the comment: Capturing more context here, based on internal discussion: other handlers are doing address resolution in `emit()` (HTTPHandler, SMTPHandler), which is expensive. In order for SysLogHandler to not regress behavior and not become expensive, performance-wise, it

[issue36670] regrtest: win_utils decodes typeperf output from the wrong encoding (test suite broken due to cpu usage feature on win 10/ german)

David Bolen added the comment: I've confirmed the partial read with some local modifications, and the failures are always split between time stamp and value: Warning -- Failed to parse typeperf output: '"10/02/2019 17:42:26.229"' 0.0 Warning -- Missing first field: ,"0.00" 0.0 Adding

[issue38333] add type signatures to library function docs

Guido van Rossum added the comment: @phr To be clear, I agree that there's nothing wrong with adding signatures to docs. We just need to find a way to do it. There will definitely be some cases where it's better not to have a type rather than trying to spell out the actual type in the

[issue38353] Cleanup the path configuration implementation code (getpath.c)

Change by STINNER Victor : -- pull_requests: +16137 pull_request: https://github.com/python/cpython/pull/16549 ___ Python tracker ___

[issue38353] Cleanup the path configuration implementation code (getpath.c)

STINNER Victor added the comment: New changeset 61691d833631fed42b86605b09e1535e3e8d40e5 by Victor Stinner in branch 'master': bpo-38353: Cleanup includes in the internal C API (GH-16548) https://github.com/python/cpython/commit/61691d833631fed42b86605b09e1535e3e8d40e5 --

[issue38333] add type signatures to library function docs

paul rubin added the comment: Yes, the suggestion was just for the docs, and since those are intended for human rather than machine consumption, it's fine if there are some blurry cases where there is no signature. Ideally in those cases, the issue should be explained in the doc text. I

[issue38354] Fix for bug 30378 regressed SysLogHandler by making it resolve addresses at initialization instead of in `.emit()`

Change by Enji Cooper : -- title: Fix for bug 30378 regressed SysLogHandler -> Fix for bug 30378 regressed SysLogHandler by making it resolve addresses at initialization instead of in `.emit()` ___ Python tracker

[issue38354] Fix for bug 30378 regressed SysLogHandler

New submission from Enji Cooper : The change made for bug 30378 caused a regression in our code by making lookups for SysLogHandler addresses at init time, instead of making them more lazy. Example: >>> import logging.handlers >>> LOGGER = logging.getLogger("logger") >>>

[issue38353] Cleanup the path configuration implementation code (getpath.c)

Change by STINNER Victor : -- keywords: +patch pull_requests: +16136 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16548 ___ Python tracker ___

[issue38353] Cleanup the path configuration implementation code (getpath.c)

New submission from STINNER Victor : Place holder issue for changes related to path configuration cleanup changes (Modules/getpath.c). -- components: Interpreter Core messages: 353774 nosy: vstinner priority: normal severity: normal status: open title: Cleanup the path configuration

[issue38014] Python 3.7 does not compile

Matej Cepl added the comment: Sorry, got confused. My openSUSE bug has nothing to do with it. -- ___ Python tracker ___ ___

[issue36670] regrtest: win_utils decodes typeperf output from the wrong encoding (test suite broken due to cpu usage feature on win 10/ german)

David Bolen added the comment: Oh, I agree it's just a warning, and I suspect few people look into warnings, but since it's not from an actual test, I'm not sure the overall build should be flagged. The manual typeperf looks fine, but there's no way I could tell visually how the I/O is

[issue38014] Python 3.7 does not compile

Matej Cepl added the comment: Isn’t https://bugzilla.suse.com/1152793 (removal of stropts.h from glibc) cause of this? -- nosy: +mcepl ___ Python tracker ___

[issue36670] regrtest: win_utils decodes typeperf output from the wrong encoding (test suite broken due to cpu usage feature on win 10/ german)

STINNER Victor added the comment: > Just an FYI that this change is generating warnings on my Windows 10 buildbot > with some regularity about a failure to parse testperf output, such as: Warning -- Failed to parse typeperf output: '"10/01/2019 07:58:50.056"' Aha, interesting. I added a

[issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode

Serhiy Storchaka added the comment: Sorry, I did not test the last version on Windows. There was a bug which caused using the Linux version on Windows. Now it should be fixed. -- ___ Python tracker

[issue36670] regrtest: win_utils decodes typeperf output from the wrong encoding (test suite broken due to cpu usage feature on win 10/ german)

David Bolen added the comment: Just an FYI that this change is generating warnings on my Windows 10 buildbot with some regularity about a failure to parse testperf output, such as: Warning -- Failed to parse typeperf output: '"10/01/2019 07:58:50.056"' from

[issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode

Tal Einat added the comment: More info: >>> '\N{PERSONAL COMPUTER}'.encode('utf-8').decode('latin-1') == '💻' True -- ___ Python tracker ___

[issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode

Tal Einat added the comment: Not sure if this helps, but a bit of experimentation brought this up: >>> '\N{PERSONAL COMPUTER}'.encode('utf-8') b'\xf0\x9f\x92\xbb' >>> '💻'.encode('utf-16le') b'\xf0\x00\x9f\x00\x92\x00\xbb\x00' >>> '💻'.encode('utf-16')

[issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode

Tal Einat added the comment: Serhiy, this looks like a great step in the right direction! Tested on Win10 with PR GH-16545 (commit f4db0e7e00). Here is a copy/paste from an IDLE shell session: >>> '\N{PERSONAL COMPUTER}' '💻' >>> print('') SyntaxError: 'utf-8' codec can't encode

[issue38344] activate.bat else needs to be on the same line as the if

Steve Dower added the comment: Also adding Ned - this made it into 3.7 as well. -- nosy: +ned.deily versions: +Python 3.7 ___ Python tracker ___

[issue38352] In typing docs, note explicit import needed for IO and Pattern/Match

New submission from Karl Kornel : Hello! In https://github.com/python/cpython/blob/master/Lib/typing.py#L115-L117, there is a note about the io and re classes not being included in typing.__all__. I am a relatively new user of typing, and I did `from typing import *` in my code. I ran the

[issue38351] Modernize email example from %-formatting to f-string

Mariatta added the comment: I think updating one isolated code example is less invasive and easier to review, instead of one big PR to change everything from "%s" to str.format or f-string. I brought up this example code merely because I happen to be reading this page. --

[issue22214] Tkinter: Don't stringify callback arguments

Change by Serhiy Storchaka : -- Removed message: https://bugs.python.org/msg353759 ___ Python tracker ___ ___ Python-bugs-list

[issue22214] Tkinter: Don't stringify callback arguments

Change by Serhiy Storchaka : -- Removed message: https://bugs.python.org/msg353760 ___ Python tracker ___ ___ Python-bugs-list

[issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode

Serhiy Storchaka added the comment: PR 16545 solves the problem by using OS specific methods for converting between Python and Tcl strings. It is not ideal, but is good enough for most real cases. Now you can paste, copy and print non-BMP characters. The code containing them can be displayed

[issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode

Change by Serhiy Storchaka : -- pull_requests: +16135 pull_request: https://github.com/python/cpython/pull/16545 ___ Python tracker ___

[issue22214] Tkinter: Don't stringify callback arguments

Serhiy Storchaka added the comment: Oops, it is better to attach it to issue13153. -- ___ Python tracker ___ ___ Python-bugs-list

[issue22214] Tkinter: Don't stringify callback arguments

Change by Serhiy Storchaka : -- versions: +Python 3.7, Python 3.8, Python 3.9 -Python 3.6 ___ Python tracker ___ ___

[issue22214] Tkinter: Don't stringify callback arguments

Serhiy Storchaka added the comment: PR 16545 solves the problem by using OS specific methods for converting between Python and Tcl strings. It is not ideal, but is good enough for most real cases. Now you can paste, copy and print non-BMP characters. The code containing them can be displayed

[issue38335] simplify overlaps function in ipaddress.py

Change by Sanjay : -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue22214] Tkinter: Don't stringify callback arguments

Change by Serhiy Storchaka : -- pull_requests: +16134 pull_request: https://github.com/python/cpython/pull/16545 ___ Python tracker ___

[issue38344] activate.bat else needs to be on the same line as the if

Steve Dower added the comment: Adding this to the end of test_unicode_in_batch_file seems to be sufficient to cause the test to fail: self.assertEqual(err.strip(), '') Potentially we should add that additional check throughout this test module, but I don't think that's needed for a

[issue38351] Modernize email example from %-formatting to f-string

Fred L. Drake, Jr. added the comment: Does it make sense to change just one example? I'm not sure what the long-term stance is on whether %-formatting should be replaced at this point, but shouldn't this be a matter of which string formatting approach we want overall, rather than adjusting

[issue38344] activate.bat else needs to be on the same line as the if

Steve Dower added the comment: Should be a straightforward fix (replace the "else" with "if not defined..."), but since it slipped through testing we probably want a regression test in test_venv as well. (+RM for the 3.8 regression) -- keywords: +3.8regression nosy: +lukasz.langa

[issue38349] Email example using imaginary library installation error. The install shows that it only supports python 2.x but is listed under python 3.6+ docs.

jackotonye added the comment: Might be best to make it a little more obvious since most examples are considered executable code. That would require little modification. On Wed, Oct 2, 2019 at 12:20 PM SilentGhost wrote: > > SilentGhost added the comment: > > imaginary in the example is not

[issue23445] Use -Og for debug builds

STINNER Victor added the comment: I created bpo-38350 to propose to revert this change. -- ___ Python tracker ___ ___

[issue38350] ./configure --with-pydebug should use -O0 rather than -Og

STINNER Victor added the comment: My use case is to debug a crash using a Python compiled in debug module, like python3-debug program in Fedora. Since the debug ABI is now compatible with the release build, the idea is to attempt to reproduce a crash in gdb using python3-debug instead of

[issue38342] ImportError: cannot import name 'MetadataPathFinder' from 'importlib.metadata'

Brett Cannon added the comment: Closing as not a bug as this seems to be an issue from installing over a b3 or earlier build where the importlib/metadata/ directory gets left behind and thus take priority in import over importlib/metadata.py. -- nosy: +brett.cannon resolution: ->

[issue38350] ./configure --with-pydebug should use -O0 rather than -Og

Change by STINNER Victor : -- keywords: +patch pull_requests: +16133 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16544 ___ Python tracker ___

[issue38338] [2.7] test_ssl fails on RHEL8

miss-islington added the comment: New changeset 183733dfb6b4779d1a5e47f41a2fb86c6be08dda by Miss Islington (bot) in branch '3.8': bpo-38338, test.pythoninfo: add more ssl infos (GH-16539) https://github.com/python/cpython/commit/183733dfb6b4779d1a5e47f41a2fb86c6be08dda --

[issue38350] ./configure --with-pydebug should use -O0 rather than -Og

STINNER Victor added the comment: test_gdb is failing in different architectures and different operating systems: * Fedora, Python 3.8, x86-64: https://bugzilla.redhat.com/show_bug.cgi?id=1734327 * RHEL8, Python 3.6, s390x https://bugzilla.redhat.com/show_bug.cgi?id=1712977 * RHEL 8,

[issue38351] Modernize email example from %-formatting to f-string

New submission from Mariatta : A string was formatted with %s in the code example https://github.com/python/cpython/blob/b3e7045f8314e7b62cd95861d207fe2f97e47198/Doc/includes/email-simple.py#L15 ``` msg['Subject'] = 'The contents of %s' % textfile ``` It would be great to modernize that

[issue38350] ./configure --with-pydebug should use -O0 rather than -Og

STINNER Victor added the comment: I basically propose to revert bpo-23445 change: commit 3d6c784371bccc2407048652bce50c5bccf9b1af Author: Antoine Pitrou Date: Wed Feb 11 19:39:16 2015 +0100 Issue #23445: pydebug builds now use "gcc -Og" where possible, to make the resulting

[issue38338] [2.7] test_ssl fails on RHEL8

STINNER Victor added the comment: New changeset 403ca7ea70232e520af18511fbfb89b58ef2a046 by Victor Stinner in branch '2.7': [2.7] bpo-38338, test.pythoninfo: add more ssl infos (GH-16543) https://github.com/python/cpython/commit/403ca7ea70232e520af18511fbfb89b58ef2a046 --

[issue38350] ./configure --with-pydebug should use -O0 rather than -Og

New submission from STINNER Victor : In Python 2.7, when using ./configure --with-pydebug, Python is built using -O0 compiler optimization level: disable all optimizations. The comment is quite explicit: "Optimization messes up debuggers, so turn it off for debug builds". if test "$Py_DEBUG"

[issue38349] Email example using imaginary library installation error. The install shows that it only supports python 2.x but is listed under python 3.6+ docs.

SilentGhost added the comment: imaginary in the example is not meant to refer to https://pypi.org/project/Imaginary/ it's meant to refer to a module that you could write that would do all the dirty work. Perhaps, it's not the best name to use provided there is an actual module on pypi,

[issue38338] [2.7] test_ssl fails on RHEL8

miss-islington added the comment: New changeset ab98cd8aee5a5a7222b82ff13d61f0d33e72a889 by Miss Islington (bot) in branch '3.7': bpo-38338, test.pythoninfo: add more ssl infos (GH-16539) https://github.com/python/cpython/commit/ab98cd8aee5a5a7222b82ff13d61f0d33e72a889 -- nosy:

[issue38338] [2.7] test_ssl fails on RHEL8

Change by STINNER Victor : -- pull_requests: +16132 pull_request: https://github.com/python/cpython/pull/16543 ___ Python tracker ___

[issue38349] Email example using imaginary library installation error. The install shows that it only supports python 2.x but is listed under python 3.6+ docs.

Change by jackotonye : -- title: Email example using imaginary library installation error. The install shows that it only supports python 2.x but is listed for python 3.6+ -> Email example using imaginary library installation error. The install shows that it only supports python 2.x

[issue38349] Email example using imaginary library installation error. The install shows that it only supports python 2.x but is listed for python 3.6+

New submission from jackotonye : https://docs.python.org/3.7/library/email.examples.html -- assignee: docs@python components: Documentation messages: 353743 nosy: docs@python, jackotonye priority: normal severity: normal status: open title: Email example using imaginary library

[issue38338] [2.7] test_ssl fails on RHEL8

Change by miss-islington : -- pull_requests: +16130 pull_request: https://github.com/python/cpython/pull/16541 ___ Python tracker ___

[issue38338] [2.7] test_ssl fails on RHEL8

Change by miss-islington : -- pull_requests: +16131 pull_request: https://github.com/python/cpython/pull/16542 ___ Python tracker ___

[issue38338] [2.7] test_ssl fails on RHEL8

STINNER Victor added the comment: New changeset b3e7045f8314e7b62cd95861d207fe2f97e47198 by Victor Stinner in branch 'master': bpo-38338, test.pythoninfo: add more ssl infos (GH-16539) https://github.com/python/cpython/commit/b3e7045f8314e7b62cd95861d207fe2f97e47198 --

[issue38348] Make python -m ast more configurable

Change by Batuhan : -- keywords: +patch pull_requests: +16129 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16540 ___ Python tracker ___

[issue38348] Make python -m ast more configurable

New submission from Batuhan : Allow user to set indent level and parsing status of type comments -- components: Library (Lib) messages: 353741 nosy: BTaskaya, serhiy.storchaka priority: normal severity: normal status: open title: Make python -m ast more configurable versions: Python

[issue38342] ImportError: cannot import name 'MetadataPathFinder' from 'importlib.metadata'

Batuhan added the comment: https://gitlab.com/python-devs/importlib_metadata/issues/92 -- nosy: +BTaskaya ___ Python tracker ___

[issue38338] [2.7] test_ssl fails on RHEL8

Change by STINNER Victor : -- keywords: +patch pull_requests: +16128 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16539 ___ Python tracker ___

[issue38342] ImportError: cannot import name 'MetadataPathFinder' from 'importlib.metadata'

Anthony Tuininga added the comment: Yes. I had tried b3 earlier, installed b4 over b3 and then rc1 over b4. Removing the cruft using the command you specified caused the problem to go away. -- ___ Python tracker

[issue38319] shutil.copyfile(): os.sendfile() fails with OverflowError on 32-bit system

STINNER Victor added the comment: 32-bit buildbots are back to green. Thanks for the fix! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

  1   2   >