Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Remove "networkx.plugins" and "networkx.plugin_info" entry-points #7192

Merged
merged 1 commit into from Jan 2, 2024

Conversation

eriknw
Copy link
Contributor

@eriknw eriknw commented Dec 28, 2023

Use "networkx.backends" and "networkx.backend_info" instead. Version 3.2 supports both options. The next release can drop "plugin".

I forgot to do this in #7157, which made a similar change.

Use `"networkx.backends"` and `"networkx.backend_info"` instead.
Version 3.2 supported both options. The next release can drop "plugin".
Copy link
Member

@dschult dschult left a comment

Choose a reason for hiding this comment

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

Thanks for this @eriknw
How long did we want both options to work? Is one release cycle enough? (probably -- we don't have many backends that we know of at this point). In the long run we should try to follow the NX deprecation cycle I guess. But I think this is fine!?!

@eriknw
Copy link
Contributor Author

eriknw commented Dec 28, 2023

Yeah, I think we're allowed to move faster b/c we call this "experimental". Once it's no longer experimental (in 2024?), we should probably follow standard deprecation cycle. Also, it's already extra nice that 3.2 supports both.

@MridulS MridulS merged commit 3a98973 into networkx:main Jan 2, 2024
39 of 40 checks passed
@jarrodmillman jarrodmillman added this to the 3.3 milestone Jan 2, 2024
cvanelteren pushed a commit to cvanelteren/networkx that referenced this pull request Apr 22, 2024
…networkx#7192)

Use `"networkx.backends"` and `"networkx.backend_info"` instead.
Version 3.2 supported both options. The next release can drop "plugin".
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

None yet

4 participants