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

MNT #287 impose minimum Python version #306

Merged
merged 5 commits into from
Jun 13, 2024
Merged

Conversation

prjemian
Copy link
Contributor

@prjemian prjemian added the bug Something isn't working label Jun 10, 2024
@prjemian prjemian added this to the v1.0.3 milestone Jun 10, 2024
@prjemian prjemian requested review from MDecarabas and a team June 10, 2024 23:02
@prjemian prjemian self-assigned this Jun 10, 2024
@coveralls
Copy link

coveralls commented Jun 10, 2024

Pull Request Test Coverage Report for Build 9456762787

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.08%) to 82.759%

Totals Coverage Status
Change from base Build 8883479879: 0.08%
Covered Lines: 984
Relevant Lines: 1189

💛 - Coveralls

@prjemian
Copy link
Contributor Author

I will update the CHANGES.rst file for this PR, too.

Copy link
Collaborator

@MDecarabas MDecarabas left a comment

Choose a reason for hiding this comment

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

Overall looks good. Small comments. Also maybe a docstring will be useful for the file so that future contributors will know what this file is used for. As of right now this is unclear to me.

Comment on lines 144 to 145
import requests

Copy link
Collaborator

Choose a reason for hiding this comment

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

Is there any reason why this import is not global?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It is not global so the application does not crash under Python <3.9 with this exception. Instead, the more meaningful message is printed to use Python 3.9 or higher.

Could have put a try..except at the global level...

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'll rewrite it to the global part.

Copy link
Collaborator

Choose a reason for hiding this comment

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

New commit looks good. If you believe this to be a legitimate worry we will encounter during deployment we can implement this solution so that we have better control over the environment. Especially since the repository comes with an env file.

https://stackoverflow.com/questions/74857446/how-to-specify-python-version-range-in-environment-yml-file

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Not sure we need to put a maximum version. Minimum version for the bluesky environment is specified:

This is different than minimum version to run this installer. We'll want this soon since the current installer:

  • fails for Python 3.6 and 3.7
  • does not install the latest environment file

Comment on lines 218 to 219
import requests

Copy link
Collaborator

Choose a reason for hiding this comment

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

Same as above

@coveralls
Copy link

coveralls commented Jun 12, 2024

Pull Request Test Coverage Report for Build 9489045808

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 82.675%

Totals Coverage Status
Change from base Build 8883479879: 0.0%
Covered Lines: 983
Relevant Lines: 1189

💛 - Coveralls

@coveralls
Copy link

coveralls commented Jun 12, 2024

Pull Request Test Coverage Report for Build 9490715430

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 82.675%

Totals Coverage Status
Change from base Build 8883479879: 0.0%
Covered Lines: 983
Relevant Lines: 1189

💛 - Coveralls

@coveralls
Copy link

coveralls commented Jun 12, 2024

Pull Request Test Coverage Report for Build 9490764218

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 82.675%

Totals Coverage Status
Change from base Build 8883479879: 0.0%
Covered Lines: 983
Relevant Lines: 1189

💛 - Coveralls

@MDecarabas MDecarabas self-requested a review June 13, 2024 16:20
Copy link
Collaborator

@MDecarabas MDecarabas left a comment

Choose a reason for hiding this comment

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

Looks good!

@prjemian prjemian merged commit f70d2db into main Jun 13, 2024
6 checks passed
@prjemian prjemian deleted the 287-min-Python-version branch June 14, 2024 23:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

update minimum Python version for new_bluesky_instrument
3 participants