➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2016-07-26 17:34 by lukasz.langa, last changed 2022-04-11 14:58 by admin.
| Messages (3) | |||
|---|---|---|---|
| msg271399 - (view) | Author: Łukasz Langa (lukasz.langa) *  |
Date: 2016-07-26 17:34 | |
ipaddr historically let users compare if one network is within another network: https://github.com/google/ipaddr-py/blob/master/ipaddr.py#L643 ipaddress specifically prohibits this comparison: https://hg.python.org/cpython/file/tip/Lib/ipaddress.py#l675 What is the reason behind this change? I propose we restore this functionality for 3.6. It's a behavior change but arguably backwards compatible in the sense that between 3.3 and 3.5 this __contains__ comparison always returns False. It's also more on par with what ipaddr did in the past. Thoughts? |
|||
| msg271401 - (view) | Author: Serhiy Storchaka (serhiy.storchaka) * |
Date: 2016-07-26 17:55 | |
This issue looks as a duplicate of issue20825. I think that if consider a network as a set of addresses, the operation "address in network" has the same meaning as for sets, but the operation "network in network" doesn't make a sense. Instead you should use the same operation as for testing a subset of a set: "network <= network". But this operation is ambiguous, because "<=" usually is ordering operation. |
|||
| msg271408 - (view) | Author: Berker Peksag (berker.peksag) * |
Date: 2016-07-26 19:00 | |
See also issue 25431. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:58:34 | admin | set | github: 71815 |
| 2016-07-26 19:00:54 | berker.peksag | set | messages: + msg271408 |
| 2016-07-26 17:55:39 | serhiy.storchaka | set | nosy:
+ serhiy.storchaka messages: + msg271401 |
| 2016-07-26 17:42:56 | pmoody | set | assignee: pmoody -> |
| 2016-07-26 17:34:35 | lukasz.langa | create | |