Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is more of an RFC than a Pull Request: only some versions work here. I'm not sure if this is the correct approach. I'll finish this if you think this is the way forward.
Different Python versions need different OpenSSL versions. This PR is an example of adding OpenSSL 1.0.x, required for 3.4. It builds, I can use pip, but I had to skip the certificate check for pypi.python.org. It's not great, but if an app is stuck on Python 3.4 then it's still better than nothing.
Is the approach of importing old openssl versions from different branches of nixpkgs sensible? Or would it make more sense to either copy the openssl package, or create a "nixpkgs-openssl" repo?
I believe this could solve #23 - Python requires ssl to build pip.
Before:
After: