anyone's using pipenv yet? I'm thinking about migrating Picard to it rather than using requirements*.txt. But it seems none of our projects is using it yet, just wondering why (or why not).
zas: no strong opinion on this, but never used pipenv so far
but I want to preserve the ability to pin different versions of dependencies for different platforms for our builds, is this possible?
ruaok
looks really nice, I dont see why we shouldn't migrate to it.
jwf
zas: I'm a big fan of Pipenv. I think it reduces the complexity of virtualenvs for people are more focused on programming than Python packaging and managing dependencies across multiple projects
The PSF is also loosely behind Pipenv too, so it has a modicum of upstream support from Python devs too
The guy who write python-requests and I think Flask is the original author of Pipenv
D4RK-PH0ENiX joined the channel
zas
outsidecontext: ofc it is possible, and pipenv is much better at "pinning" versions imho
ruaok: iliekcomputers: is POST request to `/user/<user_name>/love` a good option to mark a recording as loved. The endpoint looks a little wierd to me
ruaok
seems fine for now. its not written in stone yet, so we can change it if we want to.
shivam-kapila
I wiill use this in my proposal's first draft. Thanks ruaok.
outsidecontext
zas: interesting read. most of the criticism would not really affect us I guess. but actually I think one of the biggest benefits of virtualenv is locking dependency hierarchies, but that's one point we so far avoided in picard entirely (all the dependencies have themselves zero dependencies on other pypi packages)
zas: I switched to pipenv for a few projects. It's kind of complex to use with docker. I like the split of the pipfile/lock file, but for everything else I have a pretty good virtualenv system set up that works for me
and agreed, I've seen some of these blog posts about how it has problems, but I've not used it enough to run into huge difficulties yet
Cyna
Hey Mr_Monkey, can you help me explore this project `Design and implement a unified creation form` ?
I find this one of the best project that suits me
Are you looking up to replace the current edit forms to improve UX for beginners ?S
MBS-7894: When you create a new release based on an existing release, the new release contains no tracks
Mr_Monkey
Cyna: That's it. The idea is to have both the option of entering a single entity as we currently do, but also have a wizard-like creation form where you can search for or create in one go all the entities you need to describe "a book".
It should help reduce the amount of repeating of information we currently do (e.g. name of Work = name of Edition = name of Edition Group, with relationships automatically created) while allowing more complex cases (e.g. multiple Works by different Authors in an Edition with its own name credited on the cover to one of the Authors)
It'll require thinking about UX and making advanced mockups for starters
