-
Notifications
You must be signed in to change notification settings - Fork 34
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
Improve test and release process #52
Conversation
Hi @guilhermef , |
It's mostly to be able to reuse the cached dependencies, and it makes it easier to pin dependencies. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If noone opposes, I'm good with this. Just don't do it in thumbor's main repo. Other than that, it should be fine.
IMHO, we can go without |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also give poetry
a strong 👎 We don't need it. And it's yet another dependency.
In fact, I think we should get rid of poetry
entirely, thumbor-wise I mean. Yesterday I was debugging libthumbor
and had to go over this loop:
- edit/save
poetry build
- ...wait...
pip install dist/libthumbor-x.y.z.tar.gz
- ...wait...
- experiment
- repeat
There's definitely no poetry in that, whatsoever. And, BTW, python-poetry/poetry#34 is a joke.
The other aspects of this PR are stellar.
Also, thumbor/libthumbor#52 (comment)... meh. |
@scorphus you don't need to install the library. |
Poetry does offer GIthub actions to cache the build environment, it helps to speed up the build process and it pins the version across builds. |
There's also this. A whole collection of new commands and ideas. A few more slots dislodged in my brain. I don't think I want that. I already know how to work with Python and its ecosystem.
There are other less intrusive ways to achieve both these — arguably desirable — things. |
Normally I would introduce a
I agree, but I couldn't find an easier one that I didn't have to maintain. |
@scorphus, my suggestion would be to keep poetry while we don't have a better solution for environment caching on builds, and I'll add more docs to avoid confusion on how to run the projects with poetry. |
@guilhermef, what could other options be in your view?
@heynemann, why you think we shouldn't do this in thumbor's main repo? |
@scorphus the other option would be copying exactly what's being done by poetry, but on our workflow. |
The only reason we can't do poetry in thumbor is that when I did it screwed the C integration for thumbor. So let's leave thumbor with setup.py as the way it handles C modules is quite particular. |
@marcelometal what are your thoughts? Apart from previous words... Also, do we package remotecv? What's your experience with debian packages that use poetry? |
Hi @scorphus , sorry for the late reply... Would be nice packaging remoteCV for Debian =) IMHO, we should avoid to include third-party libs, because it increase the complexity... Debian: poetry: 1.0.7 |
Ok, then I'll remove poetry and the environment cache. |
@scorphus @marcelometal I've removed Poetry dependency. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍 Thanks, @guilhermef
Please consider a couple suggestions below.
Co-authored-by: Pablo Aguiar <scorphus@gmail.com>
Co-authored-by: Pablo Aguiar <scorphus@gmail.com>
Code Climate has analyzed commit 59b4b15 and detected 0 issues on this pull request. View more on Code Climate. |
It's the same build environment used in libthumbor and thumbor-aws.
This PR will add: