Skip to content
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

Python 3.8 #292

Merged
merged 8 commits into from
Mar 6, 2020
Merged

Python 3.8 #292

merged 8 commits into from
Mar 6, 2020

Conversation

davvid
Copy link
Member

@davvid davvid commented Feb 28, 2020

Add support for Python 3.8.

Signed-off-by: David Aguilar <davvid@gmail.com>
tox's verbose flag is "-v", not "--verbose".

Signed-off-by: David Aguilar <davvid@gmail.com>
Signed-off-by: David Aguilar <davvid@gmail.com>
Signed-off-by: David Aguilar <davvid@gmail.com>
Signed-off-by: David Aguilar <davvid@gmail.com>
Python3.8 now returns file descriptors as io.TextIOWrapper objects.

Add a custom handler that drops these to None.

Closes jsonpickle#281
Signed-off-by: David Aguilar <davvid@gmail.com>
@hartwork
Copy link
Contributor

hartwork commented Mar 2, 2020

Did you forget to add 3.8 to .travis.yml?

python:
- "2.7"
# - "3.4" # tox fails in 3.4, jobs timeout
# - "3.5" # ecdsa tests fail in 3.5.
- "3.6"
- &latest_py3 "3.7"

Signed-off-by: David Aguilar <davvid@gmail.com>
@davvid
Copy link
Member Author

davvid commented Mar 3, 2020

@hartwork thanks for the heads-up. I just added it -- wasn't sure if travis supported it yet.

Signed-off-by: David Aguilar <davvid@gmail.com>
@davvid davvid merged commit 9a3284f into jsonpickle:master Mar 6, 2020
@davvid davvid deleted the python3.8 branch March 6, 2020 08:29
@@ -7,8 +7,9 @@ python:
# - "3.5" # ecdsa tests fail in 3.5.
- "3.6"
- &latest_py3 "3.7"
- "3.8"
Copy link
Contributor

Choose a reason for hiding this comment

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

Are you aware that now latest_py3 no longer points to the latest Python 3?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah, I did that on purpose. python3.8 is so new that I didn't trust twine and the deployment steps to work in that environment. My not-great metric is that py3.8 required code updates for JP itself, and we're not even that big of a library, so I opted to hold that back for stability purposes.

We'll update that eventually, though. Thanks for the heads-up.

Copy link
Contributor

Choose a reason for hiding this comment

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

I think it would be easy to change the variable name latest_py3 to something less mis-leading in the mean time. Just an idea.

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.

2 participants