setup.py not installing all dependencies

[renanrodrigo]

Started a new environment and ran python setup.py install for python-openflow, kytos-utils and kytos, and no errors ocurred. However, when I ran kytosd -f, all I've got was:

Traceback (most recent call last):
  File "/home/renan/testes/venv/bin/kytosd", line 3, in <module>
    import daemon
ModuleNotFoundError: No module named 'daemon'

[diraol]

May be we could use this setuptools function to achieve our needs:
https://github.com/pypa/setuptools/blob/e65c45538fab94008b8066edd134725be8f9c400/bootstrap.py#L75

[abaruchi]

@renanrodrigo I run some tests to reproduce the error. I think that the procedure in kytos tutorial may be wrong. Can you please try the following:

for project in python-openflow kytos-utils kytos-napps kytos; do 
cd $project 
pip3.6 install -r requirements.txt -r requirements-dev.txt -r requirements-docs.txt >/tmp/requirements.$project.log 2>&1 
python3.6 setup.py develop >/tmp/setup.$project.log 2>&1 
cd - 
done

Note that s/pip/pip3.6/ and s/python/python3.6/ inside the for looping.

[renanrodrigo]

@abaruchi I know it works that way, I'm doing this for a while. But pythons setup.py install should install all dependencies. @macartur posted a bug in setuptools that may be causing this.

[macartur]

This is the issue: pypa/setuptools#456.

[diraol]

@renanrodrigo and @macartur dos this issue affects both install mode and develop mode? or just install?
[I'm working on a solution for us]

[diraol]

Btw, this comment seems to be the real issue for us:
pypa/setuptools#456 (comment)

[renanrodrigo]

@diraol develop mode works fine.

[diraol]

Ok, then the problem is the one from this comment:
pypa/setuptools#456 (comment)

If on our Install class (inside setup.py) we call the self.do_egg_install() instead of super().run(), then almost everything works fine.
I mean, the main problem (of installing dependencies) is solved.

The only remaining problem is that, despite the fact that jinja2 is installed by the setup script, it is not available to the setup script itself [the modules available on the Path are not "reloaded"], so we still have to deal with the Jinja2 import error.

[cemsbr]

#375 also solves this problem.

[diraol]

@cemsbr please, reference the issue on the commit! =)

[beraldoleal]

@diraol @cemsbr #375 was merged but without reference to here, right ? Can we close this ?

[diraol]

Yes we can @beraldoleal !