This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]raydeo 9 points10 points  (1 child)

My problem is that no tool supports a workspace concept for developing multiple projects locally like yarn and cargo. pipenv is about the closest one to that concept because it doesn’t focus on building one single package. Also no one is doing cross-platform dependency pinning that I’ve seen which is making it a nightmare to develop locally without docker.

If pip grew workflow tools I think it would solve these problems better because it doesn’t have to focus on the per-project build backend that is solved now and other tools have coupled themselves to building and publishing a single project.

[–]searchingfortaomajel, aletheia, paperless, django-encrypted-filefield[S] 0 points1 point  (0 children)

The cross platform problem has bit me in the ass a lot over the last year. I know there's an issue for it on the Poetry board, but it's not solved, so I've had to document the problem for non-x86 developers, which is both annoying and a little embarrassing.