summaryrefslogtreecommitdiff
path: root/setup.cfg
AgeCommit message (Collapse)Author
2024-10-01mark the PyPI metadata as supporting python 3.13Eli Schwartz
meson runs okay on 3.13, since release 1.5.0 / https://github.com/mesonbuild/meson/pull/13205
2023-10-03mark the PyPI metadata as supporting python 3.12Eli Schwartz
meson itself runs okay on 3.12, and the last issue for *probing* against 3.12 is solved. Tests pass here locally.
2023-08-18tests: fix assertion rewriting when pytest is usedBenoit Pierre
2023-06-28fix setuptools deprecation warning for renamed metadata keyEli Schwartz
Licenses can be plural, so the official key here has an "s" at the end and triggers a deprecation warning for the old name.
2023-06-28add additional setuptools metadata pointing to the source repositoryEli Schwartz
Currently, PyPI shows one link for meson -- to the homepage (the docs site). Provide an additional convenient link to the github repo.
2022-12-21meta: add python 3.11 classiferMichael Hirsch
2022-04-09packaging: make sure pyinstaller sees our distributed data filesEli Schwartz
Running pyinstaller to create a bundle, and using the resulting `pyinst-tmp/meson/meson setup ...` with the cmake module revealed that no data files were being bundled, unlike what we did for setup.cfg. Fix this oversight. Fixes #10163
2022-02-09setup.cfg: update classifier, drop deprecatedHenry Schreiner
This adds 3.10 (didn't check to see if it was tested on 3.10, that should be done, but I'm using it on 3.10). setup_requires is deprecated and should be producing warnings on modern setuptools, and never worked for setuptools anyway - setuptools can't update itself, and setuptools is what is reading this anyway!
2022-02-09pypi: include a ninja extraHenry Schreiner
This will really help with pipx run, as `pipx run meson[ninja]` will now work on any system with pipx 0.17 or newer, no dependencies required. This now includes GitHub Actions, which just updated to pipx 1.0.0. Pipx run lets you use recent (always <1 week old) versions of anything on PyPI.
2022-01-10port from embedded data to importlib.resourcesEli Schwartz
2022-01-10bump minimum required version of python to 3.7Eli Schwartz
Comment out the pending deprecation notice. It cannot be reached anymore, but is still useful for the next time we do a version bump.
2021-10-25make sure the devenv powershell script is actually distributedEli Schwartz
It's not a python file, so it will never end up in the installed package unless we mark it as package_data. This causes problems for people using non-git checkouts. Fixes #9435 Closes #9443
2021-06-02adding a _typing moduleDylan Baker
this is a place that *must* only be imported inside a if typing.TYPE_CHECKING block. It is a mixture of smoothing over thinigs that moved from typing_extensions to typing in later python versions and useful but typing only code. This makes typing_extensions required for python versions older than 3.8 *when running mypy*. typing_extensions should *only* be imported inside an `if typing.TYPE_CHECKING` block (include the new _typing.py module) to ensure that it doesn't become a runtime dependency
2021-05-13setup.cfg: update version metadata [skip ci]Michael Hirsch
Co-authored-by: Michael Hirsch <scivision@users.noreply.github.com>
2021-03-10setuptools: move stuff to declarative cfg if possible [skip ci]Eli Schwartz
We're down to just declaring the data files in python now. setup.cfg can, uniquely, retrieve version info by trying to parse the AST for simple assignments (which we use) instead of importing the entire module.
2020-11-20setup.cfg: fix python requires to be 3.6.0Dylan Baker
2020-10-30setup.cfg: Add pytest discovery argsDylan Baker
We have a single giant file for our tests, but a number of files that match pytest's default discovery globs. To fix that, let's tell pytest what to do. This means you can just `pytest` and get the right results. It also helps IDE's like vscode correctly identify tests.
2020-04-21setup.cfg: Mark setuptools as requiredDylan Baker
It's required, lets just document it as such.
2019-12-05pytest: Fix test warningsDaniel Mensinger
2019-11-02Ensure setuptools via PEP508/518 pyproject.tomlMichael Hirsch, Ph.D
2019-07-11Remove unnecessary setup.cfg lines that confound offline useMichael Hirsch, Ph.D
2019-07-11minimum python 3.5.2Michael Hirsch, Ph.D
2019-07-11ENH: metadata PEP390 setup.cfgMichael Hirsch, Ph.D
https for Meson docs url Co-Authored-By: Elliott Sales de Andrade <quantum.analyst@gmail.com>
2019-04-29Fix builtin variable namesDaniel Mensinger
2018-12-02flake8: ignore W504: line break after binary operatorXavier Claessens
It wasn't an error before, and plenty of files does that.
2018-07-02setup.cfg: Don't warn about commented codeNirbheek Chauhan
2018-06-06Fix issues found by flake8Xavier Claessens
2017-09-21flake8: disable E731: do not assign a lambda expression, use a defLuke Shumaker
It has too many false positives. It was complaining about things like if this: fn = some_func else: fn = lambda x: ... Where obviously, "fn" can't be a def, and it would be silly to introduce some other name to use as the def, just to assign it to fn.
2017-01-28vs: Use CompilerArgs() for compile and link argsNirbheek Chauhan
At the same time also fix the order in which they are added. They now match the order used in the Ninja backend.
2017-01-28Disable E266 in flake8Nirbheek Chauhan
Don't tell me how to format my comments!
2017-01-11style: disable flake8 warnings E241, E251, E305, E401Mike Sinkovsky
2016-12-29setup.cfg: fix syntaxIgor Gnatenko
2016-12-28Just say no.Jussi Pakkanen
2016-12-23setup.cfg: ignore couple of PEP8 errorsIgor Gnatenko
We don't care about E261 and temporarily ignore E501. Signed-off-by: Igor Gnatenko <i.gnatenko.brain@gmail.com>
2016-12-21Shut down the noise.Jussi Pakkanen
2016-12-21add flake8 configurationIgor Gnatenko
Signed-off-by: Igor Gnatenko <i.gnatenko.brain@gmail.com>