In 0.9, will KitchenSink support KitchenSource plug-ins?
And do circular references still confuse the GarbageDisposal?
I'm looking forward to the Counter and Range integration.
I think all of the problems with GarbageDIsposal, Counter, and Range
are fixed, but I don't know about KitchenSync
On 12/7/05, Don Hopkins [EMAIL PROTECTED] wrote:
In 0.9, will KitchenSink support KitchenSource plug-ins?
And do circular references still confuse the GarbageDisposal?
I call Not-Invented-Here on that one! Why would we need our own
GarbageDisposal when Python already comes with a
On 12/8/05, Kevin Dangoor [EMAIL PROTECTED] wrote:
On 12/7/05, Don Hopkins [EMAIL PROTECTED] wrote:
In 0.9, will KitchenSink support KitchenSource plug-ins?
And do circular references still confuse the GarbageDisposal?
I call Not-Invented-Here on that one! Why would we need our own
I did actually have the documentation portion of the site split out
between release version and development version earlier. The problem
was that documentation updates needed to be made in both places (for
corrections and amplifications). So, I brought them back together and
started labeling the
On 12/7/05, Jared Kuolt [EMAIL PROTECTED] wrote:
A big reason I don't like this idea is that the changes between 0.8
and 0.9 are so vast, it's comparing apples and oranges. I'm almost to
the point of telling people not to touch TurboGears until 0.9 because
so much of what they'll know about
I wouldn't go that far either. I tend to over-dramatize my points.
Though I think my point remains valid. Using 0.8, you'd have to create
a lot of functionality that is be built into 0.9. I would prefer to
wait it out instead of re-inventing the wheel, then porting it back to
the new wheel
6 matches
Mail list logo
