Skip to content

Conversation

@cesarcoatl
Copy link
Member

No description provided.

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey @thecesrom - I've reviewed your changes and they look great!

General suggestions:

  • Consider verifying the broader impact of enforcing Python 2.7, especially if other parts of the project or its dependencies have moved to Python 3.
  • Review the necessity of sticking with Python 2.7 given its end-of-life status; if possible, plan for an upgrade to Python 3.
Here's what I looked at during the review
  • 🟢 General issues: all looks good
  • 🟢 Security: all looks good
  • 🟢 Testing: all looks good
  • 🟢 Complexity: all looks good
  • 🟢 Docstrings: all looks good

Thanks for using Sourcery. We offer it for free for open source projects and would be very grateful if you could help us grow. If you like it, would you consider sharing Sourcery on your favourite social media? ✨

Share Sourcery

Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.

@cesarcoatl cesarcoatl merged commit 08ac66f into main Mar 14, 2024
@cesarcoatl cesarcoatl deleted the ci/pip-compile-upgrade/python2.7 branch March 14, 2024 20:44
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.

2 participants