Skip to content

Don't create pyproject.toml unnecessarily when creating requirements.txt #894

@nathanjmcdougall

Description

@nathanjmcdougall

Motivation
We shouldn't need pyproject.toml - if there are no dependencies declared in pyproject.toml we can just go ahead and create the requirements file assuming there are no dependencies (actually, in reality there might be dependencies declared in setup.cfg but that's a separate issue.) Alternatively, we might infer dependencies in a more advanced approach: #893.

Summary
Don't create pyproject.toml unnecessarily when creating requirements.txt.

Metadata

Metadata

Labels

enhancementNew feature or request

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions