Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
85 changes: 0 additions & 85 deletions auth/cloud-client-temp/noxfile.py

This file was deleted.

8 changes: 0 additions & 8 deletions auth/cloud-client-temp/requirements.txt

This file was deleted.

76 changes: 0 additions & 76 deletions auth/cloud-client-temp/snippets_test.py

This file was deleted.

1 change: 0 additions & 1 deletion auth/cloud-client/requirements-test.txt

This file was deleted.

10 changes: 8 additions & 2 deletions auth/cloud-client/requirements.txt
Original file line number Diff line number Diff line change
@@ -1,2 +1,8 @@
google-cloud-storage==2.9.0; python_version < '3.7'
google-cloud-storage==2.9.0; python_version > '3.6'
google-cloud-compute==1.42.0
google-cloud-storage==3.8.0
google-auth==2.47.0
pytest===8.4.2; python_version == '3.9'
pytest==9.0.2; python_version > '3.9'
Comment on lines +4 to +5
Copy link
Contributor

Choose a reason for hiding this comment

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

high

There are a few issues with how pytest is specified here:

  1. Test dependencies in production requirements: pytest is a testing dependency and should not be included in the main requirements.txt file. This will cause it to be installed in production environments where it's not needed. It's standard practice to keep test dependencies in a separate file, like requirements-test.txt or dev-requirements.txt.

  2. Incomplete Python version coverage: The pytest dependency is only specified for Python 3.9 and greater. The project's previous test configuration (noxfile.py) supported Python 3.7 and 3.8. If these versions are still supported, tests will fail because pytest won't be installed. Please ensure test dependencies are available for all supported Python versions.

  3. Version specifier: For version pinning in requirements.txt, the === operator is preferred to prevent automated updates from overwriting specific version numbers required for certain Python runtimes.

I recommend removing these lines from this file and adding the corrected pytest dependency to a dedicated test requirements file, ensuring === is used for version pinning.

References
  1. Use the === operator in requirements.txt for version pinning to prevent automated updates from overwriting specific version numbers required for certain Python runtimes.

boto3>=1.26.0
requests==2.32.5
python-dotenv==1.2.1
156 changes: 0 additions & 156 deletions auth/cloud-client/snippets.py

This file was deleted.

Loading
Loading