Fixing tuple, and 'UTC has no key' errors in examples/FinRL_PaperTrading_Demo.ipynb #1186
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have submitted a similar pull request at FinRL-Tutorials. Still, I think it should also be updated here since more people might come here to view the
example
files, and are unaware of the tutorial repository.An updated version of the
gymnasium
package changes the behavior ofgymnasium.Env.reset
. The return value of the reset method now returns a tuple of observation and info, which causes the tuple error mentioned in #1184 and #1164. Please refer to the gymasium's documentation for more details. This is fixed by ignoring the second value in the returned tuple.The current version of the exchange-calendars package requires the dates to be timezone native, which causes the "UTC has no key" error. The traceback can be found below. This was resolved by erasing tz=pytz.UTC.