arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-11-22 07:28:10 +00:00
Code Issues Releases Wiki Activity
7,724 Commits 350 Branches 205 Tags 207 MiB
Python 34.6%
C 33.7%
Rust 29.4%
Nix 0.6%
C++ 0.4%
Other 1.1%
67b879ac07
Go to file
matejcik 67b879ac07 python: restructure package 
This deserves some explanation.

* tests were moved to separate python/tests subdir
* trezorlib was moved to python/src, so that it does not exist on
PYTHONPATH by default
(see https://blog.ionelmc.ro/2014/05/25/python-packaging/ for details)
* everything was updated to understand the new structure
* trezorctl was changed from a top-level executable script to a module
`trezorlib.cli.trezorctl` and is installed via the entry_points
mechanism.
This should make it work normally on Windows!

The package should be installable as normal through pip and pipenv, no
changes are needed on that side.

The source package from pypi will include unit tests. (Device tests were
completely moved out). Wheel will exclude them, because users don't need
them.
That shrinks the .whl from 520 kB to 270 - nice!

python: reorganize remaining unit tests
2019-08-12 12:57:25 +02:00
ci ci: run environment only when manually triggered 2019-08-08 13:59:32 +02:00
common common/defs: add 'confidential_assets' section to coin definitions (#399) 2019-08-12 12:52:20 +02:00
core tests: drop pytest customization from core 2019-08-12 12:57:25 +02:00
crypto cardano: Implement SLIP-0023 and add SLIP-0039 support for Cardano. 2019-07-25 19:43:05 +02:00
docs/git/hooks git/hooks: do not suppress output 2019-08-02 10:39:55 +02:00
legacy core+legacy: fix KMD signing (introduce negative_fee coin field) 2019-08-09 16:47:24 +02:00
python python: restructure package 2019-08-12 12:57:25 +02:00
storage storage: fix incomatibility with new pytest 2019-07-09 14:47:24 +02:00
tests tests: move burn tests to root 2019-08-12 12:57:25 +02:00
tools python: restructure package 2019-08-12 12:57:25 +02:00
vendor core/secp256k1-zkp: use ARM assembly for field operations (#176) 2019-05-25 11:42:13 +02:00
.clang-format core+legacy: rework code styling checks 2019-04-18 17:40:55 +02:00
.gitignore ci: improve pipenv caching 2019-05-24 09:18:00 +02:00
.gitlab-ci.yml ci: update docker; no need for TLS in internal env 2019-07-29 15:23:26 +02:00
.gitmodules submodules: remove secp256k1-zkp's branch name because it will rotate 2019-06-04 08:21:42 +02:00
.travis.yml ci: run codegen checks 2019-05-17 15:49:01 +02:00
create_monorepo.py monorepo: add notes and creation tool 2019-04-15 19:16:04 +02:00
Makefile make: run flake8 during style check as well 2019-08-06 10:08:23 +02:00
Pipfile tests: add flakiness to bip32_speed test 2019-08-12 12:57:25 +02:00
Pipfile.lock tests: add flakiness to bip32_speed test 2019-08-12 12:57:25 +02:00
README-monorepo.md fix link in readme 2019-04-29 19:11:44 +02:00
README.md README: add note on CI 2019-05-23 13:19:44 +02:00
SECURITY.md add SECURITY.md 2019-06-06 19:50:57 +02:00
setup.cfg tests: enable order randomization 2019-08-12 12:57:25 +02:00
shell.nix nix: add coverage python package 2019-06-26 22:25:04 +02:00

README.md

Trezor Firmware

img

Contribute

Inspired by GitLab Contributing Guide

Security vulnerability disclosure

Please report suspected security vulnerabilities in private to security@satoshilabs.com, also see the disclosure section on the Trezor.io website. Please do NOT create publicly viewable issues for suspected security vulnerabilities.

Issue Labels

Priority

Label Meaning (SLA)
P1 Urgent The current release + potentially immediate hotfix (30 days)
P2 High The next release (60 days)
P3 Medium Within the next 3 releases (90 days)
P4 Low Anything outside the next 3 releases (120 days)

Severity

Label Impact
S1 Blocker Outage, broken feature with no workaround
S2 Critical Broken feature, workaround too complex & unacceptable
S3 Major Broken feature, workaround acceptable
S4 Low Functionality inconvenience or cosmetic issue

CI

The complete test suite is running on our internal GitLab CI. If you are an external contributor, we also have a Travis instance where a small subset of tests is running as well - mostly style and easy fast checks, which are quite common to fail for new contributors.