Re: webcheck commit: r468 - in webcheck: . webcheck

[Devin Bayer <l [at] t-0.be>]

On 2011-11-18, at 19:42, Arthur de Jong wrote:

> I have a few questions about the changes. Why is there a separate script
> needed for setuptools and for development? Wouldn't it be much easier to
> have one script to avoid things working in development but not with the
> script installed? Some applications seem to use the scripts parameter of
> setup() for this.

I did this first, but kept the current setup for a couple practical reasons:

1. you can't rename the script, and it should be "webcheck", which conflicts 
with the package name. So it would need to be placed in subdirectory

2. scripts are installed under EGG-INFO/scripts and are not importable. So 
nobody could do:

from webcheck.cmd import Crawler, main
main(Crawler())

and design-wise, cmd.py seemed like a good place to put the profiling code.

Just for now, I renamed it to run.py, since pdb in python 2.7 does "import cmd" 
and it first looks for the cmd.py in the current directory.

> Also, I think setup.py should import as much information from the
> webcheck package as possible (currently homepage and version) to avoid
> stuff getting out of sync (or is there any easier way to do this?).

Good idea - I changed that.

I had to remove the indirect dependency of webcheck/__init__.py on sqlalchemy 
because otherwise you can't run setup.py without sqlalchemy installed. And 
normally setup.py installs the dependencies for you.

~ Devin
-- 
To unsubscribe send an email to
webcheck-users-unsubscribe@lists.arthurdejong.org or see
http://lists.arthurdejong.org/webcheck-users/