@nirum changed the folder structure of the dev branch, putting all the source code in pyret/pyret. This is fine, but it means that we have to have the top-level folder itself on our PYTHONPATH, rather than the folder in which the repo lives. E.g., I have to include /usr/local/lib/python3.4/site-packages/pyret on my PYTHONPATH, rather than just /usr/local/lib/python3.4/site-pacakges.
We should include an __init__.py file inside the top-level directory, which can just do from pyret import *. Thoughts?
@nirum changed the folder structure of the
dev
branch, putting all the source code inpyret/pyret
. This is fine, but it means that we have to have the top-level folder itself on ourPYTHONPATH
, rather than the folder in which the repo lives. E.g., I have to include/usr/local/lib/python3.4/site-packages/pyret
on myPYTHONPATH
, rather than just/usr/local/lib/python3.4/site-pacakges
.We should include an
__init__.py
file inside the top-level directory, which can just dofrom pyret import *
. Thoughts?