-
Notifications
You must be signed in to change notification settings - Fork 398
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
TypeError: Unicode-objects must be encoded before hashing on node-gyp (Python 3.6.7) #743
Comments
I ended up setting another version on travis' |
the version that use it here is for legacy python version, i guest 2.7.* . so i think will be better to update node-gyp version use it here to be able for as to install recent python version. |
Had the same issue, i have solved it by setting a PYTHON env variable to |
Had the same issue, I found that the node-gyp version in |
This comment has been minimized.
This comment has been minimized.
Looked, this isn't related to the node-gyp version in the package.json, which is a dev dep (not install dep), so the fact that it is v3.x isn't related.
I help maintain node-gyp, I'll see if I can track down if this is an issue with upstream. |
Looks like this is a node-gyp bug, fixed in nodejs/node-gyp#1925, released in v5.0.6. Use a version of npm that includes that version. I just did an
Did an I believe that should close this issue, its not an issue with this project, and its fixed upstream, and released in npm. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Environment Information
Steps to Reproduce
Try to build the following Dockefile:
node-rdkafka Configuration Settings
Not needed
Additional context
Hello.
last week, I had a surprise when deploying an app, our build is throwing:
We use travis and it's python version is
3.6.7
, I've tested other version and it worked fine on all of them. Which is strange, as3.6.*
is technically supported by node-gyp.May someone give some light on what can I do? Forcing the use of another python version is something I'll have to explain to our ops team, so I would rather leave it to a last resort
The text was updated successfully, but these errors were encountered: