Green

Latest version: v4.0.2

Safety actively analyzes 710445 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 11 of 16

2.1.0

19 October 2015

- Removed official Python 3.4+ support on Windows, due to AppVeyor's
aggravating fail-4-times-out-of-5 behavior which I can't replicate at all on
real windows. If someone wants to help find the problem so we can have
consistent builds, I would be happy to restore official Python 3.4+ support
on Windows. In practice, everything functions fine on Windows as far as I
can tell, but this will drift in the future without builds to let us know
what breaks.

- Added `-u/--include-patterns` argument to pass through a list of include
patterns to coverage. See the help docs for more info.

- Fixed a crash during handling a crash in loader code due to incorrect string
formatting - contributed by jayvdb

- Green can now be run as a module with `python -m green` syntax - contributed
by krisztianfekete, fixes 91

- Fixed the text describing the ordering of the screenshots - reported by
robertlagrant

2.0.7

18 September 2015

- Fixed help documentation for `-s/--processes` to account for changes made in
the 2.0.0 overhaul. Fixes 83.

2.0.6

14 September 2015

- Green no longer follows symlinks during discovery, to avoid infinite
discovering.

2.0.5

14 September 2015

- Green no longer ignores config files when run as through django. Fixes 79
and 82.

- Green no longer crashes when run through django when no tests are present.

- Coverage output now appears before the summary, so that long coverage lists
don't make it difficult to tell whether tests passed or not.

- Fixed a bug that would cause a crash if a python package with an invalid (and
thus un-importable) name existed within the discovery scope.

- Updated the readme: swapped the features and screenshots section, swapped the
positioning of the two screenshots.

2.0.4

27 August 2015

- Fixed a bug that was causing crashes when subclassing Twisted's version of
TestCase.

2.0.3

23 August 2015

- When you use Python 2.7 and your failing test has a traceback that refers to
a line that has unicode literals in it, green will now catch the resulting
UnicodeDecodeError raised while trying to format the traceback and tell you the
module it was trying to import and that it couldn't display the correct
traceback due to the presence of a unicode literal. Resolves 77.

Page 11 of 16

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.