Automate pypi release #135
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I'm not quite understanding the numpy import error here, @ricardoV94 , @lucianopaz , @twiecki maybe you've seen something like this before? It seems like there's no reason numpy would be required for building sdist |
|
You might be building it the wrong way, maybe a difference between using Have you tried to do it locally? |
|
@ricardoV94 , after the changes I've introduced now it runs locally without issues, but here still seems to be failing. I'll keep searching for some solution but for now it's going to be guessing game a bit |
|
I need some help on that, nothing that I try works :/ |
Closed
ricardoV94
changed the title
michaelraczycki
added a commit
to michaelraczycki/pymc-experimental
that referenced
this pull request
Apr 27, 2023
* adapted the release setup to mimic one used in pymc-marketing * fixed naming not matching in __init__ * fixing importing error for numpy * fixing command * adding numpy dependency to fix missing numpy error * fixing self import in setup.py * including versioneer, supressing pre-commit for versionner files * fixed build
michaelraczycki
added a commit
to michaelraczycki/pymc-experimental
that referenced
this pull request
Apr 27, 2023
* adapted the release setup to mimic one used in pymc-marketing * fixed naming not matching in __init__ * fixing importing error for numpy * fixing command * adding numpy dependency to fix missing numpy error * fixing self import in setup.py * including versioneer, supressing pre-commit for versionner files * fixed build Automate pypi release (pymc-devs#135) * adapted the release setup to mimic one used in pymc-marketing * fixed naming not matching in __init__ * fixing importing error for numpy * fixing command * adding numpy dependency to fix missing numpy error * fixing self import in setup.py * including versioneer, supressing pre-commit for versionner files * fixed build fixed test failing due to infinite precision requirement (pymc-devs#153)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As pointed out in #134 by @ricardoV94, pymc-experimental doesn't use the same versioning system as main pymc, so the solution taken from there wouldn't work. This PR contains changes that adopt the solution used in pymc-marketing