-
Notifications
You must be signed in to change notification settings - Fork 12
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
Switch to poetry #143
Switch to poetry #143
Conversation
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.
See relevant comments I made on opendatateam/udata#2757.
We need to specify instructions on the good practice to have a shared dev env.
I personally manually activated the env (located in ~/.cache/pypoetry/virtualenvs/) in udata-front.
We could also create an env in-project in udata and use it as well in udata-front.
In any case we need to document it I think.
I had some issues when first installing (see my comment), but then it seemed to work smoothly, with both udata and udata-front being in development mode with hot reload working.
Trying to get an advice on our issue: python-poetry/poetry#6706 |
Fix datagouv/data.gouv.fr#892