-
Notifications
You must be signed in to change notification settings - Fork 40
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
Configure package in pyproject.toml
#1068
Comments
So I'm already working on this. Just going to keep writing my notes on these public issues/discussions rather than have them in, say, a personal notebook. (I don't know if this will be annoying and I should just create personal discussions on the main discussions tab and reference them in the issues, still debating myself) One thing that is interesting about the current Worth mentioning I also have had a look at the
Currently I'm thinking about the versioning thing. Also I'm wondering about this:
I'm curious, what is the particular reason for them? Writing this down here for reproducibility from a new venv to the working poetry install, maybe I'll add it in a script later:
Status in https://github.com/daquintero/tidy3d/tree/docs_improvement_suggestions |
Yea, the
I think perhaps another alternative (maybe simpler) is to just do the directory creation in
Interesting, I'd never heard of it. Thanks for looking into that.
Thanks!
Version tracking between frontand and backend? or what do you mean here? Note that we have some sort of version tracking in the form of a mapping from solver version to front end version, which is maintained in the backend. I think this stuff we can probably start looking into with the solver team, but the front end packaging is probably higher priority at least right now.
Yea a few years ago, we had a basic version of tidy3d on PYPI called |
Sounds good! I think the
Sorry I meant I've got a working Worth mentioning details re poetry extras |
Bugs I've found working with poetry:
Relevant bugs are discussed here, this Github issue. Actions to fix:
Note I've had to update |
Think we can close this? |
Replace all requirements / setup.py
The text was updated successfully, but these errors were encountered: