-
Notifications
You must be signed in to change notification settings - Fork 6
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
Adding poetry and Django test structure #5
Adding poetry and Django test structure #5
Conversation
That's pretty cool. I'm not really familar with |
Yeah! Poetry is a dependency manager, and the lock file just guarantees each person setting up the code gets exactly the same dependency list on the same version on python. It's not strictly necessary but it can save some headaches for sure. |
Yup! I get that, but, I see there are a few dependencies already defined in the file, besides Django. |
689f2c1
to
99f9f9c
Compare
Sorry, I misunderstood. Yes. Absolutely we don't need Pytest. I removed it now. The lock should just be sub-dependencies of Django |
hey @rjauquet can you help me out with something ? |
Yes, the poetry setup should create the virtualenv. I just tried this locally and was able to get it working. I'm wondering if poetry was installed with an incompatible version of python. Could you try sourcing into the virtualenv directly and then running ./manage.py test?
I think is your path. How did you install poetry? |
@rjauquet , no worries , I managed to resolve it , seems when you use sudo , it instantiates the virtualenv in a different location than it normally does . |
Added some ideas for test infrastructure. Open to other suggestions!
After installing poetry:
The test isn't really checking anything important but I wanted to make sure all the importing logic and calling worked.