Create a asn1crypto-testdata pypi package + automate release

Trying to run the unittests in my environment I could not get them to work:

[cooper:~/asn1crypto-0.22.0:]$ ~/virtualenvs/setup_py_fun/bin/python3 setup.py test
running test
running egg_info
writing asn1crypto.egg-info/PKG-INFO
writing dependency_links to asn1crypto.egg-info/dependency_links.txt
writing top-level names to asn1crypto.egg-info/top_level.txt
reading manifest file 'asn1crypto.egg-info/SOURCES.txt'
writing manifest file 'asn1crypto.egg-info/SOURCES.txt'
running build_ext
tests (unittest.loader._FailedTest) ... ERROR

======================================================================
ERROR: tests (unittest.loader._FailedTest)
----------------------------------------------------------------------
ImportError: Failed to import test module: tests
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/unittest/loader.py", line 153, in loadTestsFromName
    module = __import__(module_name)
ModuleNotFoundError: No module named 'tests'


----------------------------------------------------------------------
Ran 1 test in 0.000s

FAILED (errors=1)
Test failed: <unittest.runner.TextTestResult run=1 errors=1 failures=0>
error: Test failed: <unittest.runner.TextTestResult run=1 errors=1 failures=0>

Playing with setup.py now.

[coreycb]

Hi, I’m working on getting the asn1crypto package supported in main for Ubuntu, however it’ll be tough to get in to main without having any tests to run. Most python projects that I’ve dealt with include tests in their released tarballs, and I think it’s a worth the effort. It’s very useful for downstream distros, etc to ensure they’ve not regressed anything.

[cooperlees]

Nice. Lets see if either of us gets time. Then we could make this main package have a tests_dep on the new package. This would allow have automatic unit test runs when we change our OS’s / libraries etc. etc.