summaryrefslogtreecommitdiff
path: root/setuptools/config/_apply_pyprojecttoml.py
Commit message (Collapse)AuthorAgeFilesLines
* Overhaul for better visibility of warnings (#3849)Anderson Bravalheri2023-04-201-21/+17
|\
| * Cluster deprecations due_dateAnderson Bravalheri2023-03-071-2/+2
| |
| * Use new warnings in setuptools/config/_apply_pyprojecttoml.pyAnderson Bravalheri2023-03-071-21/+17
| |
| * Import SetuptoolsDeprecationWarning from setuptools.warningsAnderson Bravalheri2023-03-061-1/+1
| |
* | Fix '_WouldIgnoreField' warnings for scripts/gui_scriptsAnderson Bravalheri2023-03-201-1/+7
|/
* Ensure file referenced by 'license.file' in pyproject.toml is added to sdistAnderson Bravalheri2023-01-191-0/+1
|
* Ensure file referenced by 'readme' in pyproject.toml is added to sdistAnderson Bravalheri2023-01-191-3/+9
|
* Clarify modules used for pyproject.toml parsing are privateAnderson Bravalheri2022-06-171-0/+2
|
* fixed some spelling mistakes,Bastian Venthur2022-06-141-1/+1
| | | | that's all :)
* Improve warning message for _WouldIgnoreFieldAnderson Bravalheri2022-05-181-3/+5
|
* Add deprecation messages for `namespace_packages` (#3262)Anderson Bravalheri2022-05-161-0/+11
|\
| * Add deprecation messages for `namespace_packages`.Anderson Bravalheri2022-05-161-0/+11
| | | | | | | | | | | | | | | | The docs in https://setuptools.pypa.io/en/latest/userguide/package_discovery.html and https://packaging.python.org/en/latest/guides/packaging-namespace-packages/ suggest that this field is deprecated.
* | Remove residual dependencies from setup.py when dependencies are set in ↵Anderson Bravalheri2022-05-161-2/+4
|\ \ | |/ |/| | | pyproject.toml (#3306)
| * Add warning about overwritten dependenciesAnderson Bravalheri2022-05-041-2/+4
| |
* | do not backfill Project-URL: homepage into Home-page: field (causes ↵wim glenn2022-04-291-15/+1
|/ | | | duplicates on PyPI). prevent "UNKNOWN" vals from appearing in summary, license, platform. prevent an extra newline getting added in long description
* Fix previous detection of empty arraysAnderson Bravalheri2022-03-271-1/+1
|
* Merge pre-set dependencies when applying pyprojectAnderson Bravalheri2022-03-271-2/+12
|
* Prepare to be strict in the future about entry-points in pyprojectAnderson Bravalheri2022-03-271-3/+3
|
* Improve error/warning messagesAnderson Bravalheri2022-03-271-2/+5
|
* Consider missing edge case for tool.setuptools.dynamic in pyprojectAnderson Bravalheri2022-03-271-1/+0
|
* Warn if a project metadata is set outside of pyproject without dynamicAnderson Bravalheri2022-03-271-10/+89
| | | | | | | | | | | | | | - PEP 621 requires the build backend to not backfill values without dynamic. - Some users seem to been writing ``pyproject.toml`` with a "partial" ``[project]`` table even before setuptools added support for pyproject metadata. In several cases this table is incomplete and the real metadata lives either in ``setup.py`` or ``setup.cfg``. To avoid ignoring metadata in these scenarios and resulting in failing builds, the change implemented here adopts a more "forgiving" posture and warns an informative message during the transition period.
* Tests mixed pyproject metadata + config from setup.pyAnderson Bravalheri2022-03-271-0/+31
| | | | With emphasis on the ``dynamic`` behaviour
* Temporarily forgive popular patterns on invalid pyproject.tomlAnderson Bravalheri2022-03-261-0/+3
|
* Use blank lines to emphasize warningsAnderson Bravalheri2022-03-201-2/+2
| | | | This matches the level of emphasis used by distutils.
* Attempt to clarify which url is missing for pyproject-metadata buildsAnderson Bravalheri2022-03-201-5/+15
| | | | | | | | | | | | | | | | | When the user does not specify `Homepage` (or any variant such as `home-page`), distutils will warn the following message: warning: check: missing required meta-data: url This message is fine for `setup.cfg` builds because the field there is called `url`, but it does not work well for builds using pyproject.toml metadata. The change implemented here will add some other logging information that try to point the user in the correct direction for solving this issue. This problem was first identified in: https://discuss.python.org/t/help-testing-experimental-features-in-setuptools/13821
* Change pyproject.toml processing to not use dynamic for license/license-filesAnderson Bravalheri2022-03-091-24/+5
|
* Add some type hints to config.pyprojecttomlAnderson Bravalheri2022-03-051-1/+1
|
* Back-fill Description-Content-Type according to readme suffixAnderson Bravalheri2022-03-051-2/+23
| | | | | | | | | | | | According to PEP 621, the backend should fill-in the content-type if the `readme` field is passed as a string. The value is derived from the extension of the file (an error should be raised when that is not possible). Previously all READMEs were wrongly assumed rst. This error was reported in: https://discuss.python.org/t/help-testing-experimental-features-in-setuptools/13821/4
* Avoid using pkg_resources for entry pointsAnderson Bravalheri2022-03-051-5/+6
|
* Add means of applying config read from pyproject.toml to distAnderson Bravalheri2022-03-051-0/+236
Since the Distrubition and DistributionMetadata classes are modeled after (an old version of) core metadata, it is necessary to add a translation layer between them and the configuration read from pyproject.toml