summaryrefslogtreecommitdiff
path: root/setup.py
Commit message (Collapse)AuthorAgeFilesLines
* docs: bye twitter, hello mastodonNed Batchelder2023-02-151-2/+2
|
* add py.typedKotlinIsland2023-02-021-0/+1
|
* build: COVERAGE_QUIETER seems to have no effect anymoreNed Batchelder2023-01-131-14/+0
| | | | | I don't remember exactly what output what being suppressed, but setting this or not seems to make no difference anymore.
* fix: isolate user code from coverage.py internal code flags. #1524Ned Batchelder2023-01-091-1/+1
|
* refactor: removed mentions of Jython and IronPythonNed Batchelder2022-12-301-4/+0
|
* fix(docs): pre-release urls were wrong in the package descriptionNed Batchelder2022-12-031-1/+10
|
* docs: mastodon linksNed Batchelder2022-12-031-0/+1
|
* build: 3.11.0 and 3.12.0a1 are availableNed Batchelder2022-10-271-0/+1
|
* Use SPDX license expression in project metadata (#1478)Frazer McLean2022-10-211-1/+1
|
* fix: use tomli for [toml] under more precise conditions. #1390Ned Batchelder2022-06-011-1/+1
|
* Use tomllib on Python 3.11 (#1359)Shantanu2022-05-151-1/+1
| | | Co-authored-by: hauntsaninja <>
* build: Build and test tweaks to help with cross-compilationSteve Dower2022-04-301-1/+1
| | | | | | | | | | | | | | | For context, I've been testing whether a range of popular libraries are going to work on Windows ARM64. (This requires compiling on a regular x64 machine and then copying the wheel to an ARM64 one for testing.) The good news is, coverage seems to be just fine without any changes. However, because of a few assumptions in the test suite about always testing an in-place build, I had to make some tweaks to be able to run tests. My proposed tweaks should be fine for current uses, but they also allow the following: * support `SETUPTOOLS_EXT_SUFFIX` when building to override the pyd tag on Windows (used with `setup.py build_ext -L <path>` to point at [pythonarm64](https://www.nuget.org/packages/pythonarm64/) import libraries to do the cross-compile) * allow `COVERAGE_INSTALL_ARGS` to override how the tests install coverage into a venv (allows to point at a wheel rather than rebuilding from the sources) * allow `python igor.py remove_extension --from-install` to delete the extension module from `site-packages` rather than only the source tree * other changes to allow removing the `coverage` directory from the source tree before tests so that the installed copy will be used instead. I've tested these on my own Windows ARM64 machine, though unfortunately there aren't any available on CI services yet. If you wanted to start releasing (preview) wheels for win-arm64 you can, but there's no support (yet) in `cibuildwheel` or `build` to do it (because those tools don't really have a concept of cross-compilation for Windows at all... yet ;-) ). For the linter
* build: drop Python 3.6 supportNed Batchelder2021-12-311-3/+3
|
* typoNed Batchelder2021-11-111-1/+1
| | | | [skip actions]
* fix: CPython 3.11 support. #1241Ned Batchelder2021-11-101-0/+1
| | | | | | | | | | | The fix for CTracer is egregious and will need to be updated when there's a supported way to do it. The fullcoverage skip is noted in https://github.com/nedbat/coveragepy/issues/1278 The raise_through_with skip is noted in https://github.com/nedbat/coveragepy/issues/1270
* style: remove implicit string concatenationNed Batchelder2021-10-301-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | .. and also add trailing commas where needed to remove ambiguity. I used semgrep with this config: ``` rules: - id: implicit-string-concatenation pattern: | "$X" "$Y" languages: - python message: string cat BAD severity: INFO ``` Running it showed this: ``` $ semgrep --config=../lab/string-cat.yml coverage tests doc ci igor.py setup.py __main__.py Running 1 rules... setup.py severity:info rule:lab.implicit-string-concatenation: string cat BAD 128: 'https://tidelift.com/subscription/pkg/pypi-coverage' 129: '?utm_source=pypi-coverage&utm_medium=referral&utm_campaign=pypi' tests/test_api.py severity:info rule:lab.implicit-string-concatenation: string cat BAD 319: "!coverage.py: This is a private format, don't read it directly!" 320: '{"lines":{"/private/tmp/foo.py":[1,5,2,3]}}' tests/test_html.py severity:info rule:lab.implicit-string-concatenation: string cat BAD 614: ('<span class="key">if</span> <span class="num">1</span> ' 615: '<span class="op">&lt;</span> <span class="num">2</span>'), -------------------------------------------------------------------------------- 616: (' <span class="nam">a</span> ' 617: '<span class="op">=</span> <span class="num">3</span>'), -------------------------------------------------------------------------------- 665: ('<span class="key">if</span> <span class="nam">x</span> ' 666: '<span class="op">&lt;</span> <span class="num">2</span>'), -------------------------------------------------------------------------------- 667: (' <span class="nam">a</span> <span class="op">=</span> ' 668: '<span class="num">3</span>'), -------------------------------------------------------------------------------- 949: ('<span class="key">if</span> <span class="num">1</span> ' 950: '<span class="op">&lt;</span> <span class="num">2</span>'), -------------------------------------------------------------------------------- 951: (' <span class="nam">a</span> <span class="op">=</span> ' 952: '<span class="num">3</span>'), ran 1 rules on 134 files: 8 findings ``` This wasn't all of the instances, so I wrote a bug report: https://github.com/returntocorp/semgrep/issues/4184
* style: remove mention of Python 2Ned Batchelder2021-10-301-2/+2
|
* Add link to coverage.py twitter account to project urls (#1217)Asher Foa2021-08-301-0/+1
|
* fix: raise chained errors with "from" #998Ned Batchelder2021-07-201-5/+5
| | | | | | This makes exceptions report their causes correctly, as "The above exception was the direct cause of the following exception" instead of "During handling of the above exception, another exception occurred."
* Support TOML v1.0.0 syntax in `pyproject.toml` (#1186)Thomas Grainger2021-07-131-1/+1
| | | | | | | | | | | | | | | | | * Support TOML v1.0.0 syntax in `pyproject.toml` fixes #1180 Co-authored-by: Taneli Hukkinen <3275109+hukkin@users.noreply.github.com> * fix toml meta test * use pytest.mark.parametrize to narrow test failure * Update tests/test_config.py Co-authored-by: Taneli Hukkinen <3275109+hukkin@users.noreply.github.com> Co-authored-by: Taneli Hukkinen <3275109+hukkin@users.noreply.github.com>
* refactor: pyupgrade --py36-plus *.pyNed Batchelder2021-05-021-3/+3
|
* build: next version will be 6.0, dropping support for 2.7 & 3.5Ned Batchelder2021-05-011-5/+2
|
* Removed python_requires="<4" Nicholas Nadeau, Ph.D., P.Eng2021-03-031-1/+1
| | | Python 4 doesn't exist, this requirement is redundant
* Better control over setup.py warningsNed Batchelder2021-01-101-1/+14
|
* Python 3.10Ned Batchelder2020-10-101-0/+1
|
* Adapt to 3.9's way of reporting files using absolute paths.Ned Batchelder2019-11-251-0/+1
|
* Cleanups for TOML codeNed Batchelder2019-11-031-1/+1
|
* TOML support for pyproject.toml and other config filesFrazer McLean2019-11-031-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Squashed and rebased from https://github.com/nedbat/coveragepy/pull/699 Missing getfloat TOMLConfigParser -> TomlConfigParser fix getfloat for int Move TomlConfigParser Add name to contributors Import toml in backward.py fix indentation Don't ignore TomlDecodeError Raise if TomlConfigParser is used without toml installed Add tests for TOML config Fix test on Python 2 Mention toml support in documentation.
* Quiet pylintNed Batchelder2019-10-061-3/+3
|
* Doc changes for 5.0a7Ned Batchelder2019-09-211-2/+0
|
* No need for format indexes (mostly)Ned Batchelder2019-09-011-1/+1
|
* One more 'drop 3.4' changeNed Batchelder2019-03-101-1/+1
|
* Drop support for Python 3.4Ned Batchelder2019-03-101-1/+0
|
* Fix two issues with setup.pyNed Batchelder2019-03-101-1/+5
|
* Add project_urlsNed Batchelder2019-03-091-1/+5
|
* Test that we have the right Python versions in the classifiersNed Batchelder2018-11-251-0/+1
|
* Remove use_2to3=False; it is the defaultJon Dufresne2018-10-271-7/+0
| | | | Slightly simplifies setup.py.
* Check for import orderNed Batchelder2018-09-131-3/+5
|
* Change url in the distribution to GitHubNed Batchelder2018-06-241-1/+1
|
* Update NOTICE link to GitHub.Ned Batchelder2018-06-241-1/+1
|
* No more support for 2.6 or 3.3Ned Batchelder2018-05-051-3/+1
|
* I guess prevent installation on Python 4?Ned Batchelder2018-01-141-1/+1
|
* Pass python_requires argument to setuptoolsJon Dufresne2018-01-111-0/+2
| | | | | | | | | | | | | | | | | | | Helps pip decide what version of the library to install. https://packaging.python.org/tutorials/distributing-packages/#python-requires > If your project only runs on certain Python versions, setting the > python_requires argument to the appropriate PEP 440 version specifier > string will prevent pip from installing the project on other Python > versions. https://setuptools.readthedocs.io/en/latest/setuptools.html#new-and-changed-setup-keywords > python_requires > > A string corresponding to a version specifier (as defined in PEP 440) > for the Python version, used to specify the Requires-Python defined in > PEP 345.
* Update all Read the Docs links to use httpsJon Dufresne2018-01-061-1/+1
|
* Version 4.4.2 prepNed Batchelder2017-11-041-0/+1
|
* Point 'home page' on pypi to bitbucketNed Batchelder2017-11-041-1/+1
|
* Add missing classifiers for supported Python versionsJon Dufresne2017-10-211-0/+3
| | | | Documents support for general Python, Python 2, & Python 3 support.
* Add IronPython to the classifiersNed Batchelder2017-04-151-0/+1
|
* Install the fullcoverage support for CPython's useNed Batchelder2017-02-081-0/+1
|
* Prep for version 4.3.2Ned Batchelder2017-01-161-0/+1
|
View Lorry Controller Status