Skip to content

Restore compatibility with iptools.IpRangeList #1929

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 1 commit into from
Jun 1, 2024

Conversation

quinox
Copy link
Contributor

@quinox quinox commented May 30, 2024

Description

As per the discussion in #1928.

Fixes #1928

Checklist:

  • I have added the relevant tests for this change.
  • I have added an item to the Pending section of docs/changes.rst.

Copy link
Member

@matthiask matthiask left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that's a good approach. Checking __contains__ before resolving the IP should also alleviate the problem of slowness there for most uses.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

I can no longer use iptools.IpRangeList for INTERNAL_IPS
3 participants