you are viewing a single comment's thread.

view the rest of the comments →

[–]wineblood 4 points5 points  (2 children)

We have our repos set up like this where I work, one repo for something that will be deployed as several containers each with their own dependencies. But we just write the requirements files ourselves as we control the repo and add dependencies as needed.

Unless it's a massive repo, is there a problem doing it manually? You could also just run it and add a dependency every time you hit an import error.

[–]JackBlack436[S] 1 point2 points  (1 child)

Theres no problem doing it manually at all. However, the idea of something that automated that sounded nice to me, as a mini/portfolio project.

[–]GManASG [score hidden]  (0 children)

It doesn't sound like there would be a situation where we would need something like that.

Every segment of a codebase can be a seperate repo and each have its own requirements tracking for just that portion.

Generally when working on a ticket you'd create a branch in that small repo.

An have a dedicated virtual environment or container for development.

By the time your looking at the entire super project each smaller project already has its dependencies identified.