Poetry VS virtualenv

Since this is a coding challenge, I will be using Poetry to help me create the structure of the project, and to facilitate anyone running it. You can check how to install and use Poetry on their website.

For managing dependencies in this project, I used Poetry. Poetry simplifies the package management process and automates much of the heavy lifting involved with dependencies. It relies on the pyproject.toml file, which is now the standard for defining build requirements in modern Python projects.

# Palindrome project Project used to explain my view on a django project architecture ## Tools, libs, etc. Some time related files. Versions on Poetry. - [Python](https://www.python.org/) Programming languange - [django-environ](https://django-environ.readthedocs.io) Manage .envs in Django - [Poetry](https://python-poetry.org/) Python packaging and dependency management - poetry.lock - pyproject.toml - [Django](https://www.djangoproject.com/) Web framework written in Python - [Docker](https://www.docker.com/) Manage containers for dev environment - compose.yaml - compose/dev/Dockerfile - compose/dev/start - .env - [Just](https://just.systems/) encapsulate commands for easier use - justfile ## Dev environment setup 1. Install Just, Docker and Poetry(opcional). 2. Copy .env.example to .env, no need for edtion. 3. Certified that docker is up and running 4. `$ just build` ## Run the server for development 1. Certified that docker is up and running 2. `$ just runserver` You can access on http://0.0.0.0:8000/

Tools like Poetry aim to fix this problem, but vanilla pip can do just fine.

Our first step is to create our development environment, and install all required dependencies for this project. The good thing is that for this example we only need to install flama to have all the necessary tools to implement JWT authentication. We'll be using poetry to manage our dependencies, but you can also use pip if you prefer:

I use Python Poetry as the package management tool, so for this example I asume you have it already. First thing to do is install the dependencies with poetry install. You could also use pip to install them with: pip install pymongo loguru.

# Official Python runtime as a parent image FROM python:3.10 RUN set -xe # Install Poetry RUN curl -sSL https://install.python-poetry.org | python3 - --git https://github.com/python-poetry/poetry.git@master ENV PATH="/root/.local/bin:$PATH" # Confirm poetry version RUN poetry --version # Set up the working directory WORKDIR /app # Copy and install dependencies COPY . /app RUN poetry install EXPOSE 8000 # Start the application CMD ["bash", "-c", "poetry run bash ./prestart.sh && poetry run uvicorn app.main:app --reload --host 0.0.0.0"]

python and/or poetry

For more information visit: virtualenv documentation.

Python's venv module is officially recommended for creating virtual environments since Python 3.5 comes packaged with your Python installation. While there still are additional older tools available, such as conda and virtualenv, if you are new to virtual environments, it is best to use venv now.

Despite these attractive attributes, many developers I've come across don't prefer Fish shell, primarily due to integration gaps with tools like Python's virtualenv. So, in this article, I'm offering a simple solution for automatic virtualenv activation for Fish shell, steering clear of resource-intensive frameworks like oh-my-fish that often slow down the shell.

`virtualenv` still exists and is still actively developed. It's true that Python 3 ships with `venv` but I think `virtualenv` offers some additional features.

https://github.com/pypa/virtualenv

virtualenv is a tool that creates an isolated Python environment for each of your projects.

Python is the chosen language for this tutorial and as you can guess some precautions should be done to make sure that the environment is setup correctly and the main OS I'll use is Ubuntu(a Linux distro) virtual environment is a tool that helps you to isolate your code from the rest of the system. It is a good idea to create a virtual environment for your project.

$ curl -O https://github.com/pypa/virtualenv/raw/master/virtualenv.py$ python virtualenv.py my_new_env$ . my_new_env/bin/activate(my_new_env)$ pip install ... Or something entirely different?

I've been using Fish for years and spend my entire day working with Python. Python's virtualenv has an `activate.fish` command, I've never had any problems with it. Additionally, we have a ton of internal tooling built in a fabfile, so I've written a couple of snippets of fish that automatically activate that .venv (Poetry managed) whenever I cd into a directory that has one, and also expands a bunch of env vars into the shell session. I've also got this feature request in on the virtualenv repo in the hope that one day we can have activate.fish emit an event - https://github.com/pypa/virtualenv/issues/1456

We of cause, like all good developers do, put the error message online and look for clues, we quickly found a GitHub issue and boi, we are not the only souls that got crushed by a "timely" release of virtualenv just a few hours before us. Since the lastest version of virtualenv got installed every time we create the CI build job on Travis, it fails even we have done nothing. Of cause we didn't point fingers at other maintainers, they are just as hardworking as us and it's human to make mistakes. We are faced with 2 options, roll back to the previous release or wait for the patch of virtualenv to get released. As the devs of virtualenv did a lighting fast patch, we have chosen option 2.