switch to uv has removed requirements folder from generated project

[millerthegorilla]

Before I open a bug, is this expected behaviour? I just ran cookiecutter to create a new project and the generated folder structure has no requirements folder, despite it still existing in the github codebase. I understand that uv is now being used instead of pip, or whatever preceded uv, and that requirements are listed in pyproject.toml, but I am surprised to see that the requirements folder has been removed, as it is far clearer what each file does ie requirements/base.txt or requirements/local.txt and uv can be configured to read in requirements from requirements files, I think.
I use pip for venv management. If I have to switch to uv, I will, as I know it is faster, but I have seen python managers come and go, and have always ended up back with pip.

[millerthegorilla]

I also notice that despite setting github as my Source Code manager in options when generating that the project hasn't been added to a git repo inside the generated folder, so no .git folder. .gitignore exists, so perhaps this is the default, I can't recall.

[browniebroke]

The .git folder is not generated by the template, it's up to you to do it, but the .gitignore should be created.

[browniebroke]

Correct, the requirements folder is no longer used in the generated project since we moved to uv: #6139

The only reason these files are in the template is to let us keep our dependencies up to date, as Dependabot doesn't support updating a templated pyproject.toml and AFAIK PyUP does not support pyproject.toml (but supports updating a templated requirements file)

If I have to switch to uv, I will, as I know it is faster, but I have seen python managers come and go, and have always ended up back with pip.

The dependencies and dependency groups which are generated are not specific to uv, they are Python packaging standard defined by PEPs and are supported by a number of other package managers (including pip). The only bit specific to uv is the lock file, but uv has an option to export it to the standardised pylock.toml format.

With all the recent advancements in standardizing, I am far less worried about switching that I've been until now. That's also why we resisted adopting Pipenv or Poetry when they came along.

[millerthegorilla]

Ah, ok, thanks very much for the prompt reply. I shall have to take a closer look at uv generally.

[millerthegorilla]

@browniebroke hi, I note there are no instructions in the help section, yet, regarding uv. I have added some dependencies to the pyproject.toml file and when I build the containers I get the following error message:

The lockfile at `uv.lock` needs to be updated, but `--locked` was provided. To update the lockfile, run `uv lock`.

I am running as docker, but am not sure which of the dockerfiles need to be edited to allow the lock file to be updated, if that is the correct thing to do in this situation. I don't have a virtual environment with uv installed but perhaps that is the correct thing to do in order to update the lock file.
I can play around, but I would hope that some instructions could be posted on the cookiecutter site now that uv has been adopted.

[millerthegorilla]

I solved it by building the docker.compose-local.yml and then running the command uv lock as

docker compose -f docker-compose.local.yml run --rm django uv lock

[browniebroke]

What commands did you ran to hit the error? The expectation is that you would:

1. Generate the project, this should generate an up to date lockfile
2. Build the local stack once
3. From this point you can add dependencies using uv add, which should keep the lockfile up to date. If you manually edit the pyproject.toml, you have to run uv lock, either on your host machine or in the local docker container (that's why step 2 is important).

This probably could be outlined better in our docs, PR welcome to clarify the instructions.

Thanks for your feedback.

[millerthegorilla]

I was actually on my production server, getting ready to run, when I realised I hadn't the dependencies in what effectively used ot be 'base.txt' in pyproject.toml. So I added them, built the development containers and then ran the command to update the lock, and then deleted docker development containers, images, volumes, networks etc.
Are there any current instructions for the use of uv? I don't think that I am ideally placed to PR as I have virtually nil experience with it, currently.

[browniebroke]

I don't remember from the top of my head, I think we've updated our local development instructions for uv but perhaps they need expanding as folks are likely less familiar with it. I've myself been refining my workflow over the past few months.

[millerthegorilla]

I am back to django/python after a two year departure from programming anything, and always after a break am almost in the dark ages in comparison to where I need to be, the tech has advanced so quickly. Not a bad thing I guess, but I am going to have to refine my workflow for sure.
I am really struggling to get my djangocookiecutter app working in production. It works in dev mode but in production all I get is an internal server error, and am unable to get any meaningful logs - I added a log file to gunicorn but no info about any error, nothing in docker logs... etc. I am removing apps to see if they are causing the error, but am tearing my hair out, as it worked so well, behind a proxy, the last time I used it.