name conflict with conda-forge julia package

[kiwi0fruit]

pyjulia is not on conda-forge but is on pypi. I guess it may be because of the unresolved issues with Anaconda support in pyjulia. But regardless of it there is already a julia package in conda-forge that is Julia language itself.

The simple work around when finally adding pyjulia to conda-forge can be having different name for conda and pip: pyjulia conda package but julia egg. But that's rather ugly solution... Something would have to be done about it.

[tkf]

While it is ideal to have Conda and PyPI packages to have the same name, it is not always possible. I don't think this is a problem since this is fundamentally impossible to guarantee: pypi.org is a Python Package Index and anaconda.org distributes generic software packages.

Having said that, we can register a package pyjulia in PyPI like pytest project registers py.test to provide a helpful message when you try to install py.test instead of pytest. Likewise, pip install pyjulia can provide a message like "please use julia, not pyjulia, for installation." This would mitigate some confusions.

[sylvaticus]

Hello, I am noticing that this package has several names.. pyjulia, PyJulia, julia... I think there should be more consistency, and if I can toss my two cents, julia is too generic and could lead to conflicts (yep.. and indeed I arrived here on this issue).. I think the module name should really be pyjulia (or PyJulia, I'm not aware of Python module conventions..)