search

enthought / ensemble

High-level widgets for building Python applications
Other
4 stars 7 forks source link

test-new-cleaned-up-enable-setup #38

Closed itziakos closed 9 years ago

noraderam commented 9 years ago

Well, shucks. I think it would be worthwhile to try to figure out what pip is doing. I'd like to know why it's running setup.py in enable at that point when it hasn't tried installing the other dev_requirements.txt packages yet--it looks like it's just collecting eggs initially.

itziakos commented 9 years ago

My current hypothesis is that the problem is still with enable.

itziakos commented 9 years ago

It looks that pip collects all the top level requirements and downloads them, the it tries to find their runtime and setup dependencies by importing the setup.py for each downloaded dependency. The requirements are stored in a dictionary with names as theirs keys so ordering is random. When it reaches enable it tries to execute enable's setup.py but fails because the __version__ is imported from kiva._version but kiva/__init__.py ends up at some point importing numpy and traits.

jwiggins commented 9 years ago

So, we should probably not get __version__ from kiva._version then. Note that we discussed this in enthought/enable#166. I believe Corran's alternate suggestion there was to write a _version.py into both kiva and enable packages.

itziakos commented 9 years ago

I have update the enable PR to save two copies of the file one inside enable and one inside kiva, this should allow setup to finish importing

jwiggins commented 9 years ago

It makes it to tests now then fails. :tired_face:

itziakos commented 9 years ago

i think we can merge this to the travis-failure branch now. The test failures are probably not related to the package builds anymore.

jwiggins commented 9 years ago

Agreed.