why I will never use python-poetry

preview_player
Показать описание
innovative strides in deprecation policies!

==========

I won't ask for subscriptions / likes / comments in videos but it really helps the channel. If you have any suggestions or things you'd like to see please comment below!
Рекомендации по теме
Комментарии
Автор

I think this naturally calls for a video on piptools now

chrisharrel
Автор

As someone who continually has to deal with issues that only happen intermittently and seemingly with the same inputs having different behavior, this would 100% annoy the heck out of me. I can't believe that a fellow developer would think that this is an acceptable behavior to add, ESPECIALLY in a CI environment.

DavidDellsperger
Автор

That random in CI stuff is... something. Shows that the people behind this project haven't got a good understanding of how people build stuff in the wild, which is indeed disconcerting

OrCarmi
Автор

BROWNOUT_CHANCE = 5
GET_RID_OF_POETRY_CHANCE = 95

xFrez
Автор

A 5% chance to randomly fail in CI is ridiculous, as is the overnight deprecation and removal. I was looking into using poetry but your thoughts have definitely made me reconsider.

Kralnor
Автор

As someone who's dabbled in Poetry and really liked it, I found your video so informative that it got you my subscription. I'm really looking forward to watching some of your other videos!

jamesmunroe
Автор

I had not heard of pip-tools but a brief look at it makes me think it could solve some problems I've had with dependency management. Thanks for introducing me to it!

AceofSpades
Автор

Great video Anthony, thanks! It would be nice to watch a video about pip-tools

tandavme
Автор

I'm still a big fan of Poetry and will keep using it; However, your arguments here are very good, and I actually agree with them - it's bad to automatically update deps within major versions by default (because it's quite common to reach breaking changes between different minor versions), and it's SUPER BAD to introduce random breakages in CI builds just to "force" people to stop using some deprecated feature.

Thanks for the video, you got a new subscriber 🙂

DiogoBaeder
Автор

Interesting way to tell users that it’s time to fork or find something else

buck
Автор

I typically watch videos at 2x speed, but this time I'm watching at 0.5x speed.

JorgeAnais
Автор

Adding randomness is pure evil. Must have caused so much head-scratching and aggravation to people who were on this version.

Edit: thanks about the pip-tools suggestion :)

Quarky_
Автор

wow, best breakdown I've seen thus far on actual technical reasons as to why not to use poetry. Great job! Loving your vids

justinfuruness
Автор

Wow, ty for sharing this! Not that long ago we've just dealt with flask lib, that had something similar where they simply changed the default behavior, although wasn't even intended to be removed at the end. I went crazy about it. You should do another video about how flask.request.json changed from version ~1.X -> 2.2.X it's default behav.

hunorportik
Автор

Sorry this is off topic, it's my first time seeing a video of yours. I just gotta know, what keyboard is that?

joemckoy
Автор

I thought the video was clickbait and you were actually going to like it in the end but wow ok. I just started looking at poetry this morning because setuptools which i build pypi wheels in is so hard to manage. So what is the best practice to make pypi projects?

petermoore
Автор

Thanks for doing this one, now I can send others asking about poetry to your video. Much easier than having endless debates about why some feel the need for Vogon poetry. There are also other reasons, but if I remember well they would fit in the same category as your example regarding making deliberate decisions that disconsider the user-base. That kind of aggressiveness around deprecations I unacceptable, at least in my view. I was even upset about how aggressive was pip around reporting that is outdated, but what poetry did took it a new level.

ssbarnea
Автор

The greatest value for me in poetry is how it helps manage and hence democratize the use of pyproject.toml. This really helped set our team on a journey to sane packaging and dependency management.

The randomness in CI is wild though and we've definitely ran into weird stuff with poetry also the change in how hashes are handled before 1.2 compared to after which also broke our CI.

BeatX
Автор

Ekk. I did use setup-py-upgrade as part of converting 10's of poetry pyproject.toml's to setup.cfg's so thanks for making that.

sillybuttons
Автор

It's a very WTF decision. I moved away from poetry as well. now I need to convince work to do the same, but it'll be... hard given we migrated into poetry not that long ago...

mrswats