Skip to content

Conversation

@VeckoTheGecko
Copy link
Contributor

I thought that this would also be good to have ahead of the hackathon.

@erikvansebille
Copy link
Member

So this warning is raised on every import of Parcels? Is that not overkill? I assume most users run parcels through anaconda, and that the ones who run it through GitHub closing will know that they are on v4. I can imagine it becomes annoying (also for us!) to keep seeing this message

@VeckoTheGecko
Copy link
Contributor Author

VeckoTheGecko commented Sep 12, 2025

So this warning is raised on every import of Parcels?

If they import Parcels (or a module from Parcels) it will be run once for the session.

I was worried that people who were installing Parcels via conda at the event might forget that they're using the alpha version of Parcels. Though if they do conda env export they will see the version listed there - and I guess since we're promoting installing in a separate environment with a clear name it really isn't that necessary. I don't mind either way. Should I close?

@erikvansebille
Copy link
Member

OK I see. Let's then merge and if it becomes too annoying we can always remove it again

@VeckoTheGecko VeckoTheGecko merged commit 8c4aaed into Parcels-code:v4-dev Sep 12, 2025
9 checks passed
@github-project-automation github-project-automation bot moved this from Backlog to Done in Parcels development Sep 12, 2025
@VeckoTheGecko VeckoTheGecko deleted the import-warn branch September 12, 2025 15:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants