[TurboGears] #2403: Provide a TGCommand base class within TurboGears 2.x core
TurboGears
------------------------+---------------------------------------------------
Reporter: mcfletch | Owner:
Type: defect | Status: new
Priority: normal | Milestone: __unclassified__
Component: TurboGears | Version: 2.0.3
Severity: normal | Keywords:
------------------------+---------------------------------------------------
I've got a recipe for setting up a TurboGears CLI command. It sets up
tg.config, SQLAlchemy, and if lang is defined in the config, attempts to
set up i18n (thanks to tmu).
This *seems* like it is functionality that should be available by default
from TurboGears. There's enough
black-magic stuff necessary that it really seems it shouldn't be
something we're asking the (new) user to know how to do.
--
Ticket URL: <http://trac.turbogears.org/ticket/2403>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
TurboGears
------------------------+---------------------------------------------------
Reporter: mcfletch | Owner:
Type: defect | Status: new
Component: TurboGears | Version: 2.0.3
Severity: normal | Resolution:
Keywords: |
------------------------+---------------------------------------------------
Changes (by jorge.vargas):
* milestone: __unclassified__ => 2.1
Comment:
+1 this must go into 2.1. I have about 3 half done implementations on
several projects.
--
Ticket URL: <http://trac.turbogears.org/ticket/2403#comment:1>
TurboGears
------------------------+---------------------------------------------------
Reporter: mcfletch | Owner:
Type: defect | Status: new
Component: TurboGears | Version: 2.0.3
Severity: normal | Resolution:
Keywords: |
------------------------+---------------------------------------------------
* milestone: 2.1 => 2.1b2
--
Ticket URL: <http://trac.turbogears.org/ticket/2403#comment:2>
TurboGears
------------------------+---------------------------------------------------
Reporter: mcfletch | Owner:
Type: defect | Status: new
Component: TurboGears | Version: 2.0.3
Severity: normal | Resolution:
Keywords: |
------------------------+---------------------------------------------------
Comment (by percious):
Can you provide an rst file explaining usage? Do we have to put an entry
in setup.py to use this?
--
Ticket URL: <http://trac.turbogears.org/ticket/2403#comment:3>
TurboGears
------------------------+---------------------------------------------------
Reporter: mcfletch | Owner:
Priority: normal | Milestone: 2.1b2
Component: TurboGears | Version: 2.0.3
Severity: normal | Resolution: fixed
Keywords: |
------------------------+---------------------------------------------------
Changes (by mcfletch):
* status: new => closed
* resolution: => fixed
Comment:
Okay, there is now a tgext.command extension which can be installed. The
README.txt in this package is basically the original blog post updated for
the new packaging. Still needs tests and the like.
--
Ticket URL: <http://trac.turbogears.org/ticket/2403#comment:5>
TurboGears
------------------------+---------------------------------------------------
Reporter: mcfletch | Owner:
Type: defect | Status: new
Component: TurboGears | Version: 2.0.3
Severity: normal | Resolution:
Keywords: |
------------------------+---------------------------------------------------
There is a documented (short) description in the 2.1 documentation which
describes a much smaller approach to this. The TGCommand module doesn't
currently have any test-cases. Percious suggests that we not include
TGCommand without tests.
TGCommand is basically a real-world example of what is needed to prevent
cron-bombing and otherwise creating an official command, but there's some
question as to whether people really *want* that, or just want a simple
couple-of-line script to integrate into their general code-bases.
Suggestion is to make tgcommand into tgext.tgcommand (i.e. an extension
module).
--
Ticket URL: <http://trac.turbogears.org/ticket/2403#comment:4>