deprecate setup.cfg support
See original GitHub issue#3062 demonstrates that its not a sustainable option to hijack config files that will be parsed using a different parser
we should deprecate setup.cfg
usage and unless someone comes up with a sustainable option to support it, drop it
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Eventually deprecate `setup.cfg` with automatic conversion to ...
The current documentation regarding `pyproject. toml` claims that support for using it to specify package metadata and build configuration ...
Read more >Is `setup.cfg` deprecated? - python - Stack Overflow
Nope, setup.cfg it is not deprecated and the documentation you mention is misleading. There were ...
Read more >Configuring setuptools using setup.cfg files
The find_namespace: directive is supported since Python >=3.3. [5]. data_files is deprecated and should be avoided. Please check Data Files ...
Read more >Why you shouldn't invoke setup.py directly - Paul Ganssle
The setuptools project has stopped maintaining all direct invocations of setup.py years ago, and distutils is deprecated. · Direct invocations of ...
Read more >Doesn't my project need a setup.py or setup.cfg file?
The landscape of Python packaging is shifting and Setuptools has evolved to only provide backend support, no longer being the de-facto packaging tool...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@blueyed feel free to make a pr implementing that
im going to deprecate it as i dont have the time and motivation and its currently broken in strange ways - im happy to keep it if somebody comes up with a reasonably correct way to have pytest config in setup.cfg that is not completely mindboogling
however also keep in mind that
pyproject.toml
is upcoming, already standardized and very likely a much saner migration targetMy bad guys. I’ve changed the title to what I think better conveys the purpose of the issue then, let me know if it’s not good yet.