Configure setuptools.setup() with setup.cfg #39
Conversation
see https://setuptools.readthedocs.io/en/latest/setuptools.html#configuring-setup-using-setup-cfg-files Also this commit expands some metadata, e.g. classifiers and project_urls. Testing requirements are specified with "tests" extras. Other development requirements are tracked with "develop" extras. References to extras are supported in tests_require since setuptools v36.7.0, hence additional entry in setup_requires.
With v3.10.0 I got:
tests/test_matching.py:865
/home/sk/src/matchpy/tests/test_matching.py:865:
RemovedInPytest4Warning: MarkInfo objects are deprecated as they contain
merged marks which are hard to deal with correctly.
Please use node.get_closest_marker(name) or node.iter_markers(name).
Docs: https://docs.pytest.org/en/latest/mark.html#updating-code
names, values = obj.parametrize.args
Also fix missing newline.
|
@skirpichev What is the advantage of using |
|
More declarative config, no code at all. And all projects settings are in one place. |
|
Thank you for your contribution @skirpichev! I don't have a lot of time for this project anymore so I apologize for taking so long to get to your request. I agree with both your points about line endings and the requirements file. The version ranges are meant to prevent the package from breaking when one of the dependencies introduces breaking changes (assuming they do semantic versioning). |
I hope this project still be alive and development will be continued. This library looks to be a promising candidate to replace current pattern matching abilities in the diofant.
I think this one wasn't so important.
I'll try to fix that. |
MatchPy was developed because we need pattern matching for Linnea. As long as I'm working on Linnea, I will at least make sure that MatchPy remains in a usable state. MatchPy currently does everything I need for Linnea, so from my point of view there is nothing that urgently needs to be done. I wouldn't mind investing more work into MatchPy, but we don't have the resources (time, contributors) right now. Any help is much appreciated.
Thank you very much! |
This also fixes warnings for recent pytest.
Some side notes:
pytest>=3.0,<4.0). I'm not sure if this does make sense for a development version, unless you know that some dependency was broken in a new version.