From ad392bda2a5469bb59d779df4d7ce80187eadd55 Mon Sep 17 00:00:00 2001 From: matt Date: Sun, 7 Jul 2019 00:37:08 -0600 Subject: [PATCH] done. --- .travis.yml | 1 - README.md | 3 ++- setup.py | 5 ++--- 3 files changed, 4 insertions(+), 5 deletions(-) diff --git a/.travis.yml b/.travis.yml index 8f511f4..4beb23c 100644 --- a/.travis.yml +++ b/.travis.yml @@ -10,7 +10,6 @@ jobs: include: - python: '3.7' - python: '3.6' - - python: '3.5' - stage: deploy install: '' script: '' diff --git a/README.md b/README.md index 174bdb9..89e128d 100644 --- a/README.md +++ b/README.md @@ -6,6 +6,7 @@ blazing fast template matching when possible images are all known. Handy tool fo ## How to Use +It supports python 3.6 + `pip install whichimg` @@ -42,4 +43,4 @@ naive_tell([img1, img2, img3, img4], secret_img) It's **not** generally faster than the naive approach. I thought my approach was faster and spent a week writing this shit though. lmfao. -They're about equally fast on the `tests/fixtures` testing data I came up with (10x10 images). Through my rought testing, there could be a magnitude of performance gain when there are many possible images (>10) and when the images are larger (200x200 for example). \ No newline at end of file +They're about equally fast on the `tests/fixtures` testing data I came up with (10x10 images). Through my rough testing, there could be a magnitude of performance gain when there are many possible images (>10) and when the images are larger (200x200 for example). \ No newline at end of file diff --git a/setup.py b/setup.py index c9383e4..1afb4ec 100644 --- a/setup.py +++ b/setup.py @@ -42,7 +42,7 @@ # For a discussion on single-sourcing the version across setup.py and the # project code, see # https://packaging.python.org/en/latest/single_source_version.html - version="1.0.2", # Required + version="1.0.3", # Required # This is a one-line description or tagline of what your project does. This # corresponds to the "Summary" metadata field: # https://packaging.python.org/specifications/core-metadata/#summary @@ -96,7 +96,6 @@ # that you indicate whether you support Python 2, Python 3 or both. # These classifiers are *not* checked by 'pip install'. See instead # 'python_requires' below. - "Programming Language :: Python :: 3.5", "Programming Language :: Python :: 3.6", "Programming Language :: Python :: 3.7", ], @@ -121,7 +120,7 @@ # and refuse to install the project if the version does not match. If you # do not support Python 2, you can simplify this to '>=3.5' or similar, see # https://packaging.python.org/guides/distributing-packages-using-setuptools/#python-requires - python_requires=">=3.5", + python_requires=">=3.6", # This field lists other packages that your project depends on to run. # Any package you put here will be installed by pip when your project is # installed, so they must be valid existing projects.