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

[Backend] Removing future library dependancy as it is not required in… #3311

Closed
wants to merge 2 commits into from
Closed

[Backend] Removing future library dependancy as it is not required in… #3311

wants to merge 2 commits into from

Conversation

ranade1
Copy link
Contributor

@ranade1 ranade1 commented May 22, 2023

… Python 3.8 and later.

  • The future library imports have no effect on Python 3.

What changes were proposed in this pull request?

  • Removing future library dependancy

How was this patch tested?

  • Tested it by running Hue using python3.8 on MacBook and RHEL 8.4 system

Please review Hue Contributing Guide before opening a pull request.

@Harshg999
Copy link
Collaborator

We should not see the urllib.parse import error now in CI checks because that was specific to Py2.7 and this PR was a breaking change for it. So, I've removed the Py2 CI as going forward we have remove Py2 stuff anyway.

Ref: https://python-future.org/standard_library_imports.html#aliased-imports

@Harshg999
Copy link
Collaborator

Please fix the pylint issues and retrigger the CI checks.

ranade1 and others added 2 commits June 22, 2023 11:00
… Python 3.8 and later.

- The future library imports have no effect on Python 3.
@github-actions
Copy link

This PR is stale because it has been open 45 days with no activity and is not labeled "Prevent stale". Remove "stale" label or comment or this will be closed in 10 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
4 participants