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

Fix TypeError on Python 2.7 and git-lfs issue #361

Merged
merged 5 commits into from
Sep 3, 2020

Conversation

mcdeck
Copy link
Contributor

@mcdeck mcdeck commented Sep 2, 2020

I bumped into a couple of issues using the latest version of zest.releaser under python 2.7, while trying to release code that uses git and git-lfs.

This PR address both these issues.

mcdeck and others added 3 commits September 2, 2020 21:05
Use p.communicate() instead of of .read() on stderr/stdout directly as that seems to cause a deadlock with large outputs (or at least that is what I think happens).
Before this change zest.releaser would get stuck doing a clone of the repository, if the repository uses git-lfs.
This fixes ``TypeError: environment can only contain strings`` emitted by subprocess.
Subprocess seems to dislike unicode objects in os.environ/env that is passed. This assures a plain string is used instead.
@mcdeck mcdeck changed the title Patch 1 Fix TypeError on Python 2.7 and git-lfs issue Sep 2, 2020
Copy link
Member

@mauritsvanrees mauritsvanrees left a comment

Choose a reason for hiding this comment

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

Tests are green. I did a test release with your code, and it works. Looks cleaner now.
Changelog entry is missing, but I will add something after merge.
Thanks!

@mauritsvanrees mauritsvanrees merged commit 77760d0 into zestsoftware:master Sep 3, 2020
@mauritsvanrees
Copy link
Member

I have released 6.22.0 with your fixes. Thanks again!

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.

3 participants