Releases: pystorm/streamparse
Releases · pystorm/streamparse
v5.0.1
What's Changed
- Fix Read The Docs by @kbourgoin in #506
- Fix util.py:nimbus_storm_version by @maciej-lech in #501
New Contributors
- @rachelannelise made their first contribution in #504
- @maciej-lech made their first contribution in #501
Full Changelog: v5.0.0...v5.0.1
5.0.0
- Pin setuptools to 69.5.1 prevent API breakages while deploying
4.1.2
streamparse 4.1.1
streamparse 4.0.0
⚠️ Backward Incompatible Changes ⚠️
- streamparse now only supports Python 3.6+
Features
- Switched depending on
thriftpytothriftpy2, becausethriftpyis no longer maintained (PR #481)
streamparse 3.16.0
Features
- Faster virtualenv creation when passing multiple requirements files to
sparse submit(PR #459) - Add
sudo_useroption toconfig.jsonthat can be used for specifying a different user that is used for virtualenv creation/deletion instead of always using the SSH login user. (PR #455)
Fixes
- Fix typo that would cause
update_virtualenvto when no CLI options were passed (PR #459)
streamparse 3.15.1
Fixes
- Make
update_virtualenvcreate virtualenvs as sudo user, and not just when trying to delete them (0250cfa) - Prevent pip 19.0 from being installed because it breaks
--no-cache-dirinstalls (db26183) - Prevent virtualenv from downloading pip versions other than what we have pinned (0573bc8)
- Make redis examples work with
sparse runagain (b61c85d) - Fix issues where
repr(Topology)was alwaysNone(fd5b4b6)
Misc.
- Simplify Travis setup (#454)
streamparse 3.15.0
Features
- Allow submitting topologies as inactive/deactivated (PR #448)
- Stop pinning pip to 9.x when running
update_virtualenv(PR #444)
Fixes
- Added missing
optionsargument to bootstrap project (PR #436) - Import fixes in redis example (PR #451)
- Fix issues with virtualenv-related option resolution, which made options only in
config.jsonnot get used. (PR #453)
Misc.
- Reformatted code with black
streamparse 3.14.0
streamparse 3.13.1
This fixes an issue with the --overwrite_virtualenv option introduced in 3.13.0 when some of the files in the virtualenv are not removable due to insufficient permissions. You can now specify the user to user for removing them with --user. We also delete using sudo by default now. (PR #417)