trezor-firmware

Author	SHA1	Message	Date
matejcik	edfc857013	build: include all of trezor-common in MANIFEST because now we are not simply copying the coins.json file but building it from several. For future-proofness, it's simply safer to include all of trezor-common.	6 years ago
matejcik	16b0727b4b	build: include tools in sdist	6 years ago
matejcik	c844430363	build: include relevant vendored files in sdist	6 years ago
Saleem Rashid	1c8f03968c	tests: Move to trezorlib.tests	7 years ago
Pavol Rusnak	ec966a0111	rename txcache files to json	8 years ago
Pavol Rusnak	34e089d067	add bash_completion.d into source tarball	8 years ago
Jonny Heggheim	ad6a2160cc	Include the COPYING in sdist (#82 )	8 years ago
Edward Betts	0c0d7ef893	Include tests in release source tarball It would be great to include the test suite in the pypi release tarball. That way people who download and build the release can run the tests to ensure the library is working. Linux distributions, such as Debian, base their packages of Python modules on the pypi release. This means the test suite can be run when building a Debian package, it should catch mistakes in the packaging or errors in dependencies. I've written some more on this topic on the Debian Python mailing list. https://lists.debian.org/debian-python/2016/04/msg00074.html	8 years ago