On 10/28/20 10:54 AM, Thomas Huth wrote:
On 28/10/2020 14.23, John Snow wrote:
On 10/28/20 2:19 AM, Thomas Huth wrote:
On 27/10/2020 23.38, John Snow wrote:
Try using pytest to manage our various tests; even though right now
they're only invoking binaries and not really running any python-nati
On 28/10/2020 14.23, John Snow wrote:
> On 10/28/20 2:19 AM, Thomas Huth wrote:
>> On 27/10/2020 23.38, John Snow wrote:
>>> Try using pytest to manage our various tests; even though right now
>>> they're only invoking binaries and not really running any python-native
>>> code.
>>>
>>> Create tests
On 10/28/20 2:23 PM, John Snow wrote:
> On 10/28/20 2:19 AM, Thomas Huth wrote:
>> On 27/10/2020 23.38, John Snow wrote:
>>> Try using pytest to manage our various tests; even though right now
>>> they're only invoking binaries and not really running any python-native
>>> code.
>>>
>>> Create tests
On 10/28/20 2:19 AM, Thomas Huth wrote:
On 27/10/2020 23.38, John Snow wrote:
Try using pytest to manage our various tests; even though right now
they're only invoking binaries and not really running any python-native
code.
Create tests/, and add test_lint.py which calls out to mypy, flake8,
py
On 27/10/2020 23.38, John Snow wrote:
> Try using pytest to manage our various tests; even though right now
> they're only invoking binaries and not really running any python-native
> code.
>
> Create tests/, and add test_lint.py which calls out to mypy, flake8,
> pylint and isort to enforce the s
Try using pytest to manage our various tests; even though right now
they're only invoking binaries and not really running any python-native
code.
Create tests/, and add test_lint.py which calls out to mypy, flake8,
pylint and isort to enforce the standards in this directory.
Add pytest to the set
