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
sqlalchemy cannot be deployed from Linux #1356
Comments
Can you clarify what specifically isn't being handled properly? Here's what I tried, which is the behavior I'd expect:
Are you seeing different behavior? |
I’ll see if I can put a simple replication together tomorrow to demonstrate what is happening. |
I'm out of town right now. I have a similar example that doesn't work for me. I'll test this when I'm home. |
Oh interesting. I added an integration test that packages sqlalchemy, and it fails on travis: https://travis-ci.org/aws/chalice/jobs/655456628. I was testing on an ubuntu box through VMWare on my Mac, but let me spin up an EC2 ubuntu instance and see if I can repro it there. As far as that line about normalization goes, I'm hesitant to change it. That's taken directly from pep 503 (https://www.python.org/dev/peps/pep-0503/) and it's also what pip uses: https://github.com/pypa/pip/blob/master/src/pip/_vendor/packaging/utils.py#L17 But let me dig into this more and see what I can find. |
Confirmed on an ec2 ubuntu instance. On reading the myriad of PEPs, it does appear we're doing this wrong: PEP 426
PEP 508
So while our normalization is correct, we should also be doing this normalization on directory names as well when checking for a match. I'll get a fix up for this. |
Ended up fixing the bug in the linked PR that added an integ test for packaging sqlalchemy. Thanks for reporting! |
Packages with uppercase letters in their name, such as SQLAlchemy are not handled properly on case-sensitive file systems. The directory contained in the package has uppercase letters, but the package name is normalized to make them lowercase. Getting rid of the lower() fixes the issue.
The text was updated successfully, but these errors were encountered: