-
Notifications
You must be signed in to change notification settings - Fork 3
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
Releasing brim on pypi #37
Comments
The above issue has been solved by giving installation instructions in the README and temporary removing those from the
|
Some names are taken on pypi but that isn't apparent from a search. For example, cyipopt was taken but didn't show up in a search. I then had to put in a request for the name and they eventually gave it to me because it was found it was never used and someone was just parking on it. |
It seems you are depending on dev versions of software. For pip installs to work I think you really need to depend on released versions of dependencies. If we need to make a BicycleParameters release, etc. then I can help with that. The whole pypi and conda systems rely on released versions with specific version numbers, otherwise things can be resolved with dependency resolvers in the installation tools. |
the problem is that it is depedent on |
I've opened a request |
I think it took quite some months when I made the cyipopt request, fyi. |
Quite annoying that these things didn't get into 1.12. We should have tagged these prs as needing to go into 1.12. Maybe we should try to do a new release for sympy soon. |
they are experimental and so is |
Then it's probably best not to release to pypi yet. |
When trying to publish brim on pypi I ran into the following issue:
The text was updated successfully, but these errors were encountered: