The jsonseq package has a 1.0.0 release now. It'll be good to not depend on a pre-release @mapsam.
Also, I noticed that this project's requirements specs were too tight. The tests pass using any version of pytest >= 3.6.0, boto3 as old as ~= 1.4, and requests as old as ~= 1.2. I've relaxed them.
Generally, the specs in setup.py should be as loose as possible to help the package fit into an environment with other packages. Python's environments are much flatter than Node's, remember.
Use of requirements.txt with tightly pinned versions is exactly right. That keeps builds reproducible. But requirements.txt isn't where a library's specs are kept. When you see projects doing it like that, they are often doing it wrong.
I can't push to or fork this repo, so here's a good ole diff.
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 05f9020..c89e30a 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,3 +1,8 @@
+## 0.6.2 (2019-07-31)
+
+- Requirement specifiers for the library are relaxed a bit, making this package
+ easier to install alongside other packages.
+
## 0.1.0
First release of the Mapbox Tilesets CLI tool :tada:. Includes all the things!
diff --git a/requirements.txt b/requirements.txt
index e20404f..51c2637 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -2,4 +2,4 @@ boto3==1.9.99
Click==7.0
requests==2.21.0
jsonschema==3.0.1
-jsonseq==1.0a1
\ No newline at end of file
+jsonseq==1.0.0
diff --git a/setup.py b/setup.py
index 6eb3945..2d76ba4 100644
--- a/setup.py
+++ b/setup.py
@@ -11,7 +11,7 @@ def read(fname):
return open(os.path.join(os.path.dirname(__file__), fname)).read()
setup(name='tilesets-cli',
- version='0.6.1',
+ version='0.6.2',
description=u"CLI for interacting with and preparing data for the Tilesets API",
long_description=long_description,
classifiers=[],
@@ -21,11 +21,11 @@ setup(name='tilesets-cli',
url='https://github.com/mapbox/tilesets-cli',
license='BSD-2',
packages=find_packages(exclude=['ez_setup', 'examples', 'tests']),
- install_requires=read('requirements.txt').splitlines(),
+ install_requires=["boto3", "click~=7.0", "requests", "jsonschema~=3.0", "jsonseq~=1.0"],
include_package_data=True,
zip_safe=False,
extras_require={
- 'test': ['pytest==4.3.0', 'pytest-cov'],
+ 'test': ['pytest>=3.6.0', 'pytest-cov'],
},
entry_points="""
[console_scripts]
The jsonseq package has a 1.0.0 release now. It'll be good to not depend on a pre-release @mapsam.
Also, I noticed that this project's requirements specs were too tight. The tests pass using any version of pytest >= 3.6.0, boto3 as old as ~= 1.4, and requests as old as ~= 1.2. I've relaxed them.
Generally, the specs in setup.py should be as loose as possible to help the package fit into an environment with other packages. Python's environments are much flatter than Node's, remember.
Use of requirements.txt with tightly pinned versions is exactly right. That keeps builds reproducible. But requirements.txt isn't where a library's specs are kept. When you see projects doing it like that, they are often doing it wrong.
I can't push to or fork this repo, so here's a good ole diff.