disutils, project structure developing - n00b question

2009-10-29 Thread Wells
So I have my project partitioned like so: ./setup.py ./pymlb/ ./pymlb/fetcher.py ./demos ./demos/demo.py In demo.py I have: from pymlb import fetcher However, it fails b/c pymlb is up a folder. It's also NOT installed as a module in my module directory because it's a development effort and I

Re: disutils, project structure developing - n00b question

2009-10-29 Thread Simon Forman
On Thu, Oct 29, 2009 at 2:42 PM, Wells we...@submute.net wrote: So I have my project partitioned like so: ./setup.py ./pymlb/ ./pymlb/fetcher.py ./demos ./demos/demo.py In demo.py I have: from pymlb import fetcher However, it fails b/c pymlb is up a folder. It's also NOT installed as

Re: disutils, project structure developing - n00b question

2009-10-29 Thread Simon Forman
On Thu, Oct 29, 2009 at 3:45 PM, Simon Forman sajmik...@gmail.com wrote: In order for from pymlb import fetcher no work you must make the s/no/to/ D'oh! -- http://mail.python.org/mailman/listinfo/python-list

Re: disutils, project structure developing - n00b question

2009-10-29 Thread Lie Ryan
Simon Forman wrote: In order for from pymlb import fetcher no work you must make the './pymlb' directory into a package by adding a file called __init__.py (it can be empty.) Then make sure the top directory (i.e. '.' in your example) is in the python PATH. There are a couple of ways to do