Opened 15 years ago
Last modified 14 years ago
#98 closed enhancement (FIXED)
Create "setup" submodule
| Reported by: | Elrond | Owned by: | Elrond |
|---|---|---|---|
| Priority: | minor | Milestone: | 0.0.3 |
| Component: | programming | Keywords: | |
| Cc: | Parent Tickets: |
Description
The idea is to create a mediagoblin.setup submodule. This should contain code to get the app running.
Things to move there (as examples):
- celery_setup/ -> setup/celery/
- util.get_jinja_loader (and friends?)
- setup_beaker, if/when it's coming
- Maybe code from MediaGoblinApp.**init**()
This issue is to track this idea.
Change History (5)
comment:1 by , 15 years ago
comment:2 by , 15 years ago
Okay. The current "solution" is to call the thing "init", not "setup". Well.
Anyway: I have the dev/init branch up, which moves celery and get_jinja_loader into a new mediagoblin.init submodule.
comment:3 by , 15 years ago
| Milestone: | → 0.0.3 |
|---|---|
| Owner: | set to |
| Status: | New → Closed |
Merged. Thanks Elrond!
comment:4 by , 14 years ago
The original url for this bug was http://bugs.foocorp.net/issues/385 .
Relations:
#68: follows
comment:5 by , 14 years ago
| Type: | defect → enhancement |
|---|
Note:
See TracTickets
for help on using tickets.
I was just playing with it. It gives a major headache up front: "mkdir setup && touch setup/__init__.py" and the tests fail strangely. The test system thinks, that setup is a funcion on the mediagoblin module to set it up for testing. I have a very bad workaround, which I hate. So I'm looking for suggestions.