-
Notifications
You must be signed in to change notification settings - Fork 153
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
UnicodeEncodeError when installing Wheel 0.36.1 as numpy requirement #389
Comments
All of those tracebacks come from pip, not wheel. Can we agree on that? Can you give me instructions to reproduce the problem? |
From a glance this looks like you have an environment that uses |
Yeah, so reading through #331 again I remember what that was all about. The automated releases are currently made using Python 3.8 which uses the new tar format. Does this mean we can never have non-ASCII file names in sdists? |
Can you tell me why |
They were built using Travis instead of Github Actions. |
I can make GH Actions build it with py3.7 but this problem is going to come around again eventually unless I remove that particular file from the sdist. What I would like to figure out is whether any sdist should be allowed to package non-ASCII files or not. |
For what it's worth PEP 517 states that "The generated tarball should use the modern POSIX.1-2001 pax tar format, which specifies UTF-8 based file names". So in theory yes, non-ASCII filenames are allowed. But it may not be the case that tools are following that standard yet. |
That leaves the question, is wheel doing something wrong? What are the tools supposed to do when the filesystem encoding is set to |
Ah, right - that's probably a question for the packaging discourse. My instinct is to say you should report an error that suggests the user needs to use a filesystem that supports the files in the sdist, but that's very much just a knee-jerk reaction, and only a personal view. |
@agronholm Should I keep this open for you to continue discussion or should I close this? |
Maybe keep this open until a course of action can be figured out. I'm not sure what to do here. The problem does not lie with wheel or even the way it's packaged, but that facts that 1) you're trying to unpack a non-ascii file name in an environment that, for some reason, only allows ASCII file names, 2) are not using the wheel of There are two obvious workarounds:
I'm hoping other people will chime in here. |
It's not me, it's I'll keep this open, hope you'll find the right answer for this question. |
Is there a problem with |
You are correct - |
NumPy dev here. I am not sure I follow the discussion. Is something actionable NumPy could do to help out here? 1.20 will be released in January ... |
Is there a reason your build process installs the build tools from source instead of using wheels? |
@mattip Sorry for some confusion - finally I understood that reason was @agronholm This is deepvariant bash script and it had reason for doing that for Ubuntu 14.04:
Deepvariant still using 16.04 to build and don't test their scripts for 18.04, there for their code tries to build from source all non-16.04 numpy installations. According to comments in my issue - they will update to 18.04 and (I assume) stop using source in favor of wheels. |
Sounds like you can close the issue? |
For me - yes. I thought you need it for discussion. |
The right place to have that discussion would be https://discuss.python.org/c/packaging/14. |
Hello, looks like #331 strikes back in some situations.
After we tried to update our deepvariant installation to new release we encountered pretty much same problem (link to code line):
Interesting fact - we can install
wheel
with pip and we're doing it priornumpy
install - everything ok:The only difference I've found is using
.tar.gz
in a failed attempt.My manual debug result is that installing newer versions of
numpy
became successful at1.19.3
:And exactly
numpy 1.19.3
set upper versions forwheel
dependency: Changelog, PR.Can you give me any advice? Looks like there are several problems, one of them is using Python 3.6 (I can install
numpy=1.18.5
on Python 3.7 with same method).The text was updated successfully, but these errors were encountered: