import error with 0.1.0

[huwdjones]

Hi there,

Linux 3.13.0-29-generic #53-Ubuntu SMP Wed Jun 4 21:00:20 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Python 2.7.9

pip install colour
Collecting colour
Using cached colour-0.1.0.tar.gz
Installed /tmp/pip-build-jSjeRq/colour/.eggs/d2to1-0.2.11-py2.7.egg
[d2to1] running patched manifest_maker command with extra_files support
Installing collected packages: colour
Running setup.py install for colour
[d2to1] running patched manifest_maker command with extra_files support
Successfully installed colour-0.1.0

from colour import Color
Traceback (most recent call last):
File "", line 1, in
ImportError: No module named colour

[vaab]

Many thanks for your feedback. Can you tell me what's your setuptools version and pip version ? I ll investigate this myself as soon as I reach a valid connection.

[huwdjones]

Hi there,

Many thanks for the response:

~$ pip —version
pip 6.0.8 from /python-2.7.9/lib/python2.7/site-packages (python 2.7)

Python 2.7.9 (default, Mar 28 2015, 00:24:59)
[GCC 4.8.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.

import setuptools
setuptools.version.version
’12.0.5'

On 28 Mar 2015, at 09:05, Valentin Lab notifications@github.com wrote:

Many thanks for your feedback. Can you tell me what's your setuptools version and pip version ? I ll investigate this myself as soon as I reach a valid connection.

—
Reply to this email directly or view it on GitHub #15 (comment).

[aculich]

I can confirm the problem as well with python 2 & 3:

oski@BCE:~$ pip --version
pip 1.5.6 from /home/oski/anaconda/lib/python2.7/site-packages (python 2.7)
oski@BCE:~$ python
Python 2.7.8 |Anaconda 2.1.0 (64-bit)| (default, Aug 21 2014, 18:22:21) 
[GCC 4.4.7 20120313 (Red Hat 4.4.7-1)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
Anaconda is brought to you by Continuum Analytics.
Please check out: http://continuum.io/thanks and https://binstar.org
>>> import setuptools
>>> setuptools.version.__version__
'5.8'
>>> 
oski@BCE:~$ pip3 --version
pip 1.5.4 from /usr/lib/python3/dist-packages (python 3.4)
oski@BCE:~$ python3
Python 3.4.0 (default, Apr 11 2014, 13:05:11) 
[GCC 4.8.2] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import setuptools
>>> setuptools.version.__version__
'3.3'

[vaab]

This was due to a missing module = colour in the setup.cfg. I was more puzzled that the extensive packaging tests did not catch this one, but after a short reflection, this issue revealed flaws in the way the import colour was tested.

Many thanks to all reporters.

Pypi python package 0.1.1 was released with the fix (I also deleted the broken release 0.1.0)

[segalinc]

Same problem in colour-0.1.5

[vaab]

@cristinasegalin hmm, that's very strange. There are many users of this library, this is why when the first problem occurred (right after a release in 2015) it was detected right away and it was corrected in the same go, with additional tests. If this happens now, it could then come from a new combination of tools or you have a local problem, so...

May I ask you your system ? distrib ? python version ? pip version ? setuptools version ?
I can't reproduce your problem (tried with a ubuntu 14.04, with pip 1.5.4, setuptools ?)

You can get these with:

python --version
lsb_release -a
pip --version
python -c 'import setuptools; print(setuptools.version.__version__)'

Many thanks for your report

[segalinc]

I figured out that I had another python package that has the same name of this on and was imported by default. Removing that solved the problem but it's weird that there are two packages with the same name. Thanks Cristina

…

Sent from my OnePlus

On Thu, Jun 28, 2018, 02:31 Valentin Lab ***@***.***> wrote: @cristinasegalin <https://github.com/cristinasegalin> hmm, that's very strange. There are many users of this library, this is why when the first problem occurred (right after a release in 2015) it was detected right away and it was corrected in the same go, with additional tests. If this happens now, it could then come from a new combination of tools or you have a local problem, so... May I ask you your system ? distrib ? python version ? pip version ? setuptools version ? I can't reproduce your problem (tried with a ubuntu 14.04, with pip 1.5.4, setuptools ?) You can get these with: python --version lsb_release -a pip --version python -c 'import setuptools; print(setuptools.version.__version__)' Many thanks for your report — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#15 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AI63khhvE3m-EZJC9_5Ms7l9wQnCqdDuks5uBKJYgaJpZM4D16J-> .

[scrouthtv]

How did you remove the second package (I'm experiencing the same error, and cant find a solution)? @cristinasegalin

Thanks

[segalinc]

I uninstall it and installed the correct one Cristina

…

Sent from my OnePlus

On Thu, Nov 8, 2018, 13:17 scrouthtv ***@***.*** wrote: How did you remove the second package (I'm experiencing the same error, and cant find a solution)? @cristinasegalin <https://github.com/cristinasegalin> Thanks — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#15 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AI63kq01pQKynpHlZ8kMFaOnQaFaYl-Fks5utJ99gaJpZM4D16J-> .

[unaimillan]

There are two different packages: "color" and "colour"

[scrouthtv]

So my problem was that I had multiple python versions installed

Type something like where Python or which Python and uninstall all besides one (or directly call the one you want)

Because my problem was that I ran pip on the one python version but ran python itself from the other one