What is TurboGears?
-------------------
TurboGears is a popular rapid web development megaframework, built
from a number of great Python projects and with a bunch of high-level
features built within the TurboGears project.
TurboGears is a front-to-back framework helping you on the front end
(the MochiKit JavaScript library), templates for the view (Kid), the
controller in the middle (based on CherryPy) and an object-relational
mapper for your database (SQLObject).
To that mix of projects, TG adds:
* Widgets: Python objects that bundle JavaScript, CSS, HTML and
server-side validation to make form creation and powerful JavaScript
features easy.
* Internationalization: Tools and APIs to help you localize the
strings in your application.
* Identity: Authentication and authorization made easy
* Toolbox: a web-based GUI to help you work on your project (write
your own as well!) Includes CatWalk to help you work with your
database data and Model Designer to help you design your database
graphically.
* tg-admin: command line tool that gives you a quick start to your
project, helps you set up your database and more!
* Easy Ajax: flexible template support allows you to choose a
different template engine (output HTML, JSON, plain text, etc. all
from one method)
* Built-in database transactions: keeps your database (and you!)
sane. Transactions are committed or rolled back based on the success
or failure of your controller code.
* flexibility as needed: though Kid and SQLObject are the standards,
we already support many other template engines (Cheetah, Markup,
Django) and the powerful SQLAlchemy object-relational mapper.
* community: last but definitely not least -- more than 2,000 users
on the main mailing list, and others on non-English mailing lists
In short, there are lots of tools to help you get the job done quickly.
What's New Since 0.8
--------------------
Nearly everything. All of the projects that TG uses have had
significant upgrades, and nearly all of the features that have been
built by TurboGears contributors are new.
Website: http://www.turbogears.org/
Download: http://www.turbogears.org/download/
Mailing list: http://groups.google.com/group/turbogears
--
Kevin Dangoor
TurboGears / Zesty News
email: k...@blazingthings.com
company: http://www.BlazingThings.com
blog: http://www.BlueSkyOnMars.com
Yep! In the normal place:
http://www.turbogears.org/download/upgrade.html
Kevin
Is there anyone else here who has never had any luck getting Cheetah to
easy_install? I end up manually doing it every single time. Either the
local install of it conflicts with the global install (this doesn't
affect any other packages so I'm unsure whether to blame setuputils or
Cheetah, but I'm leaning toward the latter), it can't download from
sf.net, it hoses easy_install.pth... it seems like one thing after
another.
Regards,
Cliff
I just make TurboJinja template (which use Django template syntax)
available on cheeseshop
http://www.python.org/pypi
TurboJinja makes you use Django template-like syntax without install
Django.
http://docs.turbogears.org/1.0/DjangoTemplating
--
cheers
elvelind grandin
>>
>> Are upgrade instructions to be found somewhere?
>
> Yep! In the normal place:
>
> http://www.turbogears.org/download/upgrade.html
They need a little tweaking though since they still refer to preview/
download in the instructions.
Cheers,
Arthur
--
One secret of happiness is to ignore comparisons with people who are
more successful than you are: always compare downwards, not upwards”
- Richard Layard
I live behind a corporate NAT/firewall so the automated ez-install
download system is no use. The only alternative seems to be to manualy
download about a hundred (realy!) little eggs and tar files, not all of
which I may need because many of them are for older versions of Python
or for the Mac, so I have to hand-pick my way through them. But do I
actualy need all of them for the auto-installer to work and pick
through them for me? Do I need all th actuale Turbogears tarballs, or
just the latest one? I'm lost.
Argh! What's so evil about putting a single zip/gzip file up there for
download? Maybe real developers roll their own install scripts, or
something. This is turning what should be a strength of TG - the fact
that it leverages many 'best of breed' tools - into a serious
disadvantege because if you're not on a bare internet connection you
have to go pickying about to download all these fiddly little bits and
set them all up.
I've had the download problem with other projects too, it's as though
if you've got an actual job and live behind a corporate firewall you
can get knotted. I want to do an evalution of Django and TG for a
project, but even to take a look at TG I've got to jump through all
sorts of contorted hoops.
I was going to start with TG as it looks very attractive, and then
maybe look at Django, but as that's just a single dowload and off you
go I think I'll do it the other way around. This is a serious problem.
If I do select TG for a project, the chances are by the time we start
real development I'll have to do this all over again. If the install
process is so awkward, what about the upgrade process? It doesn't
inspire confidence in future version management and maintainability
either. I'm sure the easy install system is wonderful for those that
can use it, but that does me and people in my situation no favours
whatsoever.
Simon Hibbs
> I'm sorry this is such a rant, but it's how I'm feeling right now.
There was a set of messages on the list recently about how to install
without a net connection
Search for the subject 'ez_setup?? Easy my @ass'
http://groups.google.com/group/turbogears/browse_thread/thread/
dd114347e218cab0/605b24b7026d5e7d?lnk=gst&q=ez_setup%3F%3F+Easy+my+%
40ass&rnum=1#605b24b7026d5e7d
has all the gory details.
Arthur
--
He's a stranger to freedom
He's shackled to his fears and doubts
- Mary Gauthier
Matt
--
http://acl.icnet.uk/~mw
http://adhominem.blogsome.com/
+44 (0)7834 899570
as another alternative does the nat stop you checking out of the
subversion repository? That might be another option?
glenn
http://83.138.152.43/turbogears-1.0b.zip
I'm happy to keep it updated as new releases come out. You can
extract it and use easy_install to install from a folder.
Either that or use Firefox and the DownThemAll extension (that's what
I used to grab all the eggs at once).
Ed
I have no idea why easy_install isn't working. I tried all the arcane
incantations from the threads referenced and no joy. I tried futzing
with proxy environment variables and such, also nada.
As for various posts along the lines of "if easy_install fail;s becasue
another script screwed it up, 'simply' type xxx -yyy /zzz etc, etc, etc
and if that doesn work 'just' ty blah blah blah."
I don't know, perhaps there's a rarely used meaning of the terms 'just'
and 'simply' that I'm not aware of.
Still, many thanks for everyone's help and comments, as usual another
very helpful and friendly Python list. I feel pretty bad about the
negativity of my posts here, honestly I don't think that's typical of
me, but realy. Packaging software for distribution is generaly speaking
a solved problem these days.
Simon Hibbs
When it works, it really is that simple. ;]
> Still, many thanks for everyone's help and comments, as usual another
> very helpful and friendly Python list. I feel pretty bad about the
> negativity of my posts here, honestly I don't think that's typical of
> me, but realy. Packaging software for distribution is generaly speaking
> a solved problem these days.
Kevin keeps talking about providing a download with all the eggs, but
I think it's one of those things that just keeps getting pushed off
because no developers on the project have this problem. I'm the
closest, but -zmaxd solves my problems.
I thought easy_install had an option to dump all the files into a
directory. Any way we could build on that to make a one button "I've
finished updating all the eggs, build me a zipfile" script?
Thanks for this one-stop-zip :!)
I downloaded it and checked its contents. I think, while it contains
all of them listed in:
http://www.turbogears.org/download/
it may be missing one or more files it fetches from elsehwere, such as:
Cheetah-2.0rc7.tar.gz
which the installer gets from:
http://cheeseshop.python.org/packages/source/C/Cheetah/Cheetah-2.0rc7.tar.gz#md5=8a374
9a203719e0de6b0af0e841f5371
Tho laborious, what've I've done in the past is:
. install TG on a box with 'net access and that has an OS-ver closest
to your target OS-ver. Special care will be needed for the
following:
. Cheetah-2*.tar.gz
. cElementTree-1*.zip
. PyProtocols-1*.zip
. RuleDispatch-0.5*.tar.gz
. scgi-1.11.tar.gz (for lighty and may be nginx proxy use)
since the installer generates target-OS specific .eggs for these
. capture and examine the installation logs
. figure out what it decides to fetch from elsewhere
. fetch those in addition to what it finds at the TG-downlaod page
listed above
. also fetch flup & scgi modules (for lighty and may be nginx proxy
use) based on notes in:
http://docs.turbogears.org/1.0/LightTPD
. collect them all into one (build/install-from) folder
. basically follow the instructions provided by Karl in the post
titled:
"ez_setup?? Easy my ..."
in this forum
One thing folks with access to the download page could do is (for
visual clarity) to organize those files listed in two columns/n-rows:
one for 1.0b1 and another for the next preview rel, where the rows are
for OS's/CPUs. Right now, there is no logic to the order of those files
in that one-humongo-listing.... One has to wade thru those for a manual
download, and it becomes painful. Assuming the TG site is TG-based,
should be easy to put this info in a db-table and get the table/row org
for free :-)
Thanks again to Kevin & Team for TG 1.01b
Best,
/venkat
I plan on getting batch download instructions in to the official docs
once we have a fairly simple/coherent system for building the
appropriate zip files and getting them on the site.
> Assuming the TG site is TG-based,
> should be easy to put this info in a db-table and get the table/row org
> for free :-)
You'd be assuming incorrectly there. The site is kid-based but is
statically generated (it's a site, not an app).
> just for my own curiosity how does the fire wall stop you using
> ez-install? doesn't ez use http on port 80 to download each of the eggs
> - just like your web browser would do if you manually tried to download
> each of the eggs?
Hi Glenn (and everyone),
In my case there is a MS Proxy server between me and the world and it
only allows NTLM authentication. (I know, shudder!)
Setup tools suggests using NTLM APS to proxy the connection, but I find
it easier just to download the eggs, one at a time, and then do
"easy_install -f . TurboGears". The "-f ." means use the current
directory (which is where I have all the downloaded eggs).
And for setuptools itself, it is available as a tarball and can be
installed with the standard "python setup.py install". (no ez_setup
required).
You could even do "easy_install -zmaxd TurboGears" at home to just
download the files and then bring in the files on a usb key and then
"easy_install -f . TurboGears" from the usb drive. (After doing the
setuptool install, that is).
Though the single tarball that Ed is providing might be even easier.
But it is nice to have option.
Anyway, I hope this helps.
Krys
> Is there anyone else here who has never had any luck getting Cheetah to
> easy_install? I end up manually doing it every single time. Either the
It works here... I didn't do anything special.
--
Jorge Godoy <jgo...@gmail.com>
>
> I am pleased to announce TurboGears 1.0b1, which now supersedes the
> 0.8.9 release as the preferred TurboGears release. Many people have
> been using the TurboGears 0.9x releases for several months now and
> have been very happy with the results. The 1.0 APIs are stable and
> we're focused on bugs and docs for the final 1.0 release. This is a
> bugfix release over 0.9a9.
Cool! Congratulations and thanks for the work! I see that the setup.py
declares a dependency on CherryPy that disallows >= 3.0; is that so? Is
cherrypy 3.0 incompatible, or you're just being cautious?
In a quick glance over the UpgradeTo30 documento on cherrypy.org I see
some important modifications which may be problematic, but have not
checked them closely yet.
See you,
--
Gustavo Noronha Silva <k...@debian.org>
http://people.debian.org/~kov/
My pleasure. It's no hassle to do.
Is zip the best format for this? Or would people prefer I use a
different format?
> I downloaded it and checked its contents. I think, while it contains
> all of them listed in:
> http://www.turbogears.org/download/
> it may be missing one or more files it fetches from elsehwere, such as:
> Cheetah-2.0rc7.tar.gz
> which the installer gets from:
>
> http://cheeseshop.python.org/packages/source/C/Cheetah/Cheetah-2.0rc7.tar.gz#md5=8a374
> 9a203719e0de6b0af0e841f5371
I've added that. If anyone finds anymore I'll add them in.
> Tho laborious, what've I've done in the past is:
> . install TG on a box with 'net access and that has an OS-ver closest
> to your target OS-ver. Special care will be needed for the
> following:
> . Cheetah-2*.tar.gz
> . cElementTree-1*.zip
> . PyProtocols-1*.zip
> . RuleDispatch-0.5*.tar.gz
> . scgi-1.11.tar.gz (for lighty and may be nginx proxy use)
> since the installer generates target-OS specific .eggs for these
> . capture and examine the installation logs
> . figure out what it decides to fetch from elsewhere
> . fetch those in addition to what it finds at the TG-downlaod page
> listed above
> . also fetch flup & scgi modules (for lighty and may be nginx proxy
> use) based on notes in:
> http://docs.turbogears.org/1.0/LightTPD
> . collect them all into one (build/install-from) folder
> . basically follow the instructions provided by Karl in the post
> titled:
> "ez_setup?? Easy my ..."
> in this forum
That does sound laborious. I think I'll just stick to providing a
quick zip of the files (unless someone more authoritative wants to...)
Ed
Yes. Cherrypy 3.0 is incompatible with Turbogears 1.0b1
> In a quick glance over the UpgradeTo30 documento on cherrypy.org I see
> some important modifications which may be problematic, but have not
> checked them closely yet.
>
> See you,
>
> --
> Gustavo Noronha Silva <k...@debian.org>
> http://people.debian.org/~kov/
>
> >
>
--
cheers
elvelind grandin
You know, I've been thinking of doing just that. But I think you
mentioning it is just the kick I need to actually do it. I'll see what
I can do tonight, after work.
Thanks!
Krys
Well, I finally did it.
Details in this thread:
Thanks for the prod gasolin. :-)
Krys
I've reconfigured my dev server, so this is now available at
www.project-picard.net/turbogears-1.0b.zip
Ed
> I've reconfigured my dev server, so this is now available at
> www.project-picard.net/turbogears-1.0b.zip
>
> Ed
The link does not work for me. I get a 404.
Also the old link gives me a Cherrypy error.
I have updated the OfflineInstall page to your new url, but both links
are now broken.
Thanks,
Krys
I just noticed the comment on the wiki page. The correct (and tested)
URL is:
http://www.project-picard.net/tg/turbogears-1.0b.zip
I have updated the doc again. It works now.
Thanks Ed!
Krys