[issue24746] doctest 'fancy diff' formats incorrectly strip trailing whitespace

Change by Senthil Kumaran : -- pull_requests: +11058, 11059 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue24746] doctest 'fancy diff' formats incorrectly strip trailing whitespace

Change by Senthil Kumaran : -- pull_requests: +11058, 11059, 11060 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue32146] multiprocessing freeze_support needed outside win32

Change by miss-islington : -- pull_requests: +11064, 11065, 11066 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue24746] doctest 'fancy diff' formats incorrectly strip trailing whitespace

Change by Senthil Kumaran : -- pull_requests: +11067, 11068, 11070 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue24746] doctest 'fancy diff' formats incorrectly strip trailing whitespace

Change by Senthil Kumaran : -- pull_requests: +11067, 11068 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue24746] doctest 'fancy diff' formats incorrectly strip trailing whitespace

Change by Senthil Kumaran : -- pull_requests: +11067, 11068, 11069, 11070 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue24746] doctest 'fancy diff' formats incorrectly strip trailing whitespace

Ned Deily added the comment: New changeset d09e8cecf214b1de457feae01860f5592f912a8e by Ned Deily (Senthil Kumaran) in branch '3.6': Revert "bpo-24746: Avoid stripping trailing whitespace in doctest fancy diff (GH-10639) (GH-11477)" (GH-11509)

[issue35707] time.sleep() should support objects with __float__

Jeroen Demeyer added the comment: > I'm not sure in which order the conversion should be tried to avoid/reduce > precision loss during the conversion. I would suggest the order 1. __index__ to ensure exact conversion of exact integers 2. __float__ to ensure correct conversion of

[issue35710] Make dataclasses.field() accept another name for __init__ field's name

Change by Eric V. Smith : -- assignee: -> eric.smith nosy: +eric.smith type: -> enhancement ___ Python tracker ___ ___

[issue35714] Document that the null character '\0' terminates a struct format spec

Serhiy Storchaka added the comment: I think the null character is illegal character in the format string, and struct functions should raise a struct.error for it. -- nosy: +serhiy.storchaka ___ Python tracker

[issue24746] doctest 'fancy diff' formats incorrectly strip trailing whitespace

Senthil Kumaran added the comment: New changeset 0167c08163f44f4a033497102244bbb6150f606b by Senthil Kumaran in branch '2.7': bpo-24746: Fix doctest failures when running the testsuite with -R (#11501) (#11512)

[issue26239] distutils link-objects is not normalized

Cheryl Sabella added the comment: This was fixed in issue 1703178. -- nosy: +cheryl.sabella resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> link_objects in setup.cfg crashes build ___ Python tracker

[issue35661] Store the venv prompt in pyvenv.cfg

Steve Dower added the comment: Your tests actually went the other way. This one puts a trailing space after the prompt and expected it to be there in the file, but also ensured that exactly one space was added at the start. self.assertEqual(context.prompt, '(My prompt) ')

[issue35693] test_httpservers fails

Change by Jorge Ramos : -- stage: test needed -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list

[issue35399] Sysconfig bug

Change by Jorge Ramos : -- stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue35400] PGOMGR : warning PG0188:

Change by Jorge Ramos : -- stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue35711] Print information about an unexpectedly pending error before crashing

Serhiy Storchaka added the comment: Calling PyErr_Occurred() on every function call adds some overhead. It should be called only in the debug build. In addition to the traceback, it would be nice to output also some information about the callable. Note also that PyErr_Print() calls

[issue35693] test_httpservers fails

Jorge Ramos added the comment: It is true that I worry about failing tests during PGO training because they stop me from compiling Python -with- PGO. I also got here to report my experience and problems back to you guys but, if the problems are known, well, there's nothing much I can do

[issue35693] test_httpservers fails

Steve Dower added the comment: > It is true that I worry about failing tests during PGO training because they > stop me from compiling Python -with- PGO. They shouldn't prevent you from compiling with PGO... even if they cause Python to crash, you should be able to compile still. How is it

[issue35712] Make NotImplemented unusable in boolean context

Serhiy Storchaka added the comment: This is a common mistake. Even the default implementation of object.__ne__ had a bug, fixed only 4 years ago in issue21408. There were several errors in stdlib. I am sure there is a lot of occurrences of this errors in a third party code. So I like this

[issue35693] test_httpservers fails

Steve Dower added the comment: Defining new training sets for PGO would be a new job (that you could volunteer to do if you like). The test suite is convenient because when you clone our GitHub repository, it's already there. Another training suite would have to be installed somehow as part

[issue35693] test_httpservers fails

Zachary Ware added the comment: Test failures during the PGO training (*not* those after the final PGO compilation) should be ignored; if they're not, that's an issue that should be fixed. -- ___ Python tracker

[issue35156] Consider revising documentation on Python Builds from source

Change by Jorge Ramos : -- stage: needs patch -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list

[issue35157] Missing pyconfig.h when building from source and pgo flag is enabled

Change by Jorge Ramos : -- stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue35711] Print information about an unexpectedly pending error before crashing

Change by Roundup Robot : -- keywords: +patch, patch pull_requests: +11071, 11072 stage: -> patch review ___ Python tracker ___

[issue35711] Print information about an unexpectedly pending error before crashing

Change by Roundup Robot : -- keywords: +patch, patch, patch pull_requests: +11071, 11072, 11073 stage: -> patch review ___ Python tracker ___

[issue35712] Make NotImplemented unusable in boolean context

New submission from Josh Rosenberg : I don't really expect this to go anywhere until Python 4 (*maybe* 3.9 after a deprecation period), but it seems like it would have been a good idea to make NotImplementedType's __bool__ explicitly raise a TypeError (rather than leaving it unset, so

[issue35713] Fatal Python error: _PySys_BeginInit: can't initialize sys module

Tasy added the comment: Sorry for the confusion. The three dots were for many lines of successful compilation output from make. The rest is the final few lines where the compilation fails. -- ___ Python tracker

[issue35714] Document that the null character '\0' terminates a struct format spec

Steven D'Aprano added the comment: I'm not sure whether having NULLs terminate a struct format string is a feature or a bug. Given that nearly every other string in Python treat NULLs as ordinary characters, I'm inclined to say this is a bug. Or at least an unnecessary restriction that

[issue35712] Make NotImplemented unusable in boolean context

Karthikeyan Singaravelan added the comment: Seems related issue22978 -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list

[issue24746] doctest 'fancy diff' formats incorrectly strip trailing whitespace

Senthil Kumaran added the comment: All changes related to this issue are done. Thanks for your contribution and engagement everyone! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue32146] multiprocessing freeze_support needed outside win32

bbayles added the comment: Thanks for the note. I've merged in master and fixed a conflict in the test file. In an earlier rev I tried to do the argument parsing without ast.literal_eval, but found it awkward to support all the ways [1] can manifest. You might have a better idea? [1]

[issue35712] Make NotImplemented unusable in boolean context

Steven D'Aprano added the comment: > the canonical __ne__ delegation to __eq__ for any class should be implemented > as something like I disagree that your code snippet is the canonical way to write __ne__. I'd write it like this: def __ne__(self, other): return not (self ==

[issue35656] More matchers in unittest.mock

Lisa Roach added the comment: APPROXIMATE feels like it might lead to code smell to me, if I know roughly what the float should be why would I not want to test it for exactness? It could end up hiding inconsistencies the tests should be catching. -- nosy: +lisroach

[issue35714] Document that the null character '\0' terminates a struct format spec

New submission from Dan Snider : ie.: >>> from struct import calcsize >>> calcsize('\144\u0064\000xf\U0031000\60d\121\U0051') 16 I'm sure some people think it's obvious or even expect the null character to signal EOF but it probably isn't obvious at all to those without

[issue35713] Fatal Python error: _PySys_BeginInit: can't initialize sys module

Karthikeyan Singaravelan added the comment: Please attach the full build log too along with the command executed. -- nosy: +xtreak ___ Python tracker ___

[issue35713] Fatal Python error: _PySys_BeginInit: can't initialize sys module

STINNER Victor added the comment: Because it's late, I will say it shortly: if you don't elaborate how you get this error, I will simply close the issue. You have to describe what you are trying to do, your OS, etc. (It works for me!) -- ___

[issue35711] Print information about an unexpectedly pending error before crashing

New submission from Samuel Freilich : _PyObject_FastCallDict and _PyObject_FastCallKeywords assert that there is no pending exception before calling functions that might otherwise clobber the exception state. However, that doesn't produce very clear output for debugging, since the assert

[issue35711] Print information about an unexpectedly pending error before crashing

Change by Roundup Robot : -- keywords: +patch pull_requests: +11071 stage: -> patch review ___ Python tracker ___ ___

[issue2517] Error when printing an exception containing a Unicode string

Piotr Dobrogost added the comment: Benjamin Peterson in comment https://bugs.python.org/issue2517#msg64771 wrote: "That is because Python encodes it's error messages as ASCII by default…" Could somebody please point where in the source code of Python 2 this happens? --

[issue35713] Fatal Python error: _PySys_BeginInit: can't initialize sys module

STINNER Victor added the comment: > . > . > . Hello. Can you elaborate this part? -- nosy: +vstinner ___ Python tracker ___ ___

[issue34628] urllib.request.urlopen fails when userinfo is present in URL

Windson Yang added the comment: I found that Requests library use urllib3 library which looks like ignore the user info part (in request_context https://github.com/urllib3/urllib3/blob/master/src/urllib3/poolmanager.py#L208). Did I miss something or we should also ignore it? --

[issue35713] Fatal Python error: _PySys_BeginInit: can't initialize sys module

New submission from Tasy : . . . ./python -E -S -m sysconfig --generate-posix-vars ;\ if test $? -ne 0 ; then \ echo "generate-posix-vars failed" ; \ rm -f ./pybuilddir.txt ; \ exit 1 ; \ fi Fatal Python error: _PySys_BeginInit:

<    1   2