Skip to content

Remove dangling use of python-future from rrdd.py #6247

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

Merged
merged 1 commit into from
Jan 23, 2025

Conversation

MarkSymsCtx
Copy link
Contributor

No description provided.

Signed-off-by: Mark Syms <mark.syms@cloud.com>
Copy link
Member

@robhoes robhoes left a comment

Choose a reason for hiding this comment

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

The future is now.

Copy link
Collaborator

@bernhardkaindl bernhardkaindl left a comment

Choose a reason for hiding this comment

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

👍

Copy link
Contributor

@edwintorok edwintorok 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 these were used during the Py2->3 upgrade, and a noop now.

@@ -46,11 +46,6 @@

from __future__ import print_function

from future import standard_library
standard_library.install_aliases()
Copy link
Collaborator

Choose a reason for hiding this comment

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

If you drop this, you need httplib and xmlrpclib for Py2.7 compatibility.

Those are the only ones, so I'd suggest this form:

try:
    import http.client
except ImportError:
    import httplib

Copy link
Collaborator

Choose a reason for hiding this comment

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

we have dropped python2.7 support on xapi master.
Yangtze support is on another release branch.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This isn't packaged for Python 2 anymore

@MarkSymsCtx
Copy link
Contributor Author

I think these were used during the Py2->3 upgrade, and a noop now.

Except for requiring python3-future as an RPM requires.

@robhoes robhoes added this pull request to the merge queue Jan 23, 2025
Merged via the queue into xapi-project:master with commit 0e99836 Jan 23, 2025
15 checks passed
@MarkSymsCtx MarkSymsCtx deleted the remove_future branch May 20, 2025 16:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants