Skip to content

Maintenance updates#76

Merged
QSparks merged 19 commits into
masterfrom
py-sprint-25q1
Nov 5, 2025
Merged

Maintenance updates#76
QSparks merged 19 commits into
masterfrom
py-sprint-25q1

Conversation

@QSparks
Copy link
Copy Markdown
Contributor

@QSparks QSparks commented Jun 13, 2025

  • PEP 621-conformant pyproject.toml
  • Poetry >2.0
  • Drop old setup files
  • Separate Black CI workflow
  • Keep all dependencies, including R deps in the pyproject.toml
  • Bump CI workflows
  • Use marble-dev01, & beehive URLs
  • Replace pkg_resources with importlib.resources

Pending:

  • Use tagged wps-tools version once merged
  • Use tagged p2a-rule-engine version once merged
  • Use tagged climate-explorer-backend
  • Use tagged modelmeta
  • Use Tagged geospatial-python

@QSparks QSparks self-assigned this Jun 13, 2025
@review-notebook-app
Copy link
Copy Markdown

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

@QSparks QSparks marked this pull request as ready for review June 20, 2025 17:51
Copy link
Copy Markdown
Collaborator

@rod-glover rod-glover left a comment

Choose a reason for hiding this comment

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

LGTM, with the caveat that the hardcoded server addresses might better be parametrized and provided externally.

strategy:
matrix:
python-version: [3.7, 3.8]
python-version: ["3.11", "3.12"]
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

In another bird, the matrix was just 3.11. What's the criterion for Python versions to test with in these repos?

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

3.12 may be required in this particular repository to support running on the newest geospatial-python docker, which supports only python 3.12 right now.

"output_type": "stream",
"text": [
"Using sandpiper on https://docker-dev03.pcic.uvic.ca/twitcher/ows/proxy/sandpiper/wps\n"
"Using sandpiper on https://marble-dev01.pcic.uvic.ca/twitcher/ows/proxy/sandpiper/wps\n"
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

There are a lot of hardcoded server specs in this bird. I wonder if they can be factored out into ENV vars or the like, so that they are shared and easily updated.

"\u001b[0;31mFile:\u001b[0m ~/code/birds/sandpiper/</tmp/sandpiper-venv/lib/python3.8/site-packages/birdy/client/base.py-2>\n",
"\u001b[0;31mType:\u001b[0m method\n"
"\u001b[31mFile:\u001b[39m ~/python-sprint/py-repos/sandpiper/</home/quintins/.cache/pypoetry/virtualenvs/sandpiper-Bm4285Lb-py3.12/lib/python3.12/site-packages/birdy/client/base.py-2>\n",
"\u001b[31mType:\u001b[39m method"
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

This looks a bit fragile to me. Is there a better place to store this cache?

Copy link
Copy Markdown

@Nospamas Nospamas left a comment

Choose a reason for hiding this comment

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

👍

@QSparks QSparks merged commit 029e5f7 into master Nov 5, 2025
4 checks passed
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.

4 participants