A little hunting didn’t turn up anything on this, though I recall reading something of the like recently that I now can’t find.
I’m working on a project that has no runtime dependencies, Python’s stdlib is sufficient. But to build the package, there are external requirements - most notably sphinx (and the cascade of things that come with it) and lxml for the relatively complex documentation build. Is there some accepted practice to separate the description of these? If the package-build requirements are dumped into
requirements.txt, then various things make assumptions based on that being found in the github top directory - IDEs, automated scanning tools, etc. and I’m not really fond of that.