pytest.ini has the --strict
option, which is deprecated since 6.2.0 as per Deprecations section for release 6.2.0 in the Release Notes and is to be removed in pytest 8.x.
Its successor --strict-markers
has been around since version 4.5.0 (Release Notes), and that version requirement is met in e.g. Ubuntu 20.04 (focal) and Debian 11 (Bullseye) as per Repology.
Please consider replacing --strict
with --strict-markers
.
Example of the warning output when running the tests:
============================= test session starts ==============================
platform linux -- Python 3.11.7, pytest-7.4.4, pluggy-1.4.0
rootdir: /build/python-et-xmlfile/src/et_xmlfile-1.1
configfile: pytest.ini
collected 118 items
et_xmlfile/tests/test_incremental_xmlfile.py ..xxx.....x....x....x....xx [ 22%]
x.....x.....x....x....xxx.....x....x....x....sxx.....x....s....x....xxx. [ 83%]
....x......x....x.. [100%]
=============================== warnings summary ===============================
../../../../usr/lib/python3.11/site-packages/_pytest/config/__init__.py:1316
/usr/lib/python3.11/site-packages/_pytest/config/__init__.py:1316: PytestRemovedIn8Warning: The --strict option is deprecated, use --strict-markers instead.
self.issue_config_time_warning(
-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
Hi @charlie.clark some problems arise building on python-embed
Collecting et-xmlfile==1.0.1 Using cached et_xmlfile-1.0.1.tar.gz (8.4 kB) ERROR: Command errored out with exit status 1: command: 'c:\xxxxxxxxxxxxxxxxxwdir\python.exe' -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\\Users\\xxxx\\AppData\\Local\\Temp\\pip-download-03_bol2j\\et-xmlfile_58712310ca9249639af7ce1c341ce36f\\setup.py'"'"'; __file__='"'"'C:\\Users\\xxx\\AppData\\Local\\Temp\\pip-download-03_bol2j\\et-xmlfile_58712310ca9249639af7ce1c341ce36f\\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base 'C:\Users\xxxx\AppData\Local\Temp\pip-pip-egg-info-xgilxc5v' cwd: C:\Users\xxxx\AppData\Local\Temp\pip-download-03_bol2j\et-xmlfile_58712310ca9249639af7ce1c341ce36f\ Complete output (5 lines): Traceback (most recent call last): File "<string>", line 1, in <module> File "C:\Users\xxxx\AppData\Local\Temp\pip-download-03_bol2j\et-xmlfile_58712310ca9249639af7ce1c341ce36f\setup.py", line 40, in <module> from et_xmlfile import ( ModuleNotFoundError: No module named 'et_xmlfile'
A public solution is here: https://superuser.com/questions/1432693/pip-install-et-xmlfile-failure/1525354#1525354?newreg=803c8546a4df4cafb2630184d3ae3290
It's really simple and solve the problem.. there is no way to create a pull request maybe some problems on project permission?
Fixed by r26
Listing python in the requires
field is unusual, and tools either ignore it or sometimes break. There's now a python_requires
keyword to express this, and tools make use of the information.
I can't seem to fork this project to make a MR, so I'm putting the change in patch format below. This is the core piece of a commit by Nathan Rosenbloom, who has made a et-xmlfile-2021
fork on PyPI.
Obviously you'd need to upload a new release for this fix to take effect.
diff -r 50973a6de49c -r 8f28d818168e setup.py
--- a/setup.py Sat Dec 15 16:53:44 2018 +0100
+++ b/setup.py Sun Mar 14 12:12:02 2021 +0000
@@ -56,9 +56,7 @@
author_email=__author_email__,
url=__url__,
license=__license__,
- requires=[
- 'python (>=2.6.0)',
- ],
+ python_requires='>=2.6, !=3.2',
classifiers=[
'Development Status :: 5 - Production/Stable',
'Operating System :: MacOS :: MacOS X',
Resolved in -r26
CharlieC (3be79a52) at 26 Apr 13:27
Remove bitbucket pipelines config and streamline setup.py
CharlieC (ace0575d) at 26 Apr 13:27
Added tag 1.1 for changeset de1a42079e16
CharlieC (3be79a52) at 26 Apr 13:21
Remove bitbucket pipelines config and streamline setup.py
... and 8 more commits
CharlieC (8cb84e2f) at 26 Apr 10:18
CharlieC (d2df4436) at 26 Apr 10:18
Merge branch 'topic/default/setup-py-sys-path' into 'branch/default'
... and 1 more commit
CharlieC (a27e9cec) at 26 Apr 10:17
Update APIDOC config
Thanks for this. I normally put all new work on a development branch so that default can always represent the last release. But due to the minor nature of the changes and the need for a new release I don't think that matters too much.
CharlieC (d0277ad4) at 26 Apr 09:13
Add CI config.