The eregs.py module wasn't included in the setup script, which meant that the
eregs command would not work unless run in the same directory. Further,
eregs.py referred to manage.py, which is too generically named to be included
in a package. Instead, move its logic into a module deeper in the app and
reference that module in both the manage.py and eregs command. This also
allows us to remove the eregs.py script.
Coverage decreased (-0.2%) to 91.759% when pulling a875bada5239ec7d0188714089da8428f700e3b9 on cmc333333:packaging-issues into 6faf9e75c2ed620cf7681922fcb672b518681d25 on eregs:master.
Coverage decreased (-0.2%) to 91.724% when pulling 1fc5eb78b2227ffc4c3dcdc89ce8ec66b04d3e43 on cmc333333:packaging-issues into b2a4c0761d8a76b0eb10f7425a467ad4becc8865 on eregs:master.
The eregs.py module wasn't included in the setup script, which meant that the
eregs
command would not work unless run in the same directory. Further, eregs.py referred to manage.py, which is too generically named to be included in a package. Instead, move its logic into a module deeper in the app and reference that module in both the manage.py anderegs
command. This also allows us to remove the eregs.py script.