Skip to content

Conversation

@VeckoTheGecko
Copy link
Contributor

@VeckoTheGecko VeckoTheGecko commented Nov 4, 2025

Now that Parcels is in the src folder, and now that we promote the use of Pixi (or pip install -e .) to do source installation of Parcels - I don't think we need git calls to determine the version number.

This does mean that the version number does not have the git sha in it when using dev versions

e.g.,

>>> parcels.__version__
'3.1.3.dev1212'

The git sha only found its way into the version number (e.g, 'v3.1.2-1357-g0307c777') in some cases though - when importing Parcels but not installing it using pip. Hence I don't think this is really a regression.

I used xarray's version finding mechanism - note the "9999" version number is to do with pydata/xarray#8200 , which doesn't really apply to us but I thought why not have that as a fallback

@VeckoTheGecko VeckoTheGecko added v4 meta Issues to do with organisation, dev setups, branding, or things non-code related related. labels Nov 4, 2025
@github-project-automation github-project-automation bot moved this to Backlog in Parcels v4 Nov 4, 2025
@VeckoTheGecko VeckoTheGecko removed the meta Issues to do with organisation, dev setups, branding, or things non-code related related. label Nov 4, 2025
@VeckoTheGecko VeckoTheGecko merged commit 28e86bd into Parcels-code:v4-dev Nov 4, 2025
10 of 11 checks passed
@github-project-automation github-project-automation bot moved this from Backlog to Done in Parcels development Nov 4, 2025
@github-project-automation github-project-automation bot moved this from Backlog to Done in Parcels v4 Nov 4, 2025
@VeckoTheGecko VeckoTheGecko deleted the versioning branch November 4, 2025 15:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: Done
Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants