TG2 requirements vs. tg.devtools requirements
Diez B. Roggisch
I just noticed that tg.devtools contains these requirements:
Pylons>=0.9.7beta5
Catwalk
TurboGears2>=2.0b3
sprox
BeautifulSoup
Beaker>=1.1.3
FormEncode>=1.2
Paste>=1.7
PEAK-Rules
repoze.tm2
repoze.what >= 1.0.2
repoze.who>=1.0.8
Routes>=1.10.2
sqlalchemy-migrate>=0.4.4
SQLAlchemy>=0.5.0beta3
SQLAlchemy>=0.5beta3
ToscaWidgets>=0.9
TurboJson
tw.forms>=0.9.2
WebTest
WebOb
wsgiref==0.1.2
zope.sqlalchemy
Whereas TG2 only has these:
Babel
decorator
Genshi
Pylons>=0.9.7rc3
WebOb >= 0.9.5
WebFlash >= 0.1a7
ToscaWidgets>=0.9
repoze.who >= 1.0.10dev-r3295
repoze.what.plugins.sql > 1.0a2
SQLAlchemy>=0.5beta3
So I ran into troubles with freshly setup applications I deployed
through "python setup.py develop", as these didn't fetch absolutely necessary
packages.
My question is then - shouldn't these things be part of the TG2 dependencies?
If not, do we "aggressively" enough communicate that the user is required to
install these things himselve?
I think it would be disappointing to newbies if deploying their quickstarted
app would fail because of that.
Diez
Mark Ramm
quickstarted app requirements list. Then they can remove the ones
they don't use, and the tg.core requirements can be kept to a minimum,
and those who don't care will be able to get what they want without
problems.
--Mark
Mark Ramm-Christensen
email: mark at compoundthinking dot com
blog: www.compoundthinking.com/blog
Derick Eisenhardt
> We should probably add all of the tg.devtools requirements to the
> quickstarted app requirements list. Then they can remove the ones
> they don't use, and the tg.core requirements can be kept to a minimum,
> and those who don't care will be able to get what they want without
> problems.
>
> --Mark
select when they are installing (basically what is already happening
with turbogears vs tg.devtools, but more easy to understand for a new
user), and then simply state that to use QuickStart, you must use
tg.full
Gustavo Narea
> Why not just have both a tg.core and a tg.full package the user can
> select when they are installing (basically what is already happening
> with turbogears vs tg.devtools, but more easy to understand for a new
> user), and then simply state that to use QuickStart, you must use
> tg.full
+1
--
Gustavo Narea <http://gustavonarea.net/>.
Get rid of unethical constraints! Get freedomware:
http://www.getgnulinux.org/
Diez B. Roggisch
> We should probably add all of the tg.devtools requirements to the
> quickstarted app requirements list. Then they can remove the ones
> they don't use, and the tg.core requirements can be kept to a minimum,
> and those who don't care will be able to get what they want without
> problems.
Sounds good to me - especially since these requirements might change due to
users-choices of e.g. templating engine or some such.
Diez
Mark Ramm
>
> On Thursday January 29, 2009 17:56:37 Derick Eisenhardt wrote:
>> Why not just have both a tg.core and a tg.full package the user can
>> select when they are installing (basically what is already happening
>> with turbogears vs tg.devtools, but more easy to understand for a new
>> user), and then simply state that to use QuickStart, you must use
>> tg.full
>
> +1
I'm hesistant to change package names at this point, but tg.full could
be created as a new package that does this if tg.devtools is way to
hard to undersand.
TurboGears2 is the server itself. tg.devtools is the full environment
with all the tools that you want to actualy develop tg applications.
And the quickstarted template should include all the dependencies
needed for that app in it's own setup.py.
I think this make sense, but we could pull some requirements out of
devtools and put them in a new tg.core package, but IMHO this just
complicates things. And moving the developer tools (quickstart,
paster commands, etc) into tg.full seems a bit strange too, but if
it's just renaming tg.devtools to tg.full it's easy, and now's the
time to do it if that's what people want.
--Mark
Jorge Vargas
In fact I have seen many many people complain as to why easy_install
-i <url> turbogears2 doesn't works. So I don't find that a bad
request. I think "core" is a bad name, as it implies a basic set of
tools that don't work out of the box, most "core" package are simply
the api, I think "tg2" is more like it.
Looking at the bigger picture we now have.
TurboGears2 (package)
tg.devtools
tgext.*
apps
now we have a problem here. if we move all "optional" dependencies to
the apps, then that means neither TurboGears2 and tg.devtools will not
be usable out of the box, so we need to keep genshi and SA as deps for
TurboGears2.
tg.devtools should just bring in what it needs, now some of that
things there now should really go to quickstart but that is something
I don't like. As it will require testing quickstart even more.
Jorge Vargas
hi Diez, I just made a ticket and assigned it to myself to see if we
can sort this out. I think over the time our deps have moved a lot and
we need to rebase :) #2176