Poetry VS pyenv

Package Manager: Poetry is recommended for managing dependencies, though pip can also be used.

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"]

Personally, I’m a big fan of pyenv, so that’s what I’ll be using here. I’ve already got it installed on my laptop since it’s my go-to for work and personal projects.

PyFabricate queries pyenv for the developer installed Python versions. These are the only ones from which PyFabricate can create Python virtual environments.

We actively use environment managers pyenv, goenv and nvm for managing multiple versions of Python, Golang and NodeJS at Mantis. These provide us with an easily manageable, robust development environments.

Management of different language versions and interpreters is somewhat of a gray area in the Pythonic world as of September 2024, but of course the community has "unofficial" solutions that circumvent this problem. One particular good one is PyEnv, that borrows heavily from ruby's solutions for version management, which is something ruby does very well. PyEnv is basically a collection of shell scripts that help to install and select a specific python version or interpreter, in both global and localized scopes. It works by inserting a directory of shims in the PATH and will rehash the shim according to specific conditions in order to map the python binary (as well as other setup such as mapping pip, switching the PYTHON_VERSION env, etc). This guide will focus on MacOS and the Debian-family linux distros, and will cover setup on both bash and zsh. It will not cover pyenv-win.

In the case of pre-commit hooks, the runtime either has to be installed manually by every user (in the case of Husky) or is handled in Python (in the case of pre-commit). Running Node.js through Python/pyenv introduces an additional layer of complexity, which can lead to issues like OpenSSL library incompatibilities.

Install pyenv or pyenv-win

Let's get some initial setup out of the way, starting by an empty directory and a virtual environment. Create a new directory with any name you like, and a virtual environment with your preferred tool. I personally use Pyenv. It is worth noting that this tutorial was created with Python 3.11.3, and SQLAlchemy version 2.0.27.

If you have a requirement for multiple, specific Python versions, why not just use pyenv?

https://github.com/pyenv/pyenv

For more information visit: pyenv repository