[issue46089] Problems with AF_PACKET sockets

[Ethan Furman]

Ethan Furman  added the comment:

Thank you for the thorough report.  Do you feel comfortable writing that 
missing documentation?

--
nosy: +ethan.furman

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

[issue46089] Problems with AF_PACKET sockets

[Ethan Furman]

Ethan Furman  added the comment:

To contribute you'll need to sign a Contributor's License Agreement [1].

After that, anything you can do to help will move this forward.  You may not be 
aware, but Python is developed primarily by volunteers, which unfortunately 
means that time is normally spent on bugs that the volunteers are interested in 
-- and nobody else seems interested in this one (which probably means not many 
people use this functionality).

If you have time, perhaps you could write some tests?  They would obviously 
fail at the moment, but would help when somebody wants to fix the code itself.


[1] https://www.python.org/psf/contrib/contrib-form/

--
assignee: docs@python -> 

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

[issue46108] Enum repr() incorrect when mixed with dataclasses

[Ethan Furman]

New submission from Ethan Furman :

from dataclasses import dataclass
from enum import Enum

@dataclass
class Foo:
a: int = 0

class Entries(Foo, Enum):
ENTRY1 = Foo(1)

repr(Entries.ENTRY1) != ''

--
assignee: ethan.furman
messages: 408748
nosy: ethan.furman
priority: normal
severity: normal
status: open
title: Enum repr() incorrect when mixed with dataclasses
versions: Python 3.10, Python 3.11, Python 3.8, Python 3.9

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

[issue46108] Enum repr() incorrect when mixed with non-__new__ data types

[Ethan Furman]

Ethan Furman  added the comment:

Thanks, test added.  I also updated the title.

Code updated to treat any __repr__s as affecting the display of the member 
value instead of the member itself (i.e. the "<...: %r>" portion).  if a user 
actually wants to change the member repr they can assign it when creating the 
Enum:

class Entries(Foo, Enum):
ENTRY = 1
__repr__ = Foo.__repr__

assert repr(Entries.ENTRY1) == 'Entries(a=1)'

--
title: Enum repr() incorrect when mixed with dataclasses -> Enum repr() 
incorrect when mixed with non-__new__ data types

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

[issue46126] Unittest output drives developers to avoid docstrings

[Ethan Furman]

Ethan Furman  added the comment:

Could you give a couple examples for those of us not familiar with the problem?

--
nosy: +ethan.furman

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

[issue46132] Attempting to create an enum with slots silently fails

[Ethan Furman]

Change by Ethan Furman :


--
assignee:  -> ethan.furman

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

[issue46132] Consider adding __slots__ to enums?

[Ethan Furman]

Ethan Furman  added the comment:

Some testing reveals that `__slots__` is not a good option for Enum -- it makes 
it impossible to mix in in other types such as `int`.

--

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

[issue23952] cgi: Document the 'maxlen' member of the cgi module

[Ethan Furman]

Change by Ethan Furman :


--
nosy: +ethan.furman

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

[issue46262] Enum tests: Error path in `_missing_()` is not covered for `Flag` and `IntFlag`

[Ethan Furman]

Change by Ethan Furman :


--
assignee:  -> ethan.furman
nosy: +ethan.furman

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

[issue46262] Enum tests: Error path in `_missing_()` is not covered for `Flag` and `IntFlag`

[Ethan Furman]

Ethan Furman  added the comment:


New changeset 91bc6f9615eabb10090e2e4f0fe5913885a29c8c by Nikita Sobolev in 
branch 'main':
bpo-46262: [Enum] test error path in `Flag._missing_` (GH-30408)
https://github.com/python/cpython/commit/91bc6f9615eabb10090e2e4f0fe5913885a29c8c


--

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

[issue46262] Enum tests: Error path in `_missing_()` is not covered for `Flag` and `IntFlag`

[Ethan Furman]

Change by Ethan Furman :


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

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

[issue46269] '__new__' is never shown in `dir(SomeEnum)`

[Ethan Furman]

Ethan Furman  added the comment:


New changeset 817a6bc9f7b802511c4d42273a621c556a48870b by Nikita Sobolev in 
branch 'main':
bpo-46269: [Enum] remove special-casing of `__new__` in `EnumType.__dir__` 
(GH-30421)
https://github.com/python/cpython/commit/817a6bc9f7b802511c4d42273a621c556a48870b


--

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

[issue46296] Unreachable condition: `if enum_class._member_type_ is object`

[Ethan Furman]

Ethan Furman  added the comment:

(2) is false.

>>> from enum import Enum
>>> 
>>> class MyEnum(Enum):
... def __new__(cls, value):
... member = object.__new__(cls)
... return member
... ONE = 1
... 

>>> MyEnum.ONE
MyEnum.ONE

>>> MyEnum._use_args_
True

>>> MyEnum._member_type_


If coverage shows a branch not being tested, design a test for it instead of 
removing the branch.

--
assignee:  -> ethan.furman
nosy: +ethan.furman
stage: patch review -> test needed

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

[issue46296] Unreachable condition: `if enum_class._member_type_ is object`

[Ethan Furman]

Ethan Furman  added the comment:

Looking through some of my code that prompted that branch, the issue is caused 
when `_generate_next_value_` modifies the given args -- when `__set_name__` 
runs it has no way of getting the same results to automatically create the 
`_value_` attribute.

--

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

[issue46296] Unreachable condition: `if enum_class._member_type_ is object`

[Ethan Furman]

Change by Ethan Furman :


--
Removed message: https://bugs.python.org/msg410029

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

[issue46296] Unreachable condition: `if enum_class._member_type_ is object`

[Ethan Furman]

Ethan Furman  added the comment:


New changeset 74d1663580d1914bd110c3ab7282451f5e2cd2b5 by Nikita Sobolev in 
branch 'main':
bpo-46296: [Enum] add a test for missing `value` recovery (GH-30458)
https://github.com/python/cpython/commit/74d1663580d1914bd110c3ab7282451f5e2cd2b5


--

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

[issue46296] Unreachable condition: `if enum_class._member_type_ is object`

[Ethan Furman]

Ethan Furman  added the comment:

Thank you, Nikita!

--
resolution:  -> fixed
stage: test needed -> resolved
status: open -> closed

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

[issue46301] Enum tests: One branch is not covered in `Enum._convert_`

[Ethan Furman]

Change by Ethan Furman :


--
assignee:  -> ethan.furman

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

[issue46301] Enum tests: One branch is not covered in `Enum._convert_`

[Ethan Furman]

Ethan Furman  added the comment:

Alex, thanks for nosying me.  Go ahead and make Enum issues assigned to me as 
well.  :-)

--

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

[issue46301] Enum tests: One branch is not covered in `Enum._convert_`

[Ethan Furman]

Ethan Furman  added the comment:


New changeset 8d59d2563b914b7208779834895c080c70cd94dd by Nikita Sobolev in 
branch 'main':
bpo-46301: [Enum] test uncomparable values in `_convert_` (GH-30472)
https://github.com/python/cpython/commit/8d59d2563b914b7208779834895c080c70cd94dd


--

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

[issue46301] Enum tests: One branch is not covered in `Enum._convert_`

[Ethan Furman]

Change by Ethan Furman :


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

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

[issue46301] Enum tests: One branch is not covered in `Enum._convert_`

[Ethan Furman]

Ethan Furman  added the comment:

Reverting.

Nikita, you can use the command:

./python -m test.regrtest -R : test_enum

to show the leaks and hopefully track them down.  The half-hour I spent yielded 
no clues.

--

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

[issue46301] Enum tests: One branch is not covered in `Enum._convert_`

[Ethan Furman]

Change by Ethan Furman :


--
Removed message: https://bugs.python.org/msg410184

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

[issue46301] Enum tests: One branch is not covered in `Enum._convert_`

[Ethan Furman]

Ethan Furman  added the comment:


New changeset 582286d71c7ee61f5376a846a83c7be4a5727636 by Nikita Sobolev in 
branch 'main':
bpo-46301: [Enum] fix refleak tests (GH30510)
https://github.com/python/cpython/commit/582286d71c7ee61f5376a846a83c7be4a5727636


--

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

[issue46327] `test_enum` contains tests for older versions of python

[Ethan Furman]

Ethan Furman  added the comment:


New changeset 13e4659276c2af2fa5b0f2b3a31dcd69064868ef by Nikita Sobolev in 
branch 'main':
bpo-46327: [Enum] remove skipped tests (GH-30512)
https://github.com/python/cpython/commit/13e4659276c2af2fa5b0f2b3a31dcd69064868ef


--

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

[issue45331] Can create enum of ranges, cannot create range enum. Range should be subclassable... or EnumMeta.__new__ should be smarter.

[Ethan Furman]

Ethan Furman  added the comment:


New changeset 6223cbf86ad7d5e6d12f9747e5a9cf1d8c72bdc8 by Nikita Sobolev in 
branch 'main':
bpo-45331: [Enum] add rule to docs that mixin type must be subclassable 
(GH-30521)
https://github.com/python/cpython/commit/6223cbf86ad7d5e6d12f9747e5a9cf1d8c72bdc8


--

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

[issue22506] `dir` on Enum subclass doesn't expose parent class attributes

[Ethan Furman]

Ethan Furman  added the comment:

Ram asked:
-
> Also, aren't you excluding a lot of important magic methods from that `dir`?

Ethan replied:
-
> We decided the dunder methods were not interesting, so declined to include
> them in the listing.  And no, we are not changing our minds on that.  ;)

--

UPDATE:  We have changed our minds, but only for enums that have a data type, 
such as `int` or `str`, mixed in.  This behavior should be in 3.11.

--

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

[issue40066] Enum: modify __repr__, __str__; update docs

[Ethan Furman]

Change by Ethan Furman :


--
pull_requests: +28780
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/30582

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

[issue46242] Improve error message when attempting to extend an enum with `__call__`

[Ethan Furman]

Ethan Furman  added the comment:


New changeset e674e48ddc2712f28cc7ecdc66a6c328066694b0 by Nikita Sobolev in 
branch 'main':
bpo-46242: [Enum] better error message for extending `Enum` with members 
(GH-30357)
https://github.com/python/cpython/commit/e674e48ddc2712f28cc7ecdc66a6c328066694b0


--

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

[issue40066] Enum: modify __repr__, __str__; update docs

[Ethan Furman]

Ethan Furman  added the comment:


New changeset acf7403f9baea3ae1119fc6b4a3298522188bf96 by Ethan Furman in 
branch 'main':
bpo-40066:  [Enum] update str() and format() output (GH-30582)
https://github.com/python/cpython/commit/acf7403f9baea3ae1119fc6b4a3298522188bf96


--

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

[issue40066] Enum: modify __repr__, __str__; update docs

[Ethan Furman]

Ethan Furman  added the comment:

After merging in doc fix by kumaraditya303, I'll update tests so Solaris passes.

--

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

[issue40066] Enum: modify __repr__, __str__; update docs

[Ethan Furman]

Ethan Furman  added the comment:


New changeset 83d544b9292870eb44f6fca37df0aa351c4ef83a by Kumar Aditya in 
branch 'main':
bpo-40066: [Enum] skip failing doc test (GH-30637)
https://github.com/python/cpython/commit/83d544b9292870eb44f6fca37df0aa351c4ef83a


--

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

[issue40066] Enum: modify __repr__, __str__; update docs

[Ethan Furman]

Ethan Furman  added the comment:

vstinner wrote:
--
>>self.assertEqual(repr(type), '')

> For this one, I suggest to replace the value with "..." doctest pattern.

That bit of code is from the unittest suite, not the doctest suite.

I went with:  

self.assertEqual(repr(type), '' % type.value)

--

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

[issue40066] Enum: modify __repr__, __str__; update docs

[Ethan Furman]

Change by Ethan Furman :


--
pull_requests: +28846
pull_request: https://github.com/python/cpython/pull/30643

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

[issue40066] Enum: modify __repr__, __str__; update docs

[Ethan Furman]

Ethan Furman  added the comment:


New changeset 62a6594e66ca955073be2f4e5a40291a39252ef3 by Ethan Furman in 
branch 'main':
bpo-40066: [Enum] fix tests (GH-30643)
https://github.com/python/cpython/commit/62a6594e66ca955073be2f4e5a40291a39252ef3


--

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

[issue40066] Enum: modify __repr__, __str__; update docs

[Ethan Furman]

Change by Ethan Furman :


--
priority: release blocker -> normal
resolution:  -> fixed
stage: patch review -> resolved

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

[issue46108] Enum repr() incorrect when mixed with non-__new__ data types

[Ethan Furman]

Ethan Furman  added the comment:

Fixed in 3.11.

--
resolution:  -> fixed
stage:  -> resolved
status: open -> closed
superseder:  -> Enum: modify __repr__, __str__; update docs
type:  -> behavior

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

[issue45535] Enum's dir() does not contain inherited members

[Ethan Furman]

Ethan Furman  added the comment:

Fixed in 3.11.

Pure enums have a few more dir() entries now; mixed enums now show all 
inherited methods/attributes -- members still do not show up in member dirs 
(this is a good thing).

--
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
superseder:  -> Enum: modify __repr__, __str__; update docs

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

[issue46418] Simplify `MODULE` variable in `test_enum.py`

[Ethan Furman]

Ethan Furman  added the comment:


New changeset 596cf51a4d40f1ac3090cbccb83ad0663d739ae2 by Nikita Sobolev in 
branch 'main':
bpo-46418: [Enum] simplify `MODULE` declaration in tests (GH-30647)
https://github.com/python/cpython/commit/596cf51a4d40f1ac3090cbccb83ad0663d739ae2


--

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

[issue43430] Exception raised when attempting to create Enum via functional API

[Ethan Furman]

Ethan Furman  added the comment:

Thanks for the reminder.

--
resolution:  -> not a bug
stage:  -> resolved
status: pending -> closed

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

[issue46425] Multiple test modules fail to run if invoked directly

[Ethan Furman]

Ethan Furman  added the comment:

I suggest your grouping of PRs be by error type -- so have batches of "relative 
import" fixes and batches of "TESTFN" fixes, etc.

--
nosy: +ethan.furman

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

[issue45535] Enum's dir() does not contain inherited members

[Ethan Furman]

Change by Ethan Furman :


--
pull_requests: +28877
pull_request: https://github.com/python/cpython/pull/30677

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

[issue45535] Enum's dir() does not contain inherited members

[Ethan Furman]

Ethan Furman  added the comment:


New changeset 7c0914d35eaaab2f323260ba5fe8884732533888 by Ethan Furman in 
branch 'main':
bpo-45535: [Enum] include special dunders in dir() (GH-30677)
https://github.com/python/cpython/commit/7c0914d35eaaab2f323260ba5fe8884732533888


--

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

[issue40066] Enum: modify __repr__, __str__; update docs

[Ethan Furman]

Change by Ethan Furman :


--
status: open -> closed

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

[issue46477] Enum: ensure bitwise operators on subclasses are correct

[Ethan Furman]

New submission from Ethan Furman :

Creating one's own int Flag type doesn't work properly with regards to the 
bitwise operators:

class MyIntFlag(int, Flag):
ONE = 1
TWO = 2
FOUR = 4

MyIntFlag.ONE | MyIntFlag.TWO
# 

MyIntFlag.ONE | 2
# 3

--
assignee: ethan.furman
messages: 411319
nosy: ethan.furman
priority: normal
severity: normal
status: open
title: Enum: ensure bitwise operators on subclasses are correct
type: behavior
versions: Python 3.11

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

[issue46477] Enum: ensure bitwise operators on subclasses are correct

[Ethan Furman]

Change by Ethan Furman :


--
keywords: +patch
pull_requests: +29003
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/30816

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

[issue46477] Enum: ensure bitwise operators on subclasses are correct

[Ethan Furman]

Ethan Furman  added the comment:


New changeset 353e3b2820bed38da16140276786eef9ba33d3bd by Ethan Furman in 
branch 'main':
bpo-46477: [Enum] ensure Flag subclasses have correct bitwise methods (GH-30816)
https://github.com/python/cpython/commit/353e3b2820bed38da16140276786eef9ba33d3bd


--

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

[issue46103] inspect.getmembers will call the instance __bases__ attribute, which may cause an exception

[Ethan Furman]

Ethan Furman  added the comment:


New changeset 691506f4e9408a1205166f99640946ad7822e302 by Weipeng Hong in 
branch 'main':
bpo-46103: Fix inspect.getmembers to only get __bases__ from class (GH-30147)
https://github.com/python/cpython/commit/691506f4e9408a1205166f99640946ad7822e302


--

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

[issue46569] final note on StrEnum documentation incorrectly refers to int.__format__ instead of str.__format__

[Ethan Furman]

Ethan Furman  added the comment:

Good catch, thank you both.

--

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

[issue46569] final note on StrEnum documentation incorrectly refers to int.__format__ instead of str.__format__

[Ethan Furman]

Ethan Furman  added the comment:


New changeset 734b1f119be6f0dcd6845c78a9e0a71d88a90b59 by Nikita Sobolev in 
branch 'main':
bpo-46569: [Enum] fix typo in `StrEnum` docs (GH-31007)
https://github.com/python/cpython/commit/734b1f119be6f0dcd6845c78a9e0a71d88a90b59


--

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

[issue46569] final note on StrEnum documentation incorrectly refers to int.__format__ instead of str.__format__

[Ethan Furman]

Change by Ethan Furman :


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

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

[issue46586] In documentation contents enum.property erroneously links to built-in property

[Ethan Furman]

Ethan Furman  added the comment:

What does the tilde (~) do?

--

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

[issue31369] re.RegexFlag is not included in __all__, makes type inference less useful

[Ethan Furman]

Ethan Furman  added the comment:


New changeset fea7290a0ecee09bbce571d4d10f5881b7ea3485 by andrei kulakov in 
branch 'main':
bpo-31369: include ``RegexFlag`` in ``re.__all__`` (GH-30279)
https://github.com/python/cpython/commit/fea7290a0ecee09bbce571d4d10f5881b7ea3485


--

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

[issue31369] re.RegexFlag is not included in __all__, makes type inference less useful

[Ethan Furman]

Ethan Furman  added the comment:

Thanks, everyone!

--
components: +Library (Lib) -Regular Expressions
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
type:  -> behavior
versions: +Python 3.11 -Python 3.7, Python 3.8

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

[issue23952] cgi: Document the 'maxlen' member of the cgi module

[Ethan Furman]

Ethan Furman  added the comment:


New changeset 6c4e44ef8ab550f846ba056d4561efb8256b8eab by Hugo van Kemenade in 
branch 'main':
bpo-23952: Document cgi module's maxlen variable (GH-30338)
https://github.com/python/cpython/commit/6c4e44ef8ab550f846ba056d4561efb8256b8eab


--

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

[issue23952] cgi: Document the 'maxlen' member of the cgi module

[Ethan Furman]

Change by Ethan Furman :


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

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

[issue46586] In documentation contents enum.property erroneously links to built-in property

[Ethan Furman]

Ethan Furman  added the comment:

In case a future reader has the same question:

A tilde (~) creates a link to whatever follows (so `enum.property` above), but 
only shows the last segment in the text (so `property`).

--

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

[issue46586] In documentation contents enum.property erroneously links to built-in property

[Ethan Furman]

Change by Ethan Furman :


--
Removed message: https://bugs.python.org/msg412634

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

[issue46717] Raising exception multiple times leaks memory

[Ethan Furman]

Change by Ethan Furman :


--
nosy: +ethan.furman

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

[issue46586] In documentation contents enum.property erroneously links to built-in property

[Ethan Furman]

Ethan Furman  added the comment:


New changeset 9d9cfd61ec3cbe84dbc25c74f664877f3d02b8ef by Meer Suri in branch 
'main':
bpo-46586: Fix documentation links (GH-31216)
https://github.com/python/cpython/commit/9d9cfd61ec3cbe84dbc25c74f664877f3d02b8ef


--

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

[issue46885] Ensure PEP 663 changes are reverted from 3.11

[Ethan Furman]

Ethan Furman  added the comment:

This has been taken care of in issue40066.

--

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

[issue46885] Ensure PEP 663 changes are reverted from 3.11

[Ethan Furman]

Change by Ethan Furman :


--
priority: release blocker -> high

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

[issue46922] tarfile.TarFile.next() crashes on empty tar files

[Ethan Furman]

Change by Ethan Furman :


--
nosy: +ethan.furman

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

[issue6549] ttk.Style not translating some Tcl options

[Ethan Furman]

Ethan Furman  added the comment:

Not sure what 'embossed' has to do with not having dashes as part of the 
element option names.

Attached is a patch (hopefully in the right format) agains the current 3.3 
sources to remove the dash from the names in .element_names(), as well as 
return None from .configure() when setting options.

--
keywords: +patch
nosy: +stoneleaf
Added file: http://bugs.python.org/file23222/ttk.patch

___
Python tracker 
<http://bugs.python.org/issue6549>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6549] ttk.Style not translating some Tcl options

[Ethan Furman]

Ethan Furman  added the comment:

The changes to Style.configure were not good.  Corrected so the (possibly 
empty) result is returned when a query is made but not when configuration is 
set.

Two patches: one for the element_names issue, one for the configure issue.

Question:  Does it ever make sense to do both a query and a configuration 
update in the same call?  I don't think it is:

--> ttk.Style.configure('TButton', 'relief', relief='sunken'
'raised'
--> s.configure('TButton','relief')
'raised'

Does it make sense to raise an exception in configure if both query_opt and kw 
specified?

--
Added file: http://bugs.python.org/file23223/ttk_style_fixes.zip

___
Python tracker 
<http://bugs.python.org/issue6549>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6549] ttk.Style -- minor issues with element_names and configure

[Ethan Furman]

Changes by Ethan Furman :


--
title: ttk.Style not translating some Tcl options -> ttk.Style -- minor issues 
with element_names and configure

___
Python tracker 
<http://bugs.python.org/issue6549>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6549] ttk.Style -- minor issues with element_names and configure

[Ethan Furman]

Changes by Ethan Furman :


--
nosy: +terry.reedy

___
Python tracker 
<http://bugs.python.org/issue6549>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6210] Exception Chaining missing method for suppressing context

[Ethan Furman]

Ethan Furman  added the comment:

Okay, I like Matthew Barnett's idea of 

except SomeError [as e]:
raise as SomeOtherError('...')

This would require a change to the grammer as well, yes?  From:

raise_stmt: 'raise' [test ['from' test]]

to

raise_stmt: 'raise' [test ['from' test]] | 'raise' 'as' [test ['from' test]]

--

___
Python tracker 
<http://bugs.python.org/issue6210>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6210] Exception Chaining missing method for suppressing context

[Ethan Furman]

Changes by Ethan Furman :


--
nosy: +stoneleaf

___
Python tracker 
<http://bugs.python.org/issue6210>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6210] Exception Chaining missing method for suppressing context

[Ethan Furman]

Ethan Furman  added the comment:

I like MRAB's suggestion best:

MRAB wrote:
> Suggestion: an explicit 'raise' in the exception handler excludes the
> context, but if you want to include it then 'raise with'. For example:
>
> # Exclude the context
> try:
> command_dict[command]()
> except KeyError:
> raise CommandError("Unknown command")
>
> # Include the context
> try:
> command_dict[command]()
> except KeyError:
> raise with CommandError("Unknown command")

I think we can even strike off the verbiage "in the exception handler"... that 
way, raise always does the same thing -- raise KeyError will raise a KeyError, 
always, not sometimes a KeyError and sometimes a KeyError nested in a 
WhatEverError.

--

___
Python tracker 
<http://bugs.python.org/issue6210>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6210] Exception Chaining missing method for suppressing context

[Ethan Furman]

Ethan Furman  added the comment:

> There is already support for this in the traceback module (see the
> "chain" parameter to various funcs).

I'm not sure how that's going to help as I don't want my library code to be 
responsible for printing out exceptions, I just want them to print reasonably 
-- and it seems very unreasonable to have the exception I'm converting /from/ 
show up in the traceback.

--

___
Python tracker 
<http://bugs.python.org/issue6210>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6210] Exception Chaining missing method for suppressing context

[Ethan Furman]

Ethan Furman  added the comment:

> Besides, if you are writing library code (as opposed to application
> code), you shouldn't care at all how tracebacks are displayed, should
> you?

I care when it lies:

During handling of the above exception, another exception occurred:

This is a blatant falsehood -- another exception did not occur, a different 
exception was raised.

Now, when another exception does actually occur, I'm all for the nested 
traceback, but if I'm raising a different one, why is this useful:

--> d.address
Traceback (most recent call last):
  File "nested_exceptions.py", line 7, in __getattr__
return self.data[self.names.index(name)]
ValueError: tuple.index(x): x not in tuple

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "", line 1, in 
  File "nested_exceptions.py", line 9, in __getattr__
raise AttributeError("Attribute %s does not exist" % name)
AttributeError: Attribute address does not exist

?

Furthermore, I use my own library, and have no interest in seeing extra, 
completely unnecessary, and wrong (verbiage, anyway) traceback info -- not in 
my own libraries, nor in other's that I may be using.

Keep the nesting for when an exception actually occurs, not for when an 
exception is, under programmer control, being modified/changed.

--

___
Python tracker 
<http://bugs.python.org/issue6210>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6210] Exception Chaining missing method for suppressing context

[Ethan Furman]

Ethan Furman  added the comment:

>> During handling of the above exception, another exception occurred:
>> 
>> This is a blatant falsehood -- another exception did not occur, a
>> different exception was raised.
> 
> This doesn't make any difference in any other context, so why would it
> here?

I'm not sure I understand what you are saying -- could you rephrase?


> By the way, this is all described in detail in a PEP:
> http://www.python.org/dev/peps/pep-3134/

Yes, I know -- and from the PEP:

Rationale

The Python-Dev discussions revealed interest in exception chaining
for two quite different purposes.  To handle the unexpected raising
of a secondary exception, the exception must be retained implicitly.
To support intentional translation of an exception, there must be a
way to chain exceptions explicitly.  This PEP addresses both.

Open Issue: Suppressing Context

As written, this PEP makes it impossible to suppress '__context__',
since setting exc.__context__ to None in an 'except' or 'finally'
clause will only result in it being set again when exc is raised.

The two motivations are excellent, and I have no issue with them; what I have 
issue with is that it is no longer possible to discard previous context.  If I 
want to change the error message, I can use

except ValueError as exc:
raise AttributeError("blah") from exc

and then get

  The above exception was the direct cause of the following exception

I would also like to see:

except ValueError as exc:
raise AttributeError("blah") with exc

to get 

  During handling of the above exception, another exception occurred

which would be the same as:

1/0

to get

  During handling of the above exception, another exception occurred

and, finally, if all I have is 

except ValueError as exc:
raise AttributeError("blah")

I just get the normal, previous context free, traceback.

--

___
Python tracker 
<http://bugs.python.org/issue6210>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6210] Exception Chaining missing method for suppressing context

[Ethan Furman]

Ethan Furman  added the comment:

> And what if the exception is raised from a subroutine?

Well, if I have it surrounded by a try/except block, presumably I'm aware that 
an exception could be raised.  ;)

And if I'm aware that an exception could be raised, it may also be possible 
that I want to change the exception -- leading to the three possibilities I 
described earlier.  

Looking through my dbf module, most of those re-raises I'll be changing to use 
the raise ... from ... syntax, but there are still a couple places where it 
makes no sense to have the extra nested information available.

--

___
Python tracker 
<http://bugs.python.org/issue6210>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6210] Exception Chaining missing method for suppressing context

[Ethan Furman]

Ethan Furman  added the comment:

> I'm talking about the exception raised from the except block.

So was I -- why should this:

try:
x = y / z
except ZeroDivisionError as exc:
raise InvalidInput()

be different from this:

try:
x = divide_and_conquer(y, z)
except ZeroDivisionError as exc:
raise InvalidInput()

?

In both cases I want to discard the previous exception, and raise my own in its 
place (without the nesting, in this example).

--

___
Python tracker 
<http://bugs.python.org/issue6210>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6210] Exception Chaining missing method for suppressing context

[Ethan Furman]

Ethan Furman  added the comment:

> I said the *except* block, not the *try* block ;)

Ah.  So you did.

Okay, if I'm understanding correctly, the scenario you are talking about 
involves the code in the except block calling some other function, and that 
other function is raising an exception...  seems unlikely that this would be a 
case of transforming one exception into another, therefore the raise should not 
suppress the context by default...  okay, I'll concede the point.

Looks like the best option, then, is Nick's idea of the .no_context() method on 
exceptions.

--
versions: +Python 3.2 -Python 3.3

___
Python tracker 
<http://bugs.python.org/issue6210>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6210] Exception Chaining missing method for suppressing context

[Ethan Furman]

Changes by Ethan Furman :


--
versions: +Python 3.3 -Python 3.2

___
Python tracker 
<http://bugs.python.org/issue6210>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6210] Exception Chaining missing method for suppressing context

[Ethan Furman]

Ethan Furman  added the comment:

raise AttributeError from None

makes sense to me, and in a nice, short example like that I prefer it. 
In real code, however, I think

raise AttributeError.no_context("Field %s is not in table" % attr)

is going to be easier for the human to parse than

raise AttributeError("Field %s is not in table" % attr) from None

--

___
Python tracker 
<http://bugs.python.org/issue6210>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue47063] SimpleHTTPRequestHandler has hard coded index page list.

[Ethan Furman]

Ethan Furman  added the comment:

`index.htm[l]` is pretty standard for the name of the index page.  What's your 
use-case for wanting different names?  Keep in mind that the word `Simple` is 
in the name for a reason.

--
nosy: +ethan.furman
versions: +Python 3.11 -Python 3.8

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

[issue47111] ENUM TypeError using mixing

[Ethan Furman]

Change by Ethan Furman :


--
nosy: +ethan.furman

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

[issue46126] Unittest output drives developers to avoid docstrings

[Ethan Furman]

Ethan Furman  added the comment:

Perhaps we could make an enhancement then?  Having the extra information on a 
separate line is, at least for me, very jarring -- as in, I hadn't figured out 
that that was the way it was done until Inadasan pointed it out.

Perhaps a command-line switch to enable having it all on one line?  That would 
also help when grepping.  (I would propose it to be the default behavior, but I 
can see that that would result in very long lines.)

--

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

[issue47133] enhance unittest to show test name and docstring on one line

[Ethan Furman]

New submission from Ethan Furman :

When running unittest with the -v flag, if a test has errors, and has a 
docstring, the test name is shown on one line, and the docstring is shown on 
the next line -- and the ERROR word is shown with the docstring.

What this means is that:
- the test name is easily missed by anyone who isn't aware of that (I only 
recently found out when someone else pointed it out to me)
- grepping for ERROR doesn't reveal the test name, necessitating a search 
through the testing code to find the test that failed

There are two possible solutions, and the selection of which one should be 
discussed on python-dev:
- print the name and docstring, and ERROR, all on one line; or
- provide a command-line switch to select that behavior

---

For the experienced developers who see this:  please leave the issue for one of 
the new developers subscribed to core-mentorship.  Thank you.

--
components: Tests
messages: 416090
nosy: ethan.furman
priority: low
severity: normal
stage: needs patch
status: open
title: enhance unittest to show test name and docstring on one line
type: enhancement
versions: Python 3.11

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

[issue46126] Unittest output drives developers to avoid docstrings

[Ethan Furman]

Ethan Furman  added the comment:

That makes sense.

issue47133 created.

--

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

[issue47133] enhance unittest to show test name and docstring on one line

[Ethan Furman]

Change by Ethan Furman :


--
assignee:  -> ethan.furman

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

[issue14265] Fully qualified test name in failure output

[Ethan Furman]

Ethan Furman  added the comment:

Hopefully somebody on the core-mentorship list can move this forward by 
converting to a PR and reviewing.

If @palaviv is still active the review itself will still be useful.

--
assignee: michael.foord -> ethan.furman
keywords: +easy -patch
nosy: +ethan.furman
stage:  -> patch review
versions: +Python 3.11 -Python 3.6

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

[issue47133] enhance unittest to show test name and docstring on one line

[Ethan Furman]

Ethan Furman  added the comment:

I proposed a discussion to python-dev to increase the odds that folks with an 
interest could chime in.  Not everyone follows the new-bugs list.

I find having the output on two lines counter-intuitive -- I was expecting one 
line per test, and indeed my experience seemed to support that (out of hundreds 
of tests showing on one line, it's easy to miss that the rare verbose error is 
on two).  And I'm not the only one, since another developer also thought there 
was a problem and spent most of issue46126 "fixing" it.

Another reason for posting to python-dev is that issue 46126 had been active 
for three months and had a PR merged before another dev mentioned that verbose 
tests with docstrings just printed on two lines instead of one.

Thank you for pointing out the possible disruption caused by unittest output 
changes.

--

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

[issue4833] Explicit directories for zipfiles

[Ethan Furman]

Change by Ethan Furman :


--
nosy: +ethan.furman
versions: +Python 3.11 -Python 3.4

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

[issue46337] urllib.parse: Allow more flexibility in schemes and URL resolution behavior

[Ethan Furman]

Change by Ethan Furman :


--
nosy: +ethan.furman

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

[issue46337] urllib.parse: Allow more flexibility in schemes and URL resolution behavior

[Ethan Furman]

Ethan Furman  added the comment:

Éric Araujo wrote on PR30520:

> No, we should not redefine the behavior of urlparse.
> 
> I was always talking about adding another function. Yes it can be a one-liner,
> but my point is that I don’t see the usefulness of having the separate flags 
> to
> pick and choose parts of standard parsing.

I suspect the usefulness comes from error checking -- if a scheme doesn't 
support parameters, then having what looks like parameters converted would not 
be helpful.

Further, while a new function is definitely safer, how many parse options do we 
need?  Anyone else remember `os.popen()`, `os.popen2`, `os.popen3`, and, 
finally, `os.popen4()`?

Assuming we just enhance the existing function, would it be more palatable if 
there was a `SchemeFlag.ALL`, so universal parsing was just 
`urlparse(uri_string, flags=SchemeFlag.ALL)`?  To be really user-friendly, we 
could have:

class SchemeFlag(Flag):
RELATIVE = auto()
NETLOC = auto()
PARAMS = auto()
UNIVERSAL = RELATIVE | NETLOC | PARAMS
#
def __repr__(self):
return f"{self.module}.{self._name_}"
__str__ = __repr__
RELATIVE, NETLOC, PARAMS, UNIVERSAL = SchemeFlag

Then the above call becomes:

urlparse(uri_string, flags=UNIVERSAL)

--

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

[issue46337] urllib.parse: Allow more flexibility in schemes and URL resolution behavior

[Ethan Furman]

Ethan Furman  added the comment:

Sounds good.

--

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

[issue47200] Add ZipInfo.mode property

[Ethan Furman]

Change by Ethan Furman :


--
nosy: +ethan.furman, twouters

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

[issue4833] Explicit directories for zipfiles

[Ethan Furman]

Change by Ethan Furman :


--
nosy: +alanmcintyre, twouters

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

[issue47200] Add ZipInfo.mode property

[Ethan Furman]

Change by Ethan Furman :


--
nosy: +alanmcintyre, serhiy.storchaka

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

[issue47224] The variable __module__ in the class body getting an undesirable value from __prepare__ of the metaclass

[Ethan Furman]

Ethan Furman  added the comment:

Stop creating new issues for the same problem.

If you didn't specify the first issue well enough, add your specifics to it and 
continue that conversation.  Splitting the thoughts and feedback across 
multiple issues is not efficient.

Closing this issue, reopening the original (issue47136).

--
nosy: +ethan.furman
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed

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

[issue47136] Wrong value assigned automatically to the variable __module__ in the class body.

[Ethan Furman]

Ethan Furman  added the comment:

issue47223 and issue47224 closed, reopening this one.

--
nosy: +ethan.furman
resolution: duplicate -> 
stage: resolved -> 
status: closed -> open

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

[issue47136] Wrong value assigned automatically to the variable __module__ in the class body.

[Ethan Furman]

Ethan Furman  added the comment:

Takuo, please give us an example from real code so we can see the problem.

--

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

[issue47136] The variable __module__ in the class body getting an undesirable value from __prepare__ of the metaclass

[Ethan Furman]

Ethan Furman  added the comment:

You are using the same generic example -- it does show the issue you are 
concerned with, but offers no rational for why we should "fix" it -- in other 
words, we cannot tell if it's actually broken.

Please provide an example of code you are actually using -- a trimmed down 
metaclass is fine, but it should show the kinds of names you are changing to, 
why you want to change the names, etc.

Maybe this is a just a documentation issue, or maybe it's an overlooked case 
that should be supported in Python -- we cannot tell based solely on your 
generic example.

--

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

[issue47231] TarFile.getmember cannot work on tar sourced directory over 100 characters

[Ethan Furman]

Ethan Furman  added the comment:

Nosied others from issue21987.

--
nosy: +andrei.avk, ethan.furman, r.david.murray, vstinner

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

[issue4833] Explicit directories for zipfiles

[Ethan Furman]

Ethan Furman  added the comment:


New changeset 050a8f94c678a05d506fe192c863c4a572178c42 by Sam Ezeh in branch 
'main':
bpo-4833: Add ZipFile.mkdir (GH-32160)
https://github.com/python/cpython/commit/050a8f94c678a05d506fe192c863c4a572178c42


--

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

[issue37830] continue in finally with return in try results with segfault

[Ethan Furman]

Ethan Furman  added the comment:

My apologies if I missed something, but do we have a consensus on the desired 
solution?

My understanding of `try/finally` is that whatever happens in the `finally` 
clause should:

- always happen
- win any conflicts with `try` clause

For example:

  try:
 a = 2
  finally:
 a = 3
  print(a)
  # 3

and

  def f():
 try:
return 5
 finally:
return 7
  print(f())
  # 7

So it seems like the ideal solution to:

  def mult(thing):
  print(thing*2)
  return thing * 2

  def simple():
  for number in range(2):
  try:
  return mult(number)
  finally:
  continue
  print(simple())

would be:

  0
  2
  None

--
nosy: +ethan.furman

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