[issue34656] memory exhaustion in Modules/_pickle.c:1393

[Miro Hrončok]

Miro Hrončok  added the comment:

Should this go to 3.4 and 3.5 as well, since it is a security thing?

http://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-20406.html

--
nosy: +hroncok

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35696] remove unnecessary operation in long_compare()

[Ma Lin]

New submission from Ma Lin :

static int
long_compare(PyLongObject *a, PyLongObject *b)
{

}

This function in /Objects/longobject.c is used to compare two PyLongObject's 
value.
We only need the sign, converting to -1 or +1 is not necessary.

--
messages: 333293
nosy: Ma Lin
priority: normal
severity: normal
status: open
title: remove unnecessary operation in long_compare()
versions: Python 3.8

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35696] remove unnecessary operation in long_compare()

[Ma Lin]

Change by Ma Lin :


--
keywords: +patch
pull_requests: +10974
stage:  -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35696] remove unnecessary operation in long_compare()

[Ma Lin]

Change by Ma Lin :


--
keywords: +patch, patch
pull_requests: +10974, 10975
stage:  -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35696] remove unnecessary operation in long_compare()

[Ma Lin]

Change by Ma Lin :


--
keywords: +patch, patch, patch
pull_requests: +10974, 10975, 10976
stage:  -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue34656] memory exhaustion in Modules/_pickle.c:1393

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

I am not sure this issue should be classified as a security issue. It can cause 
DDOS, because pickle should not be used with untrusted data. If it is used, the 
program has more severe security issues than just DDOS.

The crash could be triggered by accident, but this is very unlikely. I doubts 
that this happened even once in real world.  Libraries used for handling a 
large amount of data (like NumPy) use more efficient pickle representation, and 
can provide even more efficient alternate serialization methods. Note that 
integers and floats are not memoized, this increases the complexity and size of 
data that could be affected by this bug.

But I think that this fix needs a news entry. Do you mind to add it Benjamin?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24780] unittest assertEqual difference output foiled by newlines

[Karthikeyan Singaravelan]

Karthikeyan Singaravelan  added the comment:

Thanks @chris.jerdonek. I have reverted the title to original report. Since 
CPython now accepts PR if any one of the original authors can convert their 
patch to a PR with tests then it will be great.

--
title: difflib.ndiff produces unreadable output when input missing trailing 
newline -> unittest assertEqual difference output foiled by newlines

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35638] Introduce fixed point locale aware format type for floating point numbers

[Stefan Krah]

Stefan Krah  added the comment:

> Since it seems like we are still at the "idea" stage, would it make sense to 
> add a function which accept options to choose how to format a number?

Maybe, but I think for format() Eric's latest proposal on python-ideas is great 
("*f" for "f + LC_NUMERIC", "$f" for "f + LC_MONETARY".

For me that's sufficient. Does locale.format_string() handle the other cases?


> By the way, the decimal module doesn't support properly the following corner 
> case: LC_NUMERIC using an encoding different than LC_CTYPE encoding. I wrote 
> https://github.com/python/cpython/pull/5191 but I abandonned my change.

Well, I *discovered and opened* #7442 several years ago, and you said:

"I see that various people contributed to the issue, but it looks like the only 
user asking for the request is Stefan Krah. I prefer to close the issue and 
wait until more users ask for it before considering again the patch, or find a 
different way to implement the feature (support LC_NUMERIC and LC_CTYPE locales 
using a different encoding)."


So why would you think that I'm not aware of that issue? It has low priority 
for me and I hesitate to depend on the official locale functions in decimal 
because I don't want to be involved in additional issue reports in that area.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35638] Introduce fixed point locale aware format type for floating point numbers

[Łukasz Stelmach]

Łukasz Stelmach  added the comment:

I'd appreciate, if we continued the discussion at python-ideas, where I posted 
the idea[1]. There has already been several valuable comments.

[1] https://mail.python.org/pipermail/python-ideas/2019-January/054793.html

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35687] The unittest module diff is missing/forgetting/not putting newline before + and ? for some inputs

[Addons Zz]

Addons Zz  added the comment:

The issue is also reproducible, by directly using difflib:
```python
import difflib

def bugged_diff(expected, actual):
expected = expected.splitlines( 1 )
actual = actual.splitlines( 1 )

# diff = difflib.ndiff( expected, actual )
if expected != actual:
diff = difflib.context_diff( expected, actual, fromfile='expected 
input', tofile='actual output', lineterm='\n' )
return '\n' + ''.join( diff )


if __name__ == '__main__':
expected = "testing.main_unit_tests.test_dictionaryBasicLogging:416 - 
dictionary\n" \
"testing.main_unit_tests.test_dictionaryBasicLogging:417 - 
dictionary {1: 'defined_chunk'}"

actual = "15:49:35:912.348986 - testing.main_unit_tests - dictionary\n" \
"15:49:35:918.879986 - testing.main_unit_tests - dictionary {1: 
'defined_chunk'}"

print( expected, actual )
```

It outputs:
```
testing.main_unit_tests.test_dictionaryBasicLogging:416 - dictionary
testing.main_unit_tests.test_dictionaryBasicLogging:417 - dictionary {1: 
'defined_chunk'} 15:49:35:912.348986 - testing.main_unit_tests - dictionary
15:49:35:918.879986 - testing.main_unit_tests - dictionary {1: 'defined_chunk'}
```

But it should be: (still missing the new line on the same place as 
`assertEqual` does)
```
testing.main_unit_tests.test_dictionaryBasicLogging:416 - dictionary
testing.main_unit_tests.test_dictionaryBasicLogging:417 - dictionary {1: 
'defined_chunk'} 
15:49:35:912.348986 - testing.main_unit_tests - dictionary
15:49:35:918.879986 - testing.main_unit_tests - dictionary {1: 'defined_chunk'}
```

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35687] The unittest module diff is missing/forgetting/not putting newline before + and ? for some inputs

[Addons Zz]

Addons Zz  added the comment:

* Correction
```python
import difflib

def bugged_diff(expected, actual):
expected = expected.splitlines( 1 )
actual = actual.splitlines( 1 )

# diff = difflib.ndiff( expected, actual )
if expected != actual:
diff = difflib.context_diff( expected, actual, fromfile='expected 
input', tofile='actual output', lineterm='\n' )
return '\n' + ''.join( diff )


if __name__ == '__main__':
expected = "testing.main_unit_tests.test_dictionaryBasicLogging:416 - 
dictionary\n" \
"testing.main_unit_tests.test_dictionaryBasicLogging:417 - 
dictionary {1: 'defined_chunk'}"

actual = "15:49:35:912.348986 - testing.main_unit_tests - dictionary\n" \
"15:49:35:918.879986 - testing.main_unit_tests - dictionary {1: 
'defined_chunk'}"

print( bugged_diff( expected, actual ) )
```

Outputs:
```
*** expected input
--- actual output
***
*** 1,2 
! testing.main_unit_tests.test_dictionaryBasicLogging:416 - dictionary
! testing.main_unit_tests.test_dictionaryBasicLogging:417 - dictionary {1: 
'defined_chunk'}--- 1,2 
! 15:49:35:912.348986 - testing.main_unit_tests - dictionary
! 15:49:35:918.879986 - testing.main_unit_tests - dictionary {1: 
'defined_chunk'}
```

May be it should be:
```

*** expected input
--- actual output
***
*** 1,2 
! testing.main_unit_tests.test_dictionaryBasicLogging:416 - dictionary
! testing.main_unit_tests.test_dictionaryBasicLogging:417 - dictionary {1: 
'defined_chunk'}
--- 1,2 
! 15:49:35:912.348986 - testing.main_unit_tests - dictionary
! 15:49:35:918.879986 - testing.main_unit_tests - dictionary {1: 
'defined_chunk'}
```

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35687] The unittest module diff is missing/forgetting/not putting newline before + and ? for some inputs

[Addons Zz]

Addons Zz  added the comment:

I applied the patch from https://bugs.python.org/file44679 and it fixed the 
issue for this example using the unittest module:
```python
import unittest

class StdErrUnitTests(unittest.TestCase):

def test_function_name(self):
expected = "testing.main_unit_tests.test_dictionaryBasicLogging:416 - 
dictionary\n" \
"testing.main_unit_tests.test_dictionaryBasicLogging:417 - 
dictionary {1: 'defined_chunk'}"

actual = "15:49:35:912.348986 - testing.main_unit_tests - dictionary\n" 
\
"15:49:35:918.879986 - testing.main_unit_tests - dictionary {1: 
'defined_chunk'}"

self.assertEqual(expected, actual)

if __name__ == '__main__':
unittest.main()
```

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35550] Some define guards for Solaris are wrong

[Jakub Kulik]

Jakub Kulik  added the comment:

We are building previous versions of Python with Solaris Studio which works 
with define guards as they are right now. 3.7 is first version build with gcc. 
We don't plan to switch to gcc on 2.7 and so it doesn't affect us.

But I guess if this fix can be done easily, it would be correct to do.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35697] decimal: formatter error if LC_NUMERIC uses a different encoding than LC_CTYPE

[STINNER Victor]

New submission from STINNER Victor :

The decimal module support formatting a number in the "n" formatting type if 
the LC_NUMERIC locale uses a different encoding than the LC_CTYPE locale. 

Example with attached decimal_locale.py on Fedora 29 with Python 3.7.2:

$ python3 decimal_locale.py 
LC_NUMERIC locale: uk_UA.koi8u
decimal_point: ',' = ',' = U+002c
thousands_sep: '\xa0' = '\xa0' = U+00a0
Traceback (most recent call last):
  File "/home/vstinner/decimal_locale.py", line 16, in 
text = format(num, "n")
ValueError: invalid decimal point or unsupported combination of LC_CTYPE and 
LC_NUMERIC

Attached PR modify the _decimal module to support this corner case.

Note: I already wrote PR 5191 last year, but I abandoned the PR in the 
meanwhile.

--

Supporting non-ASCII decimal point and thousands separator has a long history 
and a list of now fixed issues:

* bpo-7442
* bpo-13706
* bpo-25812
* bpo-28604 (LC_MONETARY)
* bpo-31900
* bpo-33954

I even wrote an article about these bugs :-)
https://github.com/python/cpython/pull/5191

Python 3.7.2 now supports different encodings for LC_NUMERIC, LC_MONETARY and 
LC_CTYPE locales. format(int, "n") sets temporarily LC_CTYPE to LC_NUMERIC to 
decode decimal_point and thousands_sep from the correct encoding. The LC_CTYPE 
locale is only changed if it's different than LC_NUMERIC locale and if the 
decimal point and/or thousands separator is non-ASCII. It's implemented in this 
function:

int
_Py_GetLocaleconvNumeric(struct lconv *lc,
 PyObject **decimal_point, PyObject **thousands_sep)

Function used by locale.localeconv() and format() (for "n" type).

I decided to fix the bug when I was fixing other locale bugs because we now got 
enough bug reports.

Copy of my msg309980:

"""
> I would not consider this a bug in Python, but rather in the locale settings 
> passed to setlocale().

Past 10 years, I repeated to every single user I met that "Python 3 is right, 
your system setup is wrong". But that's a waste of time. People continue to 
associate Python3 and Unicode to annoying bugs, because they don't understand 
how locales work.

Instead of having to repeat to each user that "hum, maybe your config is 
wrong", I prefer to support this non convential setup and work as expected ("it 
just works"). With my latest implementation, setlocale() is only done when 
LC_CTYPE and LC_NUMERIC are different, which is the corner case which 
"shouldn't occur in practice".
"""

--
components: Library (Lib)
files: decimal_locale.py
messages: 02
nosy: vstinner
priority: normal
severity: normal
status: open
title: decimal: formatter error if LC_NUMERIC uses a different encoding than 
LC_CTYPE
versions: Python 3.8
Added file: https://bugs.python.org/file48038/decimal_locale.py

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35697] decimal: formatter error if LC_NUMERIC uses a different encoding than LC_CTYPE

[STINNER Victor]

STINNER Victor  added the comment:

Oh, I was wrong: bpo-25812 has not been fixed yet.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35697] decimal: formatter error if LC_NUMERIC uses a different encoding than LC_CTYPE

[Stefan Krah]

Change by Stefan Krah :


--
assignee:  -> skrah
nosy: +skrah

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35697] decimal: formatter error if LC_NUMERIC uses a different encoding than LC_CTYPE

[Stefan Krah]

Stefan Krah  added the comment:

Since #7442 (again, *I* discovered this and it is *mentioned* in the
_decimal sources), there have been zero bug reports about decimal.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35697] decimal: formatter error if LC_NUMERIC uses a different encoding than LC_CTYPE

[STINNER Victor]

Change by STINNER Victor :


--
keywords: +patch
pull_requests: +10977
stage:  -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35697] decimal: formatter error if LC_NUMERIC uses a different encoding than LC_CTYPE

[STINNER Victor]

Change by STINNER Victor :


--
keywords: +patch, patch
pull_requests: +10977, 10978
stage:  -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35697] decimal: formatter error if LC_NUMERIC uses a different encoding than LC_CTYPE

[STINNER Victor]

Change by STINNER Victor :


--
keywords: +patch, patch, patch
pull_requests: +10977, 10978, 10979
stage:  -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35698] Division by 2 in statistics.median

[Jonathan Fine]

New submission from Jonathan Fine :

When len(data) is odd, median returns the average of the two middle values. 
This average is computed using
i = n//2
return (data[i - 1] + data[i])/2

This results in the following behaviour

>>> from fractions import Fraction
>>> from statistics import median
>>> F1 = Fraction(1, 1)

>>> median([1])
1
>>> median([1, 1]) # Example 1.
1.0

>>> median([F1])
Fraction(1, 1)
>>> median([F1, F1])
Fraction(1, 1)

>>> median([2, 2, 1, F1]) # Example 2.
Fraction(3, 2)

>>> median([2, 2, F1, 1]) # Example 3.
1.5

Perhaps, when len(data) is odd, it would be better to test the two middle 
values for equality. This would resolve Example 1. It would not help with 
Examples 2 and 3, which might not have a satisfactory solution.

See also issue 33084.

--
messages: 05
nosy: jfine2358
priority: normal
severity: normal
status: open
title: Division by 2 in statistics.median
type: behavior

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35697] decimal: formatter error if LC_NUMERIC uses a different encoding than LC_CTYPE

[STINNER Victor]

STINNER Victor  added the comment:

Ok, I wrote PR 11474. Correct result with this PR:

$ ./python decimal_locale.py 
LC_NUMERIC locale: uk_UA.koi8u
decimal_point: ',' = ',' = U+002c
thousands_sep: '\xa0' = '\xa0' = U+00a0
format: '1\xa0200,5' = 1 200,5 = U+0031 U+00a0 U+0032 U+0030 U+0030 U+002c 
U+0035

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35697] decimal: formatter error if LC_NUMERIC uses a different encoding than LC_CTYPE

[STINNER Victor]

STINNER Victor  added the comment:

Stefan Krah:
> Since #7442 (again, *I* discovered this and it is *mentioned* in the
_decimal sources), ...

I closed bpo-7442 in the meanwhile, so I opened this new issue specific to the 
decimal module.

> ... there have been zero bug reports about decimal.

Well, here you have :-) A bug report about decimal.

I let you decide what to do with this bug. I wrote a fix. It's up to you to 
merge it, reject it or do nothing :-)

I wanted to make sure that the bug is fixed in all parts of the Python stdlib.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25812] locale.nl_langinfo() can't decode value

[STINNER Victor]

STINNER Victor  added the comment:

Since this bug has been reported, locale.localeconv() has been fixed in 
bpo-31900 to temporarily set LC_CTYPE to LC_NUMERIC to decode numeric fields of 
localeconv() from the proper encoding. I guess that a similar fix can be 
applied to locale.nl_langinfo(): set LC_CTYPE to LC_NUMERIC if the parameter is 
a numeric field.

I only knew locale.nl_langinfo(locale.CODESET). I didn't know that this 
function accepted other arguments :-)

I even wrote an article about these locale bugs :-)
https://github.com/python/cpython/pull/5191

See also bpo-35697: "decimal: formatter error if LC_NUMERIC uses a different 
encoding than LC_CTYPE".

--
nosy: +vstinner

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35698] Division by 2 in statistics.median

[STINNER Victor]

STINNER Victor  added the comment:

> When len(data) is odd, median returns the average of the two middle values.

I'm not sure that I understand your issue. Do you consider that it's a bug? 
It's part of the definition of the median function, no?
https://en.wikipedia.org/wiki/Median#Finite_set_of_numbers

--
nosy: +vstinner

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35697] decimal: formatter error if LC_NUMERIC uses a different encoding than LC_CTYPE

[Stefan Krah]

Stefan Krah  added the comment:

Don't you find it strange to close #7442 in mutual agreement and now
mention the word "bug" 50 times?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35697] _decimal: Implement the previously rejected changes from #7442.

[Stefan Krah]

Change by Stefan Krah :


--
title: decimal: formatter error if LC_NUMERIC uses a different encoding than 
LC_CTYPE -> _decimal: Implement the previously rejected changes from #7442.

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35697] _decimal: Implement the previously rejected changes from #7442.

[Stefan Krah]

Stefan Krah  added the comment:

Also Marc-Andre does not consider this a bug in #31900.  The
presentation of this issue is increasingly bizarre.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35699] distutils cannot find Build Tools 2017 since 3.7.2

[Marc Schlaich]

New submission from Marc Schlaich :

vshwere.exe doesn't return Build Tools 2017 per default. This means Build Tools 
2017 are not detected by distutils in 3.7.2 and you get the famous "Microsoft 
Visual C++ 14.0 is required" error.

Please see https://github.com/Microsoft/vswhere/issues/125 for more details.

The solution is to add 

"-products", "*",

to the vswhere.exe call.

This is a regression of https://bugs.python.org/issue35067.

--
components: Distutils
messages: 12
nosy: dstufft, eric.araujo, schlamar, steve.dower
priority: normal
severity: normal
status: open
title: distutils cannot find Build Tools 2017 since 3.7.2
type: behavior
versions: Python 3.7, Python 3.8

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35697] _decimal: Implement the previously rejected changes from #7442.

[STINNER Victor]

STINNER Victor  added the comment:

Stefan Krah:
> Don't you find it strange to close #7442 in mutual agreement and now
mention the word "bug" 50 times?

We agreed to close the bug in 2014. In the meanwhile, more and more people 
reported the same bug (multiple similar bug reports and more and more frequent 
messages). So I decided to fix the bug instead of explaining to users that they 
must not do that :-)


> Also Marc-Andre does not consider this a bug in #31900.  The
presentation of this issue is increasingly bizarre.

Aha, maybe I misunderstood him when he wrote (msg309981):

"Sounds like a good compromise :-)"

--

I'm not sure of what you are asking here. You are the maintainer of the decimal 
module. If you consider that it's not worth it, just close the issue. It's up 
to you ;-)

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35550] Some define guards for Solaris are wrong

[STINNER Victor]

STINNER Victor  added the comment:

> We don't plan to switch to gcc on 2.7 and so it doesn't affect us.

Ok. I close the issue. If anyone wants to fix 2.7, please go ahead :-)

--
stage: commit review -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35638] Introduce fixed point locale aware format type for floating point numbers

[STINNER Victor]

STINNER Victor  added the comment:

> By the way, the decimal module doesn't support properly the following corner 
> case: LC_NUMERIC using an encoding different than LC_CTYPE encoding. I wrote 
> https://github.com/python/cpython/pull/5191 but I abandonned my change.

FYI I opened bpo-35697 to discuss the decimal module case.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35697] _decimal: Implement the previously rejected changes from #7442.

[STINNER Victor]

STINNER Victor  added the comment:

Oh, I forgot to mention the context: I reported this issue as follow-up to 
discussions on bpo-35638: "Introduce fixed point locale aware format type for 
floating point numbers".

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35697] _decimal: Implement the previously rejected changes from #7442.

[STINNER Victor]

STINNER Victor  added the comment:

Extract of Stefan Krah's msg333296 of bpo-35638:

> So why would you think that I'm not aware of that issue?

Oh, I never said that.

I wrote "By the way, the decimal module doesn't support properly the following 
corner case: LC_NUMERIC using an encoding different than LC_CTYPE encoding. I 
wrote https://github.com/python/cpython/pull/5191 but I abandonned my change." 
as a reminder for myself. I found again the bug when I wrote my article, and I 
realized that I abandoned my PR when I had my burnout, and not because the fix 
was "officially" rejected.

So I opened this issue to get an official statement :-)


> It has low priority for me and I hesitate to depend on the official locale 
> functions in decimal because I don't want to be involved in additional issue 
> reports in that area.

As I wrote in my PR, I'm not very happy of my proposed implementation. But 
let's discuss options to fix it :-)

I don't understand "I don't want to be involved in additional issue reports in 
that area". If the bug is fixed, why do you expect more bug reports? You wrote 
that nobody reported any issue related to formatting a decimal number using the 
locale since 2009.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35700] Place, Pack and Grid should return the widget

[Peter Vex]

New submission from Peter Vex :

When you want to simply place a widget on a window and you also want to store 
the reference for that widget in a variable you can't do that in one line, 
which is really unpleasant, because when you create a new widget these things 
are usually the first what you want to do with a widget and breaking it two 
line is just making things more complicated.

For example, if you want to create 3 label, place it next to each other and 
store their reference:

import tkinter as tk
root = tk.Tk()

# you can't do that:
# here the variables assigned to None, since grid() returns 'nothing'
label1 = tk.Label(root).grid(row=0, column=0)
label2 = tk.Label(root).grid(row=0, column=1)
label3 = tk.Label(root).grid(row=0, column=2)

# actually, you must do this:
label1 = tk.Label(root)
label1.grid(row=0, column=0)
label2 = tk.Label(root)
label2.grid(row=0, column=1)
label3 = tk.Label(root)
label3.grid(row=0, column=2)

--
components: Tkinter
messages: 18
nosy: Peter Vex
priority: normal
pull_requests: 10980
severity: normal
status: open
title: Place, Pack and Grid should return the widget
type: behavior
versions: Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Senthil Kumaran]

Senthil Kumaran  added the comment:


New changeset cbb16459934eaf29c7c7d362939cd05550b2f21f by Senthil Kumaran 
(Sanyam Khurana) in branch 'master':
bpo-24746: Avoid stripping trailing whitespace in doctest fancy diff (#10639)
https://github.com/python/cpython/commit/cbb16459934eaf29c7c7d362939cd05550b2f21f


--
nosy: +orsenthil

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[miss-islington]

Change by miss-islington :


--
pull_requests: +10981, 10982, 10983, 10985
stage: test needed -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[miss-islington]

Change by miss-islington :


--
pull_requests: +10982, 10985

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[miss-islington]

Change by miss-islington :


--
pull_requests: +10981, 10982
stage: test needed -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[miss-islington]

Change by miss-islington :


--
pull_requests: +10981, 10982, 10983, 10984, 10985
stage: test needed -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[miss-islington]

Change by miss-islington :


--
pull_requests: +10981
stage: test needed -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[miss-islington]

Change by miss-islington :


--
pull_requests: +10982, 10983, 10984, 10985, 10986

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[miss-islington]

miss-islington  added the comment:


New changeset 53cf5f084b01cb16630361be5377047c068d2b44 by Miss Islington (bot) 
in branch '3.7':
bpo-24746: Avoid stripping trailing whitespace in doctest fancy diff (GH-10639)
https://github.com/python/cpython/commit/53cf5f084b01cb16630361be5377047c068d2b44


--
nosy: +miss-islington

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35697] _decimal: Implement the previously rejected changes from #7442.

[Stefan Krah]

Stefan Krah  added the comment:

I mean issue reports like #33954 or #35195.  These are just
two examples, and I'm NOT claiming that they are related.

But if functions like _PyUnicode_InsertThousandsGrouping()
*were* used in _decimal, I'd feel compelled to investigate.

Now I don't have to. I'd investigate #35195 for example, perhaps
just to find out that it has an entirely different cause.


Sometimes not being dependent on API functions is a virtue if
the code does not change very often.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Senthil Kumaran]

Senthil Kumaran  added the comment:


New changeset 5d9ae8b9df8371dd65514e0d60b561fd37056986 by Senthil Kumaran (Miss 
Islington (bot)) in branch '3.6':
bpo-24746: Avoid stripping trailing whitespace in doctest fancy diff (GH-10639) 
(#11477)
https://github.com/python/cpython/commit/5d9ae8b9df8371dd65514e0d60b561fd37056986


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35700] Place, Pack and Grid should return the widget

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

Methods place(), pack() and grid() correspond to corresponding Tk commands. 
These commands return nothing (empty string) in Tk, and Tkinter methods return 
nothing (None) in Python. If they will became returning something meaningful in 
future versions of Tk, we will lost a chance to translate this to Python if 
make them now returning the widget itself.

Note also that method chaining is not commonly used in Python. This code would 
look pretty unpythonic.

For these reasons I am against this idea.

--
nosy: +gpolo, serhiy.storchaka, terry.reedy

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35700] Place, Pack and Grid should return the widget

[Peter Vex]

Peter Vex  added the comment:

I can somewhat agreed with your point, even if it's not too realistic, but 
reasonable enough.

Also, I'd only use method chaining, because that'd be the only option. I can't 
pass an argument to tk.Label at creation like 'manager="grid"' or anything like 
that. In any case, I think doing it in a separate line makes the code longer 
and less readable even if it's pythonic.

Thanks for your consideration.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8538] Add FlagAction to argparse

[Rémi Lapeyre]

Change by Rémi Lapeyre :


--
keywords: +patch
pull_requests: +10987
stage: needs patch -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8538] Add FlagAction to argparse

[Rémi Lapeyre]

Change by Rémi Lapeyre :


--
keywords: +patch, patch
pull_requests: +10987, 10988
stage: needs patch -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8538] Add FlagAction to argparse

[Rémi Lapeyre]

Change by Rémi Lapeyre :


--
keywords: +patch, patch, patch
pull_requests: +10987, 10988, 10989
stage: needs patch -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35641] IDLE: calltips not properly formatted for functions without doc-strings

[Terry J. Reedy]

Change by Terry J. Reedy :


--
pull_requests: +10990, 10991

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35641] IDLE: calltips not properly formatted for functions without doc-strings

[Terry J. Reedy]

Change by Terry J. Reedy :


--
pull_requests: +10990, 10991, 10992

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35641] IDLE: calltips not properly formatted for functions without doc-strings

[Terry J. Reedy]

Change by Terry J. Reedy :


--
pull_requests: +10990

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35641] IDLE: calltips not properly formatted for functions without doc-strings

[Terry J. Reedy]

Change by Terry J. Reedy :


--
pull_requests:  -10992

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8538] Add FlagAction to argparse

[Rémi Lapeyre]

Rémi Lapeyre  added the comment:

I made a first proposal for this feature in PR 11478, I had to adapt 
argparse.Action to customize how the action is represented in the usage string 
by adding a format_usage() method that would default to the current behavior if 
not overridden.

Other methods to do this may be better but I did not find them.

--
versions: +Python 3.7, Python 3.8 -Python 3.2

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35641] IDLE: calltips not properly formatted for functions without doc-strings

[Terry J. Reedy]

Change by Terry J. Reedy :


--
pull_requests:  -10991

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35641] IDLE: calltips not properly formatted for functions without doc-strings

[Terry J. Reedy]

Terry J. Reedy  added the comment:


New changeset ee6559436797032b816dfb8c6376c9a451014962 by Terry Jan Reedy in 
branch 'master':
bpo-35641: Move IDLE blurb to IDLE directory (#11479)
https://github.com/python/cpython/commit/ee6559436797032b816dfb8c6376c9a451014962


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35698] Division by 2 in statistics.median

[Rémi Lapeyre]

Rémi Lapeyre  added the comment:

What do you think median([1, 1.0]) should return?

--
nosy: +remi.lapeyre

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35641] IDLE: calltips not properly formatted for functions without doc-strings

[miss-islington]

Change by miss-islington :


--
pull_requests: +10993, 10994, 10995

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35641] IDLE: calltips not properly formatted for functions without doc-strings

[miss-islington]

Change by miss-islington :


--
pull_requests: +10993

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35641] IDLE: calltips not properly formatted for functions without doc-strings

[miss-islington]

Change by miss-islington :


--
pull_requests: +10993, 10994

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35641] IDLE: calltips not properly formatted for functions without doc-strings

[miss-islington]

miss-islington  added the comment:


New changeset 6f76ef81596bbd885957b7fea3f40024ed9d6797 by Miss Islington (bot) 
in branch '3.7':
bpo-35641: Move IDLE blurb to IDLE directory (GH-11479)
https://github.com/python/cpython/commit/6f76ef81596bbd885957b7fea3f40024ed9d6797


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35693] test_httpservers fails

[Jorge Ramos]

Jorge Ramos  added the comment:

The thread doesn't display the attachment icon in bugtracker webpage, so I will 
copy the output here:

E:\RepoGiT\3.6>PCbuild\rt.bat -x64 -v test_httpservers
Deleting .pyc files ...
0 .pyc deleted
Cleaning _pth files ...

E:\RepoGiT\3.6>"E:\RepoGiT\3.6\PCbuild\amd64\python.exe"  -u -Wd -E -bb -m test 
 -v test_httpservers
== CPython 3.6.8+ (heads/3.6:c2340619a7, Jan 7 2019, 21:35:13) [MSC v.1916 64 
bit (AMD64)]
== Windows-10-10.0.17763-SP0 little-endian
== cwd: E:\RepoGiT\3.6\build\test_python_19808
== CPU count: 8
== encodings: locale=cp1252, FS=utf-8
Run tests sequentially
0:00:00 [1/1] test_httpservers
test_err (test.test_httpservers.RequestHandlerLoggingTestCase) ... ok
test_get (test.test_httpservers.RequestHandlerLoggingTestCase) ... ok
test_close_connection (test.test_httpservers.BaseHTTPRequestHandlerTestCase) 
... ok
test_date_time_string (test.test_httpservers.BaseHTTPRequestHandlerTestCase) 
... ok
test_header_buffering_of_send_error 
(test.test_httpservers.BaseHTTPRequestHandlerTestCase) ... ok
test_header_buffering_of_send_header 
(test.test_httpservers.BaseHTTPRequestHandlerTestCase) ... ok
test_header_buffering_of_send_response_only 
(test.test_httpservers.BaseHTTPRequestHandlerTestCase) ... ok
test_header_length (test.test_httpservers.BaseHTTPRequestHandlerTestCase) ... ok
test_header_unbuffered_when_continue 
(test.test_httpservers.BaseHTTPRequestHandlerTestCase) ... ok
test_html_escape_on_error 
(test.test_httpservers.BaseHTTPRequestHandlerTestCase) ... ok
test_http_0_9 (test.test_httpservers.BaseHTTPRequestHandlerTestCase) ... ok
test_http_1_0 (test.test_httpservers.BaseHTTPRequestHandlerTestCase) ... ok
test_http_1_1 (test.test_httpservers.BaseHTTPRequestHandlerTestCase) ... ok
test_request_length (test.test_httpservers.BaseHTTPRequestHandlerTestCase) ... 
ok
test_too_many_headers (test.test_httpservers.BaseHTTPRequestHandlerTestCase) 
... ok
test_with_continue_1_0 (test.test_httpservers.BaseHTTPRequestHandlerTestCase) 
... ok
test_with_continue_1_1 (test.test_httpservers.BaseHTTPRequestHandlerTestCase) 
... ok
test_with_continue_rejected 
(test.test_httpservers.BaseHTTPRequestHandlerTestCase) ... ok
test_command (test.test_httpservers.BaseHTTPServerTestCase) ... ok
test_error_content_length (test.test_httpservers.BaseHTTPServerTestCase) ... ok
test_handler (test.test_httpservers.BaseHTTPServerTestCase) ... ok
test_head_via_send_error (test.test_httpservers.BaseHTTPServerTestCase) ... ok
test_header_close (test.test_httpservers.BaseHTTPServerTestCase) ... ok
test_header_keep_alive (test.test_httpservers.BaseHTTPServerTestCase) ... ok
test_internal_key_error (test.test_httpservers.BaseHTTPServerTestCase) ... ok
test_latin1_header (test.test_httpservers.BaseHTTPServerTestCase) ... ok
test_request_line_trimming (test.test_httpservers.BaseHTTPServerTestCase) ... ok
test_return_custom_status (test.test_httpservers.BaseHTTPServerTestCase) ... ok
test_return_explain_error (test.test_httpservers.BaseHTTPServerTestCase) ... ok
test_return_header_keep_alive (test.test_httpservers.BaseHTTPServerTestCase) 
... ok
test_send_blank (test.test_httpservers.BaseHTTPServerTestCase) ... ok
test_send_error (test.test_httpservers.BaseHTTPServerTestCase) ... ok
test_version_bogus (test.test_httpservers.BaseHTTPServerTestCase) ... ok
test_version_digits (test.test_httpservers.BaseHTTPServerTestCase) ... ok
test_version_invalid (test.test_httpservers.BaseHTTPServerTestCase) ... ok
test_version_none (test.test_httpservers.BaseHTTPServerTestCase) ... ok
test_version_none_get (test.test_httpservers.BaseHTTPServerTestCase) ... ok
test_get (test.test_httpservers.SimpleHTTPServerTestCase) ... FAIL
test_head (test.test_httpservers.SimpleHTTPServerTestCase) ... ok
test_html_escape_filename (test.test_httpservers.SimpleHTTPServerTestCase) ... 
skipped 'Can not create file .txt on current file system'
test_invalid_requests (test.test_httpservers.SimpleHTTPServerTestCase) ... ok
test_path_without_leading_slash 
(test.test_httpservers.SimpleHTTPServerTestCase) ... FAIL
test_undecodable_filename (test.test_httpservers.SimpleHTTPServerTestCase) ... 
skipped 'undecodable name cannot be decoded on win32'
test_authorization (test.test_httpservers.CGIHTTPServerTestCase) ... 
E:\RepoGiT\3.6\lib\encodings\cp1252.py:21: ResourceWarning: unclosed 

  class IncrementalDecoder(codecs.IncrementalDecoder):
E:\RepoGiT\3.6\lib\encodings\cp1252.py:21: ResourceWarning: unclosed 

  class IncrementalDecoder(codecs.IncrementalDecoder):
ok
test_headers_and_content (test.test_httpservers.CGIHTTPServerTestCase) ... ok
test_invaliduri (test.test_httpservers.CGIHTTPServerTestCase) ... ok
test_issue19435 (test.test_httpservers.CGIHTTPServerTestCase) ... ok
test_nested_cgi_path_issue21323 (test.test_httpservers.CGIHTTPServerTestCase) 
... ok
test_no_leading_slash (test.test_httpservers.CGIHTTPServerTestCase) ... ok
test_os_environ_is_not_altered (test.test_httpservers.CGIHTTPServerTestCase) 
... ok
test_post (tes

[issue35656] More matchers in unittest.mock

[Petter S]

Petter S  added the comment:

Agreed! The code above was a quick example. There are also functions in the 
standard library for approximate float matching that the "real" code would use.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35066] Inconsistency between dangling '%' handling in time.strftime() and datetime.strftime()

[STINNER Victor]

STINNER Victor  added the comment:

Paul Ganssle asked me to look at PR 10692. This issue is about consistency, so 
I don't understand this part of the change:

try:
_time.strftime('%')
except ValueError:
self.skipTest('time module does not support trailing %')

Would why datetime have the same behavior on all platforms, but 
time.strftime('%') may or may not raise an exception depending on the libc?

Can't we get the same behavior on all platforms and the same behavior in time 
and datetime module. Honestly, I have no preference between always raising an 
exception or always success (just copy trailing "%").

This issue reminds me the old bpo-16322: time.strftime("%z") fails to format 
properly the timezone name. I would suggest to "preprocess" the input string 
passed to the C function strftime() / wcsftime() to replace %z or %Z with the 
timezone name, but only pass format substrings?

Something similar can be done for the trailing "%": pass a substring (without 
the trailing %) to strftime() / wcsftime(), and later append "%".

--
nosy: +vstinner

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35700] Place, Pack and Grid should return the widget

[Zachary Ware]

Zachary Ware  added the comment:

I agree with Serhiy that we shouldn't do this; tkinter is (mostly) just a thin 
wrapper around Tcl/Tk and this isn't enough of a win to deviate from that.  In 
any case, this would be an enhancement that could only go into 3.8 at this 
point.

For your particular example, it would prefer to read the following anyway:

```
import tkinter as tk

root = tk.Tk()

labels = []
for i in range(3):
label = tk.Label(root)
label.grid(row=0, column=i)
labels.append(label)
```


Or if you really want this feature in your own code, try this out:

```
import tkinter as tk
from functools import partial

def _mapped(method, widget, *args, **kwargs):
getattr(widget, method)(*args, **kwargs)
return widget

packed = partial(_mapped, 'pack')
gridded = partial(_mapped, 'grid')
placed = partial(_mapped, 'place')

root = tk.Tk()

label1 = gridded(tk.Label(root), row=0, column=0)
label2 = gridded(tk.Label(root), row=0, column=1)
label3 = gridded(tk.Label(root), row=0, column=2)
```

--
nosy: +zach.ware
type: behavior -> enhancement
versions: +Python 3.8 -Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35678] subprocess.check_output(): OSError: [WinError 87]

[MaximilianSP]

MaximilianSP  added the comment:

Hello Victor, 

a new version of the code has been released and I now get another error. I will 
mark the issue as resolved. Thank you for the quick response!

--
resolution:  -> not a bug

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35678] subprocess.check_output(): OSError: [WinError 87]

[MaximilianSP]

Change by MaximilianSP :


--
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35693] test_httpservers fails

[Zachary Ware]

Zachary Ware  added the comment:

No need to paste the output; it's linked between the form at the top and the 
first message.  It's not shown on the issue list view because it's not a patch.

The next step is to see if it still fails when you build from the `master` 
branch since 3.6 is now closed to anything but security fixes.  Debugging is 
likely to be up to you, though; this doesn't happen on any of our CI platforms 
or on my own machines.  We can give you tips on how to go about that debugging 
here or via IRC or Zulip, though.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35678] subprocess.check_output(): OSError: [WinError 87]

[STINNER Victor]

STINNER Victor  added the comment:

Ok, you're welcome ;-)

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35397] Undeprecate and document urllib.parse.unwrap

[Rémi Lapeyre]

Change by Rémi Lapeyre :


--
keywords: +patch
pull_requests: +10996
stage:  -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35066] Inconsistency between dangling '%' handling in time.strftime() and datetime.strftime()

[Michael Saah]

Michael Saah  added the comment:

Hi Victor, thanks for taking a look.

> Would why datetime have the same behavior on all platforms, but 
> time.strftime('%') may or may not raise an exception depending on the libc?

If I understand the call stack correctly, datetime does not have the
same behavior on all platforms. datetime does some preprocessing and
then hands the resulting format string down to time.strftime, which in
turn passes it down to the system. The time module does not check for
trailing %.

To be honest, I can't claim to understand the strftime
system-dependence, as I couldn't find good documentation of it nor
could I find error handling code. The C version of datetime.strftime
really just said "There's a lone trailing %; doesn't make sense." when
making the check. The python version of datetime did not make this
check, and neither does any version of the time module's strftime.

> Something similar can be done for the trailing "%": pass a substring (without 
> the trailing %) to strftime() / wcsftime(), and later append "%".

I like this idea, as it gets around the ill-defined parameters of
system-dependence that I'm working with. This change would need to
made to the time module, and would be in addition to the changes I've
already made.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35397] Undeprecate and document urllib.parse.unwrap

[Rémi Lapeyre]

Change by Rémi Lapeyre :


--
keywords: +patch, patch
pull_requests: +10996, 10997
stage:  -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35397] Undeprecate and document urllib.parse.unwrap

[Rémi Lapeyre]

Change by Rémi Lapeyre :


--
keywords: +patch, patch, patch
pull_requests: +10996, 10997, 10998
stage:  -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35700] Place, Pack and Grid should return the widget

[Peter Vex]

Peter Vex  added the comment:

Thank you Zachary, very interesting examples, to say the least!

--
type: enhancement -> behavior
versions: +Python 3.7 -Python 3.8

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35700] Place, Pack and Grid should return the widget

[Zachary Ware]

Change by Zachary Ware :


--
type: behavior -> enhancement
versions: +Python 3.8 -Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35701] 3.8 needlessly breaks weak references for UUIDs

[Josh Rosenberg]

New submission from Josh Rosenberg :

I 100% agree with the aim of #30977 (reduce uuid.UUID() memory footprint), but 
it broke compatibility for any application that was weak referencing UUID 
instances (which seems a reasonable thing to do; a strong reference to a UUID 
can be stored in a single master container or passed through a processing 
pipeline, while also keying WeakKeyDictionary with cached supplementary data). 
I specifically noticed this because I was about to do that very thing in a 
processing flow, then noticed UUIDs in 3.6 were a bit heavyweight, memory-wise, 
went to file a bug on memory usage to add __slots__, and discovered someone had 
already done it for me.

Rather than break compatibility in 3.8, why not simply include '__weakref__' in 
the __slots__ listing? It would also remove the need for a What's New level 
description of the change, since the description informs people that:

1. Instances can no longer be weak-referenced (which adding __weakref__ would 
undp)
2. Instances can no longer add arbitrary attributes. (which was already the 
case in terms of documented API, programmatically enforced via a __setattr__ 
override, so it seems an unnecessary thing to highlight outside of Misc/NEWS)

The cost of changing __slots__ from:

__slots__ = ('int', 'is_safe')

to:

__slots__ = 'int', 'is_safe', '__weakref__'

would only be 4-8 bytes (for 64 bit Python, total cost of object + int would go 
from 100 to 108 bytes, still about half of the pre-__slots__ cost of 212 
bytes), and avoid breaking any code that might rely on being able to weak 
reference UUIDs.

I've marked this as release blocker for the time being because if 3.8 actually 
releases with this change, it will cause back compat issues that might prevent 
people relying on UUID weak references from upgrading their code.

--
components: Library (Lib)
keywords: 3.7regression, easy
messages: 38
nosy: Nir Soffer, josh.r, serhiy.storchaka, taleinat, vstinner, wbolster
priority: release blocker
severity: normal
stage: needs patch
status: open
title: 3.8 needlessly breaks weak references for UUIDs
type: behavior
versions: Python 3.8

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35700] Place, Pack and Grid should return the widget

[Josh Rosenberg]

Josh Rosenberg  added the comment:

Closing as rejected; to my knowledge, *no* built-in Python method both mutate 
an object and returns the object just mutated, precisely because:

1. It allows for chaining that leads fairly quickly to unreadable code (Python 
is not Perl/Ruby)

2. It creates doubt as to whether the original object was mutated or not (if 
list.sort returns a sorted list, it becomes unclear as to whether the original 
list was sorted as well, or whether a new list was returned; sortedlist = 
unsortedlist.sort() might give an inaccurate impression of what was going on). 
Zachary's example of using top-level functions to do the work instead is 
basically the same practicality compromise that sorted makes in relation to 
list.sort.

--
nosy: +josh.r
resolution:  -> rejected
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35698] Division by 2 in statistics.median

[Josh Rosenberg]

Josh Rosenberg  added the comment:

vstinner: The problem isn't the averaging, it's the type inconsistency. In both 
examples (median([1]), median([1, 1])), the median is unambiguously 1 (no 
actual average is needed; the values are identical), yet it gets converted to 
1.0 only in the latter case.

I'm not sure it's possible to fix this though; right now, there is consistency 
among two cases:

1. When the length is odd, you get the median by identity (and therefore type 
and value are unchanged)
2. When the length is even, you get the median by adding and dividing by 2 (so 
for ints, the result is always float).

A fix that changed that would add yet another layer of complexity:

1. When the length is odd, you get the median by identity (and therefore type 
and value are unchanged)
2. When the length is even, 
  a. If the two middle values are equal (possibly only if they have equal types 
as well, to resolve the issue with [1, 1.0] or [1, True]), return the first of 
the two middle values (median by identity as in #1)
  b. Otherwise, you get the median by adding and dividing by 2

And note the required type checking in 2a required to even make it that 
consistent. Even if we accepted that, we'd pretty quickly get into a debate 
over whether median([3, 5]) should try to return 4 instead of 4.0, given that 
the median is representable in the source type (which would further damage 
consistency).

If anything, I think the best design would have been to *always* include a 
division step (so odd length cases performed middle_elem / 1, while even did 
(middle_elem1 + middle_elem2) / 2) so the behavior was consistent regardless 
odd vs. even input length, but that shipped has probably sailed, given the 
documented behavior specifically notes that the precise middle data point is 
itself returned for the odd case.

I think the solution for people concerned is to explicitly convert int values 
to be median-ed to fractions.Fraction (or decimal.Decimal) ahead of time, so 
floating point math never gets involved, and the return type is consistent 
regardless of length.

--
nosy: +josh.r

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Sanyam Khurana]

Change by Sanyam Khurana :


--
pull_requests: +10999

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Sanyam Khurana]

Change by Sanyam Khurana :


--
pull_requests: +10999, 11000

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Senthil Kumaran]

Senthil Kumaran  added the comment:


New changeset 02e33d9567aa4bd612f9f08053acbfd5e68480d0 by Senthil Kumaran 
(Sanyam Khurana) in branch '2.7':
[2.7] bpo-24746: Avoid stripping trailing whitespace in doctest fancy diff 
(#11482)
https://github.com/python/cpython/commit/02e33d9567aa4bd612f9f08053acbfd5e68480d0


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35692] pathlib.Path.exists() on non-existent drive raises WinError instead of returning False

[Brett Cannon]

Change by Brett Cannon :


--
components: +Library (Lib), Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35198] Build issue while compiling cpp files in AIX

[Michael Felt]

Michael Felt  added the comment:

On 08/01/2019 15:40, Ayappan wrote:
> Ayappan  added the comment:
>
> Not sure what went wrong here.
> I used gcc & g++ and didn't hit this issue.
>
> --
>
> ___
> Python tracker 
> 
> ___
>
Well, it is probably an issue with xlc as I have vac.C and
vacpp.cmp.core installed (aka xlc and xlC). These days it seems only gcc
environment gets tested in depth and portability issues with "posix"
compilers get missed.

GCC is a fine compiler - just not the one I am using for a number of
"logistical" reasons.

Thanks for the update!

Michael

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35700] Place, Pack and Grid should return the widget

[Terry J. Reedy]

Terry J. Reedy  added the comment:

1. (Josh beat me here.)  One of Python's design features is that stdlib 
functions/methods that mutate (or register) an object never (as far as I can 
remember) return the object.  (If they return anything other than None, it is 
something other than the object.  List.pop returns a member, not the list.)  
Changing this rule either in particular cases or in general has been rejected 
by Guido multiple times.  A new proposal for particular exceptions would have 
to be approved by the still-in-the-future new design decision process.  It 
would likely start with posting to python-ideas list.

Consistency of this rule is a feature.  If people got used to writing 'item = 
Widget(...).geo_manager(...)', they would more often make the mistake of 
writing buggy code like 'items = lister().sort()'


2. (Based on experience with IDLE.)  The toy example with 3 one-line statements 
creating 3 blank Labels admittedly looks nice and neat.  And in such 
situations, can actually get close today.

label1 = tk.Label(root); label1.grid(row=0, column=0)
label2 = tk.Label(root); label2.grid(row=0, column=1)
label3 = tk.Label(root); label3.grid(row=0, column=2)

However, in real situations, the widget creation statement is often or usually 
in the body of a class method and starts with at least an 8 space indent.  The 
call nearly always has a content argument and often other configuration 
arguments.  Such statements often require more than one line even without the 
manager call added.  Manager calls may also have additional arguments.  The 
result is ragged code and if manager calls are appended, they are not so easy 
to pick out.

I believe a majority of experienced tkinter users prefer a style omitted from 
the opening example: create a batch of widgets; then lay them out.  The 
following untested example shows the idea.  It keeps the row and column numbers 
close together and includes parent grid calls in the layout section.

class Viewframe(Frame):
def __init__(self, parent, ...)
...
self.populate()
def populate(self):
label = Label(self, text='hello world', ...)
button = Button(self, text='press me), command=lambda: )
text = Text(self, ...)

label.grid(row=0, column=0)
button.grid(row=1, column=0)
text.grid(row=0, column=1, rowspan=2, sticky='NSEW')
self.columnconfigure(column=1, weight=1)

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35641] IDLE: calltips not properly formatted for functions without doc-strings

[Terry J. Reedy]

Change by Terry J. Reedy :


--
pull_requests:  -10995

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35641] IDLE: calltips not properly formatted for functions without doc-strings

[Terry J. Reedy]

Change by Terry J. Reedy :


--
pull_requests:  -10994

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35693] test_httpservers fails

[Jorge Ramos]

Jorge Ramos  added the comment:

Ok, thank you. Here are my findings:

steps taken:

1) download today's version of 3.7.2 and 3.8.0 alpha 0
2) navigate to tools/msi
3) run build.bat -x64 (to create amd64 folder under pcbuild)
4) navigate to pcbuild
5) run rt.bat -x64 -v test_httpservers

results:

1) FAILED for 3.7.2 (same as 3.6.8)
2) SUCCESS for 3.8.0 alpha 0

According to PEP-0537 python 3.7.2 is still under bugfixes, so, can I help in 
something to sort this out?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35693] test_httpservers fails

[Zachary Ware]

Zachary Ware  added the comment:

Certainly! Bugfixes, in library or test code, are still welcome on 3.7.

--
stage:  -> test needed
versions: +Python 3.7 -Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35693] test_httpservers fails

[Jorge Ramos]

Change by Jorge Ramos :


--
versions: +Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35674] Expose os.posix_spawnp()

[Pablo Galindo Salgado]

Pablo Galindo Salgado  added the comment:

I also think to expose posix_spawnp() as os.posix_spawnp() seems the more 
consistent thing to do as the os/posix module tries to mirror glibc as much as 
possible, which helps with discoverability and cross-reference with man pages.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35674] Expose os.posix_spawnp()

[STINNER Victor]

STINNER Victor  added the comment:

Pablo:
> I also think to expose posix_spawnp() as os.posix_spawnp() seems the more 
> consistent thing to do as the os/posix module tries to mirror glibc as much 
> as possible, which helps with discoverability and cross-reference with man 
> pages.

Ok. Let's do that.

@Joannah Nanjekye: Don't hesitate to come to me if you need my help to 
implement that ;-)

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35493] multiprocessing.Pool._worker_handler(): use SIGCHLD to be notified on worker exit

[Pablo Galindo Salgado]

Pablo Galindo Salgado  added the comment:

@Antoine Do you think we should start planning one of these long term solutions 
or we should start trying to use Process.sentinel as a short term solution for 
this particular issue?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue33437] Defining __init__ in enums

[Cheryl Sabella]

Change by Cheryl Sabella :


--
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35698] Division by 2 in statistics.median

[STINNER Victor]

STINNER Victor  added the comment:

> vstinner: The problem isn't the averaging, it's the type inconsistency.

>>> type(statistics.median([1]))

>>> type(statistics.median([1,2]))


Which consistency? :-)

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35493] multiprocessing.Pool._worker_handler(): use SIGCHLD to be notified on worker exit

[Antoine Pitrou]

Antoine Pitrou  added the comment:

If using Process.sentinel looks easy enough, then go for it.  Existing users of 
multiprocessing.Pool will benefit.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35699] distutils cannot find Build Tools 2017 since 3.7.2

[Steve Dower]

Steve Dower  added the comment:

Excellent catch! Are you interested in creating a PR?

Also, I don't recall whether we are handling multiple installs or not, but if 
we are not I would rather explicitly list the products that may include 
compilers than using "*" (since there are and will be more products that do 
not). If we're checking for installed packages as well and iterating over all 
results then "*" will be fine.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35693] test_httpservers fails

[Jorge Ramos]

Jorge Ramos  added the comment:

I have realized that results from rt.bat differ from those when running 
buildrelease.bat (see example below)
Why do the tests run OK in rt.bat but fail in buildrelase.bat?

To my best understanding, the tests are summoned directly via rt.bat but also 
from buildrelease.bat (because these are used to generate data for the PGO 
optimization process right?)- but when run from the buildrelease.bat file, the 
tests are in "silent" mode, just fatal errors are displayed at the command 
prompt as opposed to .

Is there a way to pass some arguments to buildrelease.bat so that the tests run 
in verbose mode? This is important, because that way i can know exactly which 
tests fail.

-

EXAMPLE

verbose from  in test_distutils:

0:03:57 [113/418] test_distutils
xxmodule.c
   Creando biblioteca 
D:\Users\yorch\AppData\Local\Temp\tmpy9gd5kib\Release\Users\yorch\AppData\Local\Temp\tmpy9gd5kib\xx.cp38-win_amd64.lib
 y objeto 
D:\Users\yorch\AppData\Local\Temp\tmpy9gd5kib\Release\Users\yorch\AppData\Local\Temp\tmpy9gd5kib\xx.cp38-win_amd64.exp
Generando código
Generación de código finalizada
foo.c
   Creando biblioteca 
D:\Users\yorch\AppData\Local\Temp\tmpxp_bpi50\tempt\Users\yorch\AppData\Local\Temp\tmpmz5_h8sb\foo.cp38-win_amd64.lib
 y objeto 
D:\Users\yorch\AppData\Local\Temp\tmpxp_bpi50\tempt\Users\yorch\AppData\Local\Temp\tmpmz5_h8sb\foo.cp38-win_amd64.exp
Generando código
Generación de código finalizada
foo.c
   Creando biblioteca 
D:\Users\yorch\AppData\Local\Temp\tmpxp_bpi50\tempt\Users\yorch\AppData\Local\Temp\tmpmz5_h8sb\foo.cp38-win_amd64.lib
 y objeto 
D:\Users\yorch\AppData\Local\Temp\tmpxp_bpi50\tempt\Users\yorch\AppData\Local\Temp\tmpmz5_h8sb\foo.cp38-win_amd64.exp
Generando código
Generación de código finalizada
xxmodule.c
   Creando biblioteca 
D:\Users\yorch\AppData\Local\Temp\tmptd13yi9i\Release\Users\yorch\AppData\Local\Temp\tmptd13yi9i\xx.cp38-win_amd64.lib
 y objeto 
D:\Users\yorch\AppData\Local\Temp\tmptd13yi9i\Release\Users\yorch\AppData\Local\Temp\tmptd13yi9i\xx.cp38-win_amd64.exp
Generando código
Generación de código finalizada
foo.c
   Creando biblioteca 
D:\Users\yorch\AppData\Local\Temp\tmp4ttgsjp5\tempt\Users\yorch\AppData\Local\Temp\tmp1yxs7b6r\foo.cp38-win_amd64.lib
 y objeto 
D:\Users\yorch\AppData\Local\Temp\tmp4ttgsjp5\tempt\Users\yorch\AppData\Local\Temp\tmp1yxs7b6r\foo.cp38-win_amd64.exp
Generando código
Generación de código finalizada
foo.c
   Creando biblioteca 
D:\Users\yorch\AppData\Local\Temp\tmp4ttgsjp5\tempt\Users\yorch\AppData\Local\Temp\tmp1yxs7b6r\foo.cp38-win_amd64.lib
 y objeto 
D:\Users\yorch\AppData\Local\Temp\tmp4ttgsjp5\tempt\Users\yorch\AppData\Local\Temp\tmp1yxs7b6r\foo.cp38-win_amd64.exp
Generando código
Generación de código finalizada
xxmodule.c
   Creando biblioteca build\temp.win-amd64-3.8\Release\xx.cp38-win_amd64.lib y 
objeto build\temp.win-amd64-3.8\Release\xx.cp38-win_amd64.exp
Generando código
Generación de código finalizada

E:\RepoGiT\3.8\build\test_python_2512>exit 1

E:\RepoGiT\3.8\build\test_python_2512>exit 0
0:04:41 [114/418] test_docxmlrpc -- test_distutils passed in 44 sec 267 ms
***

verbose from buildrelease.bat -x64 from test_distutils
***
xxmodule.c
E:\RepoGiT\3.8\include\Python.h(8): fatal error C1083: No se puede abrir el 
archivo incluir: 'pyconfig.h': No such file or directory
foo.c
   Creando biblioteca 
D:\Users\yorch\AppData\Local\Temp\tmpwzeadhd1\tempt\Users\yorch\AppData\Local\Temp\tmp196_7v3c\foo.cp38-win_amd64.lib
 y objeto 
D:\Users\yorch\AppData\Local\Temp\tmpwzeadhd1\tempt\Users\yorch\AppData\Local\Temp\tmp196_7v3c\foo.cp38-win_amd64.exp
Generando código
Generación de código finalizada
foo.c
   Creando biblioteca 
D:\Users\yorch\AppData\Local\Temp\tmpwzeadhd1\tempt\Users\yorch\AppData\Local\Temp\tmp196_7v3c\foo.cp38-win_amd64.lib
 y objeto 
D:\Users\yorch\AppData\Local\Temp\tmpwzeadhd1\tempt\Users\yorch\AppData\Local\Temp\tmp196_7v3c\foo.cp38-win_amd64.exp
Generando código
Generación de código finalizada
xxmodule.c
E:\RepoGiT\3.8\include\Python.h(8): fatal error C1083: No se puede abrir el 
archivo incluir: 'pyconfig.h': No such file or directory
foo.c
   Creando biblioteca 
D:\Users\yorch\AppData\Local\Temp\tmp9093ml9w\tempt\Users\yorch\AppData\Local\Temp\tmpsn45j3j7\foo.cp38-win_amd64.lib
 y objeto 
D:\Users\yorch\AppData\Local\Temp\tmp9093ml9w\tempt\Users\yorch\AppData\Local\Temp\tmpsn45j3j7\foo.cp38-win_amd64.exp
Generando código
Generación de código finalizada
foo.c
   Creando biblioteca 
D:\Users\yorch\AppData\Local\Temp\tmp9093ml9w\tempt\Users\yorch\AppData\Local\Temp\tmpsn45j3j7\foo.cp38-win_amd64.lib
 y objeto 
D:\Users\yorch\AppData\Local\Temp\tmp9093ml9w\tempt\Users\yorch\AppData\Local\Temp\tmpsn45j3j7\foo.cp38-win_amd6

[issue35404] Document how to import _structure in email.message

[Brian Curtin]

Brian Curtin  added the comment:


New changeset e394ba32147f687b6bc7518d461f1d84211698e0 by Brian Curtin 
(Charles-Axel Dein) in branch 'master':
bpo-35404: Clarify how to import _structure in email.message doc (GH-10886)
https://github.com/python/cpython/commit/e394ba32147f687b6bc7518d461f1d84211698e0


--
nosy: +brian.curtin

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35493] multiprocessing.Pool._worker_handler(): use SIGCHLD to be notified on worker exit

[Pablo Galindo Salgado]

Change by Pablo Galindo Salgado :


--
keywords: +patch, patch, patch
pull_requests: +11001, 11002, 11003
stage:  -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com