-
-
Notifications
You must be signed in to change notification settings - Fork 105
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
Remove conda-forge branding #332
base: main
Are you sure you want to change the base?
Conversation
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipe:
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( I do have some suggestions for making it better though... For recipe:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
-1 on this. I know that there are some downstream software which use sys.version
to detect a conda
installed python.
Patching I really prefer this approach over making the regex more tolerant. |
Playing devil's advocate here but given
Isn't this the thing we should fix here first. Then branding or no branding is untangled from your issue. |
Agree with Ray 🙂 |
@mingwandroid @jakirkham Quite the contrary. The conda package for xeus-python is dynamically linked with libpython.so (and we prefer it so), but in the case of a wheel, some distributions of Python don't come with a shared object - and we must link statically. This is how several other packages operate to distribute PyPI wheels. My point is that conda-forge's Python brands the Python interpreter's banner by changing the |
I must not have made myself clear here. That branding works with the dylib but not the static archive seems to me a serious bug and entirely orthogonal to whether we should brand or not. Now if everyone was in agreement to ditch branding then OK, let's do that, delete all the changes and move on. Bur that's not the situation and if we did do that we'd need a deprecation cycle for it. I'm happy to look into using the anaconda branding code for conda forge, which I believe works in both cases. In my opinion this is the best path forward. |
Actually, there is no "bug", since the manylinux wheel is linked against the
I think we can start with #331 which makes the regex compatible with both the branding and the absence thereof, and discuss the complete removal at greater length. |
What manylinux libpython.a do you mean? AFAIK this doesn't exist. You are linking against some random libpython the distribution you ran your build upon happened to have installed I guess? I don't want to spend time taking about random software. |
And is it true that you are using this random python but with a python syslib from conda-forge? |
No, we are linking against the right libpython.a, but preventing the manylinux docker file from deleting it. This is something several other packages are doing to embed python, such as Panda3D. |
9418f97
to
1b98cdb
Compare
Alternative to #331.
I think that this fix is actually preferable than the current branding solution.