Skip to content

import clr clashes with pythonnet package #1

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

Closed
den-run-ai opened this issue Feb 17, 2017 · 17 comments
Closed

import clr clashes with pythonnet package #1

den-run-ai opened this issue Feb 17, 2017 · 17 comments

Comments

@den-run-ai
Copy link

pythonnet/pythonnet#388

pythonnet has been available since 2003.

@vmuriart
Copy link

The name clashes with IronPython which uses import clr as its import hook.

@lmittmann
Copy link
Owner

I noticed the package name conflict after publishing. Does this affect your build or installation process?

My understanding of pythonnet/pythonnet#388 is, that pip install clr was executed instead of pip install pythonnet, right?

@den-run-ai
Copy link
Author

This does not affect our build or installation, but new pythonnet users will keep bumping into this issue by incorrectly assuming that pip install clr is necessary before import clr.

Would you mind renaming your package before it is too late? I see that it is only about one month old?

@lmittmann
Copy link
Owner

It is actually really hard to find a good 3 letter name. How about a little compromise:

  • We update the pythonnet/README.md to show some installation instructions, since people who wrongly install clr instead of pythonnet just got a different error, before I published my package.
  • I will update the AttributeError to show a more explanatory error message, pointing to pythonnet

@vmuriart
Copy link

The problem is for users that install both like the original issue that made us detect it.

@lmittmann
Copy link
Owner

I thought the original issue was that a new pythonnet user installed the wrong package.

@den-run-ai
Copy link
Author

den-run-ai commented Feb 18, 2017 via email

@lmittmann
Copy link
Owner

System is a toplevel module of pythonnet?

@den-run-ai
Copy link
Author

den-run-ai commented Feb 18, 2017 via email

@lmittmann
Copy link
Owner

The AttributeError caused by clr.AddReference can be easily detected. Detecting the import System error might be more complicated. I will have a look on how this "hook up" is done, it might be also catchable.

@vmuriart
Copy link

vmuriart commented Feb 18, 2017 via email

@vmuriart
Copy link

vmuriart commented Feb 18, 2017 via email

@filmor
Copy link

filmor commented Mar 23, 2017

@lmittmann Please take a stance on this now.

Are you going to rename your library? You are clashing with both Python.NET and IronPython and are causing confusion for people using pip directly. If not, please at least say so now and we will put the corresponding information into our Readme and entry page.

Please don't try to hack around this by capturing import System or clr.AddReference.

@lmittmann
Copy link
Owner

I will rename the library later today. I am not sure about the best way to transfer ownership of a pypi package though. Any ideas @denfromufa @vmuriart @filmor?

@filmor
Copy link

filmor commented Mar 28, 2017

Does this link work? https://pypi.python.org/pypi?:action=role_form&package_name=clr

You can add one of us as owners and we will handle it from there.

Many thanks for the renaming :)

@lmittmann
Copy link
Owner

That worked, you should have access now.

@koubaa
Copy link

koubaa commented Oct 13, 2021

@lmittmann could you please unlist clr from pypi?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants