Skip to content

Release v2.9.0 #629

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Dec 19, 2019
Merged

Release v2.9.0 #629

merged 7 commits into from
Dec 19, 2019

Conversation

araffin
Copy link
Collaborator

@araffin araffin commented Dec 19, 2019

Description

This is the (Christmas) v2.9.0 release.

Motivation and Context

  • I have raised an issue to propose this change (required for new features and bug fixes)

I also updated the documentation and docstrings at some places:

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation (update in the documentation)

Checklist:

  • I've read the CONTRIBUTION guide (required)
  • I have updated the changelog accordingly (required).
  • My change requires a change to the documentation.
  • I have updated the tests accordingly (required for a bug fix or a new feature).
  • I have updated the documentation accordingly.
  • I have ensured pytest and pytype both pass.

setup.cfg Outdated
@@ -19,4 +19,3 @@ filterwarnings =

[pytype]
inputs = stable_baselines
python_version = 3.5
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we dropping support for 3.5? If so we should specify the lowest supported version here. We should probably also add a python_requires in setup.py

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a way to allow using pytype with python > 3.5?
I removed this line because I had to comment it each time I wanted to check typing, which was quite annoying.
If there is no other mean, I'll put that line back.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so, no drop of python 3.5 support yet (I would have created an issue if this was the case)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think pytype always type checks with the Python version of the interpreter it's running under, which is a bit annoying. If you don't specify it then it'll use the system default. It seems unfortunate to get different type check results depending on what system you're running on, but uncommenting the line does sound frustrating.

Could you install Python 3.5 in addition to the Python interpreter you normally use?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can but this would mean duplicating a complete conda env only for this particular purpose.
i'll put the line back

Copy link
Collaborator

@AdamGleave AdamGleave left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@araffin araffin merged commit 98e9ee9 into master Dec 19, 2019
@araffin araffin deleted the release/v2.9.0 branch December 19, 2019 23:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Structure of ReplayBuffer._storage Weird tensorboard plots in GAIL assert self.n_batch % self.nminibatches == 0 AssertionError
2 participants