[issue35060] subprocess output seems to depend on size of terminal screen

Stéphane Wirtel added the comment: My script: #!/usr/bin/env python import pathlib import subprocess output = subprocess.check_output(['ps', 'aux']) pathlib.Path('/tmp/ps_aux.txt').write_bytes(output) When I execute the following script in the REPL, I get your

[issue35060] subprocess output seems to depend on size of terminal screen

Stéphane Wirtel added the comment: just one question, did you use this command in the REPL? -- ___ Python tracker <https://bugs.python.org/issue35060> ___ ___

[issue35060] subprocess output seems to depend on size of terminal screen

Stéphane Wirtel added the comment: Very strange, I tried with 3.8a and I did not get this issue. Normally we use a pipe for stdin and stdout when we use check_output, so in this case, there is no relation with the size of the terminal. this is just a stream. second point, you explain that

[issue35055] Error when we try to download the epub archive

Stéphane Wirtel added the comment: @ned maybe we could close this issue -- ___ Python tracker <https://bugs.python.org/issue35055> ___ ___ Python-bugs-list mailin

[issue35055] Error when we try to download the epub archive

Stéphane Wirtel added the comment: same issue with 3.6 -- versions: +Python 3.6 ___ Python tracker <https://bugs.python.org/issue35055> ___ ___ Python-bugs-list m

[issue35055] Error when we try to download the epub archive

New submission from Stéphane Wirtel : On this page https://docs.python.org/3/download.html, there is a link for the epub archive but we can not download it because there is 404 Not Found. https://docs.python.org/3/archives/python-3.7.1-docs.epub -- messages: 328332 nosy: matrixise

[issue35044] Use the :exc: role for the exceptions in the doc

Change by Stéphane Wirtel : -- keywords: +patch pull_requests: +9375 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue35044> ___ ___ Py

[issue35042] Use the role :pep: for the PEP \d+

Stéphane Wirtel added the comment: @thatiparthy When you start to contribute to Python, and you see there is a PEP in the doc. 1. What's a PEP? 2. Where can I find the PEP XYZ? 3. Am I on the right website for the PEP? if you don't know the concept of the PEPs, you will check

[issue35042] Use the role :pep: for the PEP \d+

Stéphane Wirtel added the comment: in fact, in the doc of Sphinx, it's just :pep: and not :PEP: see http://www.sphinx-doc.org/en/master/usage/restructuredtext/roles.html?highlight=%3Apep%3A#role-pep in this case, I think it's better to use the "reference" and u

[issue35044] Use the :exc: role for the exceptions in the doc

New submission from Stéphane Wirtel : In the doc, there is some locations where we do not use the :exc: role for the exceptions, I try to fix that with this PR. -- assignee: docs@python components: Documentation messages: 328249 nosy: docs@python, matrixise priority: normal severity

[issue35042] Use the role :pep: for the PEP \d+

Stéphane Wirtel added the comment: sure, it's the default behavior of this role, I have a PR with the fix, but Github has a big issue with the PRs :/ -- ___ Python tracker <https://bugs.python.org/is

[issue35042] Use the role :pep: for the PEP \d+

Change by Stéphane Wirtel : -- keywords: +patch pull_requests: +9374 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue35042> ___ ___ Py

[issue35042] Use the role :pep: for the PEP \d+

New submission from Stéphane Wirtel : In the doc, we write PEP XYZ but there is a sphinx role for that, just replace PEP XYZ by :pep:`XYZ` and convert the :PEP: by :pep: -- assignee: docs@python components: Documentation messages: 328240 nosy: docs@python, matrixise priority: normal

[issue34909] StrEnum subclasses cannot be created

Stéphane Wirtel added the comment: Hi Ned, good news (I hope the best for the wife of Ethan) -- ___ Python tracker <https://bugs.python.org/issue34909> ___ ___

[issue34909] StrEnum subclasses cannot be created

Stéphane Wirtel added the comment: Hi Ethan and Ned, I am not fluent with the code of the Enum, but maybe I could work on this issue and try to finish it. Ethan, I am really sorry for your wife, take care of her. -- ___ Python tracker <ht

[issue35032] Remove the videos from faq/Windows

Change by Stéphane Wirtel : -- keywords: +patch pull_requests: +9345 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue35032> ___ ___ Py

[issue35032] Remove the videos from faq/Windows

New submission from Stéphane Wirtel : In the FAQ of Windows, there are two references to external videos for the configuration of a dev environment for Windows, but these videos are no longer available because the domain name no longer exists. -- assignee: docs@python components

[issue24658] open().write() fails on 2 GB+ data (OS X)

Change by Stéphane Wirtel : -- pull_requests: +9289 ___ Python tracker <https://bugs.python.org/issue24658> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue24568] Misc/NEWS: "free-after-use" -> "use-after-free"

Change by Stéphane Wirtel : -- pull_requests: +9288 ___ Python tracker <https://bugs.python.org/issue24568> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue24658] open().write() fails on 2 GB+ data (OS X)

Change by Stéphane Wirtel : -- pull_requests: +9287 ___ Python tracker <https://bugs.python.org/issue24658> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue24658] open().write() fails on 2 GB+ data (OS X)

Stéphane Wirtel added the comment: Hi all, Could you test the PR with Windows? I don't have a Windows computer. Thank you, Stéphane -- ___ Python tracker <https://bugs.python.org/is

[issue34996] Add name to process and thread pool

Stéphane Wirtel added the comment: Hi Raz, 1. Please could you sign the CLA? 2. About the name, why did you use these names? Is there a discussion somewhere about the names? Thank you -- nosy: +matrixise ___ Python tracker <ht

[issue23420] python -m cProfile -s fails with non informative message

Stéphane Wirtel added the comment: welcome -- ___ Python tracker <https://bugs.python.org/issue23420> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue23420] python -m cProfile -s fails with non informative message

Change by Stéphane Wirtel : -- pull_requests: +9281 ___ Python tracker <https://bugs.python.org/issue23420> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue23420] python -m cProfile -s fails with non informative message

Change by Stéphane Wirtel : -- pull_requests: +9280 ___ Python tracker <https://bugs.python.org/issue23420> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue23420] python -m cProfile -s fails with non informative message

Change by Stéphane Wirtel : -- pull_requests: +9279 ___ Python tracker <https://bugs.python.org/issue23420> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue23420] python -m cProfile -s fails with non informative message

Stéphane Wirtel added the comment: Hi, Just used the content of the patch and apply it on master, Add a unittest and the blurb entry. -- nosy: +matrixise ___ Python tracker <https://bugs.python.org/issue23

[issue23420] python -m cProfile -s fails with non informative message

Change by Stéphane Wirtel : -- pull_requests: +9278 ___ Python tracker <https://bugs.python.org/issue23420> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34994] sysconfig returns the git commands for GITBRANCH, GITVERSION and GITTAG

Stéphane Wirtel added the comment: yep, sure and now, after your explanations (you and victor) I just closed my PR, but to be honnest with your, I was really surprised when I have seen the git commands in the GIT* variables. Thanks for your review and your time. -- resolution: not a

[issue34994] sysconfig returns the git commands for GITBRANCH, GITVERSION and GITTAG

Change by Stéphane Wirtel : -- stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue34994> ___ ___ Python-bugs-list

[issue34994] sysconfig returns the git commands for GITBRANCH, GITVERSION and GITTAG

Stéphane Wirtel added the comment: sure, but you can also get these info from sysconfig. and for me, there is a problem with sysconfig. two solutions, remove GIT* from sysconfig or fix sysconfig with the right values. -- stage: patch review

[issue34994] sysconfig returns the git commands for GITBRANCH, GITVERSION and GITTAG

Change by Stéphane Wirtel : -- keywords: +patch pull_requests: +9257 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue34994> ___ ___ Py

[issue34994] sysconfig returns the git commands for GITBRANCH, GITVERSION and GITTAG

New submission from Stéphane Wirtel : > ./configure --prefix=$PWD-build --with-pydebug --quiet > make -j 4 -s > git --git-dir ./.git rev-parse --short HEAD ee171a26c1 > ./python -m sysconfig | grep GIT GITBRANCH = "git --git-dir ./.git name-rev --name-only HEAD" GITTAG =

[issue34990] year 2038 problem in compileall.py

Change by Stéphane Wirtel : -- keywords: +patch pull_requests: +9256 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue34990> ___ ___ Py

[issue34992] many warnings with f28 and gcc 8.1.1

New submission from Stéphane Wirtel : I use Fedora 28 and gcc (GCC) 8.1.1 20180712 (Red Hat 8.1.1-5) and I get a lot of warnings, with the standard config of Python (./configure) Objects/call.c: In function '_PyMethodDef_RawFastCallDict': Objects/call.c:515:24: warning: ca

[issue34990] year 2038 problem in compileall.py

Stéphane Wirtel added the comment: So we need to fix compileall.py. maybe we could add the label 'easy' to this issue. -- ___ Python tracker <https://bugs.python.o

[issue34990] year 2038 problem in compileall.py

Stéphane Wirtel added the comment: But until 2038, maybe there will be a new format for the .pyc file. We should keep this issue and try to fix it for 3.8 or 3.9? -- ___ Python tracker <https://bugs.python.org/issue34

[issue34990] year 2038 problem in compileall.py

Stéphane Wirtel added the comment: With 3.8a Traceback (most recent call last): File "/home/stephane/src/github.com/python/cpython/Lib/runpy.py", line 192, in _run_module_as_main return _run_code(code, main_globals, None, File "/home/stephane/src/github.com/python/cpyth

[issue34969] Add --fast, --best to the gzip CLI

Stéphane Wirtel added the comment: Julien, Currently, the default compresslevel for gzip.open, GzipFile is 9, for the best method compression. Maybe we could define 6 as the tradeoff and specify 1 (for fast), 9 (for best), 6 (tradeoff). Maybe in an other issue

[issue34969] Add --fast, --best to the gzip CLI

Change by Stéphane Wirtel : -- nosy: +mdk stage: patch review -> ___ Python tracker <https://bugs.python.org/issue34969> ___ ___ Python-bugs-list mai

[issue34969] Add --fast, --best to the gzip CLI

Change by Stéphane Wirtel : -- keywords: +patch pull_requests: +9207 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue34969> ___ ___ Py

[issue34969] Add --fast, --best to the gzip CLI

New submission from Stéphane Wirtel : the gzip module has a CLI but this one does not allow to specify the compression method (slow, fast) -- assignee: matrixise messages: 327626 nosy: matrixise priority: normal severity: normal status: open title: Add --fast, --best to the gzip CLI

[issue34967] Sphinx is deprecating add_description_unit

Change by Stéphane Wirtel : -- keywords: +patch pull_requests: +9202 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue34967> ___ ___ Py

[issue34962] make doctest does not pass :/

Change by Stéphane Wirtel : -- keywords: +patch pull_requests: +9186 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue34962> ___ ___ Py

[issue34962] make doctest does not pass :/

New submission from Stéphane Wirtel : make -C Doc/ doctest does not pass the tests. -- messages: 327553 nosy: matrixise priority: normal severity: normal status: open title: make doctest does not pass :/ versions: Python 3.8 ___ Python tracker

[issue34959] Are the tests optional on travis?

Change by Stéphane Wirtel : -- resolution: -> rejected ___ Python tracker <https://bugs.python.org/issue34959> ___ ___ Python-bugs-list mailing list Unsubscrib

[issue34959] Are the tests optional on travis?

Stéphane Wirtel added the comment: this issue is useless :/ -- stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/i

[issue34959] Are the tests optional on travis?

New submission from Stéphane Wirtel : In the config of Travis, we can see there is a OPTIONAL=true env var for the tests at line 72: https://github.com/python/cpython/blob/master/.travis.yml#L72 If I read the doc, normally the tests can crash and this is not a problem? Is it right, because I

[issue34839] doctest: Change example under warnings section

Stéphane Wirtel added the comment: Hi Raymond and Tim, I just updated the PR with your recommendations. Have a nice day, -- ___ Python tracker <https://bugs.python.org/issue34

[issue34906] Fix typo in the documentation

Change by Stéphane Wirtel : -- pull_requests: +9173 ___ Python tracker <https://bugs.python.org/issue34906> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34906] Fix typo in the documentation

Change by Stéphane Wirtel : -- pull_requests: +9172 ___ Python tracker <https://bugs.python.org/issue34906> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34906] Fix typo in the documentation

Change by Stéphane Wirtel : -- pull_requests: +9169 ___ Python tracker <https://bugs.python.org/issue34906> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34913] Document gzip command line interface

Change by Stéphane Wirtel : -- keywords: +patch pull_requests: +9168 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue34913> ___ ___ Py

[issue23596] gzip argparse interface

Stéphane Wirtel added the comment: I have added some tests for 3.6, 3.7 and 3.8. But for the new CLI, just for 3.8 now, I am going to close this issue. -- stage: patch review -> resolved status: open -> closed versions: +Python 3.6, Python 3.7, Python 3.8 -Pyth

[issue23596] gzip argparse interface

Change by Stéphane Wirtel : -- pull_requests: +9167 ___ Python tracker <https://bugs.python.org/issue23596> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue23596] gzip argparse interface

Stéphane Wirtel added the comment: And now, I am going to work on the refactoring with argparse -- ___ Python tracker <https://bugs.python.org/issue23

[issue23596] gzip argparse interface

Stéphane Wirtel added the comment: Hi Berker, Here is my PR for this issue. >From this PR, I will add the new CLI with argparse. And after this issue, I will work on https://bugs.python.org/issue34913 -- nosy: +matrixise ___ Python trac

[issue23596] gzip argparse interface

Change by Stéphane Wirtel : -- pull_requests: +9162 ___ Python tracker <https://bugs.python.org/issue23596> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34945] regression with ./python -m test and pdb

Change by Stéphane Wirtel : -- title: regression with ./python -m test -> regression with ./python -m test and pdb ___ Python tracker <https://bugs.python.org/issu

[issue34945] regression with ./python -m test

New submission from Stéphane Wirtel : Hi Steve, I have a regression since the commit d0f49d2f5085ca68e3dc8725f1fb1c9674bfb5ed, commit d0f49d2f5085ca68e3dc8725f1fb1c9674bfb5ed (HEAD) Author: Steve Dower Date: Tue Sep 18 09:10:26 2018 -0700 bpo-34582: Adds JUnit XML output for regression

[issue33643] Mock functions with autospec STILL don't support assert_called_once, assert_called, assert_not_called

Stéphane Wirtel added the comment: There is a problem with your code, you use `mock` library but this one does not exist in the standard library. You should use `unittest.mock` Because this issue is not related with the unittest.mock library, I am going to close this issue

[issue34909] StrEnum subclasses cannot be created

Stéphane Wirtel added the comment: Ethan, I think you have fixed the issue, could you close this issue? Thank you -- ___ Python tracker <https://bugs.python.org/issue34

[issue34839] doctest: Change example under warnings section

Stéphane Wirtel added the comment: Tim, I understand. It's just my experience, I have seen a lot of new comers (in my python trainings), they just copy the examples and don't read the total explanation. sometimes, because english is not their native language and in this case, t

[issue34839] doctest: Change example under warnings section

Stéphane Wirtel added the comment: Hi Raymond, Ok, if you agree with Tim, I just created a PR. Have a nice day, -- keywords: -patch stage: patch review -> needs patch ___ Python tracker <https://bugs.python.org/issu

[issue34839] doctest: Change example under warnings section

Change by Stéphane Wirtel : -- keywords: +patch pull_requests: +9123 stage: needs patch -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue34839] doctest: Change example under warnings section

Stéphane Wirtel added the comment: Hi Terry, You say we need to keep this illustration with a section 'before 3.6' but in think it's a bad thing. 1. when you read a documentation, you just copy the example, and sometimes you don't read the requirements. 2. why d

[issue34909] StrEnum subclasses cannot be created

Stéphane Wirtel added the comment: git bisect start # bad: [1596fea0a329e1f5e4cce0135724881ca5f1d341] bpo-34899: Fix a possible assertion failure due to int_from_bytes_impl() (GH-9705) git bisect bad 1596fea0a329e1f5e4cce0135724881ca5f1d341 # good: [84b0129b5e0a0e22aad22ae8db2e3833a228aa57

[issue34909] StrEnum subclasses cannot be created

Stéphane Wirtel added the comment: Hi Ethan, the issue appears with your patch 0c076caaa82a9c6596e1fe1dbe6384d53f30a1a3 is the first bad commit commit 0c076caaa82a9c6596e1fe1dbe6384d53f30a1a3 Author: Ethan Furman Date: Fri Sep 21 22:26:32 2018 -0700 [3.7] bpo-29577: Enum: mixin

[issue34906] Fix typo in the documentation

Stéphane Wirtel added the comment: I just created a new PR where I fix typos in the Misc directory (mainly). -- ___ Python tracker <https://bugs.python.org/issue34

[issue34906] Fix typo in the documentation

Change by Stéphane Wirtel : -- pull_requests: +9122 ___ Python tracker <https://bugs.python.org/issue34906> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34907] calculation not working properly

Stéphane Wirtel added the comment: and you can read this link where we explain the limits of the float type: https://docs.python.org/3/tutorial/floatingpoint.html -- status: closed -> open ___ Python tracker <https://bugs.python.org/issu

[issue34907] calculation not working properly

Stéphane Wirtel added the comment: because you have the round with the float type. you could use the decimal module with Decimal In [1]: import decimal In [2]: decimal.Decimal('15.06') + 5 Out[2]: Decimal('20.06') -- nosy: +matrixise stage: -> resolved

[issue34906] Fix typo in the documentation

Change by Stéphane Wirtel : -- keywords: +patch pull_requests: +9095 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue34906> ___ ___ Py

[issue34906] Fix typo in the documentation

Change by Stéphane Wirtel : -- assignee: matrixise nosy: matrixise priority: normal severity: normal status: open title: Fix typo in the documentation versions: Python 3.8 ___ Python tracker <https://bugs.python.org/issue34

[issue34903] strptime %d handling of single digit day of month

Stéphane Wirtel added the comment: Hi Mike, Thank you for your issue, but could you add the link to the documentation, just because we have time.strptime and datetime.datetime.strptime. Thank you, -- nosy: +matrixise ___ Python tracker <ht

[issue14886] json C vs pure-python implementation difference

Stéphane Wirtel added the comment: We have received a notification about this bug for 3.5 -- nosy: +matrixise versions: +Python 3.5, Python 3.6, Python 3.7, Python 3.8 -Python 2.7, Python 3.2, Python 3.3 ___ Python tracker <https://bugs.python.

[issue34359] Wrong virtual environment found

Stéphane Wirtel added the comment: it's normal because this path is in the PATH env variable. so in this case, I think we can close this issue. -- ___ Python tracker <https://bugs.python.org/is

[issue34359] Wrong virtual environment found

Stéphane Wirtel added the comment: Now, you could use a Windows shortcut where you specify the version of Python when you execute your script. F:\python\scripts3\.venv\bin\python myscript.py For example. -- nosy: +matrixise resolution: not a bug -> stage: resolved ->

[issue34359] Wrong virtual environment found

Stéphane Wirtel added the comment: And the Shebang is specific to the Unix-like systems, the loader from the operating system, will read the first line and will try to execute the defined interpreter. https://en.wikipedia.org/wiki/Shebang_(Unix) On Windows, I am not sure, but like Paul

[issue34355] SIGSEGV (Address boundary error)

Change by Stéphane Wirtel : -- components: -asyncio nosy: -asvetlov, yselivanov ___ Python tracker <https://bugs.python.org/issue34355> ___ ___ Python-bug

[issue34355] SIGSEGV (Address boundary error)

Stéphane Wirtel added the comment: and what's the issue with asyncio ? -- ___ Python tracker <https://bugs.python.org/issue34355> ___ ___ Python-bugs-list m

[issue34355] SIGSEGV (Address boundary error)

Stéphane Wirtel added the comment: With the last revision of 3.7 (w/o --with-debug), I don't get this issue on Fedora 28 :/ -- nosy: +matrixise ___ Python tracker <https://bugs.python.org/is

[issue34310] Build error with option "--with-pydebug" on Mac OS 10.13.6

Stéphane Wirtel added the comment: Hi Yu, I am going to close this issue because 1. there is no master-dirty branch 2. your hash commit: d17fe275a3 does not exist in the CPython repository 3. I just downloaded the last revision of CPython and compile it on a 10.13.4 OSX and I don't have

[issue34310] Build error with option "--with-pydebug" on Mac OS 10.13.6

Stéphane Wirtel added the comment: Could you retry with a make distclean && ./configure --with-debug && make ? To be sure. -- nosy: +matrixise ___ Python tracker <https://bugs.py

[issue34332] Suggestion for a new loop type

Stéphane Wirtel added the comment: You can also use a context manager and the `with` statement. -- nosy: +matrixise ___ Python tracker <https://bugs.python.org/issue34

[issue34326] test_subprocess.POSIXProcessTestCase fails in AMD64 Ubuntu 3.x

Change by Stéphane Wirtel : -- stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue34326> ___ ___ Pyth

[issue34326] test_subprocess.POSIXProcessTestCase fails in AMD64 Ubuntu 3.x

Stéphane Wirtel added the comment: Thanks Victor, I don't know enough the API C-Python :/ -- ___ Python tracker <https://bugs.python.org/issue34326> ___ ___

[issue34329] Document how to remove a suffix with pathlib.Path.with_suffix

Stéphane Wirtel added the comment: It's the same thing for everything, for example, in Karate, you will start with the white belt and with practice, you will get the black belt. Thank you again for your contribution. -- ___ Python tracker &

[issue34329] Document how to remove a suffix with pathlib.Path.with_suffix

Stéphane Wirtel added the comment: yep, it's a manual modification in b.p.o but after that, we can check your PR. thank you for your patience. -- ___ Python tracker <https://bugs.python.org/is

[issue34329] Document how to remove a suffix with pathlib.Path.with_suffix

Stéphane Wirtel added the comment: Good catch, thank you. Could you sign the CLA, without the CLA, we can't process your PR. Thank you -- nosy: +matrixise ___ Python tracker <https://bugs.python.org/is

[issue34326] test_subprocess.POSIXProcessTestCase fails in AMD64 Ubuntu 3.x

Stéphane Wirtel added the comment: Pablo, the main issue comes after this commit, you can strace the call for example ./python -m unittest test.test_subprocess.POSIXProcessTestCase.test_pass_fds on this test function and you will see than there is a opened file descriptor. I tried to

[issue34326] test_subprocess.POSIXProcessTestCase fails in AMD64 Ubuntu 3.x

Stéphane Wirtel added the comment: I think there is an issue with pymain_run_file, in the new code of Victor, a file descriptor is not closed but I don't know why. -- ___ Python tracker <https://bugs.python.org/is

[issue34326] test_subprocess.POSIXProcessTestCase fails in AMD64 Ubuntu 3.x

Stéphane Wirtel added the comment: I continue to work on this issue -- ___ Python tracker <https://bugs.python.org/issue34326> ___ ___ Python-bugs-list mailin

[issue34326] test_subprocess.POSIXProcessTestCase fails in AMD64 Ubuntu 3.x

Stéphane Wirtel added the comment: When I try to find the issue with git bisect, I have one commit. 72ec3193b5118a2ccc8be8bf03d7b74691c6a264 is the first bad commit commit 72ec3193b5118a2ccc8be8bf03d7b74691c6a264 Author: Victor Stinner Date: Thu Aug 2 19:34:20 2018 +0200 bpo-34170

[issue34326] test_subprocess.POSIXProcessTestCase fails in AMD64 Ubuntu 3.x

Stéphane Wirtel added the comment: same problem here: linux: https://python.visualstudio.com/8e426817-76c0-4b99-ba9e-a48a1e4bd5db/_build/index?buildId=21241 macOS: https://python.visualstudio.com/8e426817-76c0-4b99-ba9e-a48a1e4bd5db/_build/index?buildId=21242

[issue34326] test_subprocess.POSIXProcessTestCase fails in AMD64 Ubuntu 3.x

Stéphane Wirtel added the comment: Same issue with my builds : * Linux -> https://python.visualstudio.com/cpython/_build/results?buildId=21273&view=logs * macOS -> https://python.visualstudio.com/cpython/_build/results?buildId=21274&view=logs -- nosy: +matri

[issue34207] test_cmd_line test_utf8_mode test_warnings fail in all FreeBSD 3.x (3.8) buildbots

Stéphane Wirtel added the comment: xtreak in this case, it's an issue on the buildbot cluster, we have to be sure that we don't have this error again. and for that, we have to find the origin of the crash on buildbot. -- nosy:

[issue34323] False timeout log message on proactor close

Stéphane Wirtel added the comment: Hi johnboy2, thank you for your issue, but could you send us more information about your platform? thank you -- nosy: +matrixise ___ Python tracker <https://bugs.python.org/issue34

[issue34324] Doc README wrong directory name for venv

Stéphane Wirtel added the comment: I just pushed a PR. -- nosy: +matrixise ___ Python tracker <https://bugs.python.org/issue34324> ___ ___ Python-bugs-list mailin

[issue34324] Doc README wrong directory name for venv

Change by Stéphane Wirtel : -- keywords: +patch pull_requests: +8149 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue34324> ___ ___ Py

<    1   2   3   4   5   6   7   8   9   10   >