Please explain me why this is API change?
old code
http://trac.turbogears.org/browser/projects/tg.devtools/trunk/devtools/templates/turbogears/%2Bpackage%2B/websetup.py_tmpl?rev=6511
new code
Honestly guys, if you want a bug for this change I can produce one in
about 30 seconds.
$ paster quickstart tgtest
$ cd tgtest
$ paster setup-app development.ini
change model
$ pastser setup-app development.ini
error ensues
My change fixes this bug and is a minor refactor. This is the biggest
On Monday March 23, 2009 16:58:17 Jorge Vargas wrote:
On Mon, Mar 23, 2009 at 8:02 AM, Gustavo Narea m...@gustavonarea.net wrote:
On Monday March 23, 2009 07:29:54 Jorge Vargas wrote:
Please explain me why this is API change?
snip
please tell me how the calling code changes from A to B ?
This has taken way too long and it's way out of topic. I won't bother
answering inline anymore. If you want to think it's api change then
fine go ahead this is no api at all as you don't even need quickstart
to have a TG2 project. If you keep insisting it changes the API fine I
won't argue about
Look, it was my choice to make this happen, and I stand by it.
We can tell people installing pages to update websetup.py as
nessisary, and the people reading the python magazine article can use
code that just works.
And from my perspective the code inside the quickstart--that we intend
for
On Wed, Mar 18, 2009 at 7:14 AM, Gustavo Narea m...@gustavonarea.net wrote:
Hello,
If we're supposed to be in a feature-freeze, that's for people to be confident
that from now on things aren't going to change, unless a critical bug has to
be fixed, so that they can start building software
Well, since this is a template only change, you can make the change
after quickstart and never install 2.1 and there are several issues
that go into a feature freeze:
1) potential for breaking things
2) need to rewrite docs
3) need for public blog posts, articles, etc to work with the released
Hi, Jorge et al.
On Sunday March 22, 2009 22:02:42 Jorge Vargas wrote:
If we're supposed to be in a feature-freeze, that's for people to be
confident that from now on things aren't going to change, unless a
critical bug has to be fixed, so that they can start building software
and
Hello,
On Sunday March 22, 2009 23:11:48 Mark Ramm wrote:
And from Gustavo's message I assume that he had people put extra
bootstrap data into websetup.py and showed that in the article --
which is what would be broken by chris's change.
Yes, exactly.
Cheers!
--
Gustavo Narea
let me clarify this.
On Tue, Mar 17, 2009 at 10:38 PM, Jorge Vargas jorge.var...@gmail.com wrote:
On Tue, Mar 17, 2009 at 2:05 PM, Mark Ramm mark.mchristen...@gmail.com
wrote:
Works for me. We can try to shoehorn this into rc1 if we can get it
done in the next day or so -- otherwise
Hello,
If we're supposed to be in a feature-freeze, that's for people to be confident
that from now on things aren't going to change, unless a critical bug has to
be fixed, so that they can start building software and writing about TG2 with
the guarantee that their product isn't going to
I after a bit more thinking about this, and after seeing the size of
the change, I think I'm back to thinking this will be a 2.1 feature.
But I know it's nice stuff and nesissary for tgext.pages, but the
component stuff is a 2.1 goal, and we do have a feature freeze going
on, and I need to be
Well, it's in and the docs are updated. Dunno what to say, you
mentioned this after I had already implemented.
On Mar 18, 6:17 am, Mark Ramm mark.mchristen...@gmail.com wrote:
I after a bit more thinking about this, and after seeing the size of
the change, I think I'm back to thinking this
By the way, we really need HG. I think that should be a goal for
pycon. We need to be able to easily branch on stuff like this.
Also, i have every confidence that this change will not introduce
errors. I will also be online almost continuously over the next few
weeks for support (9-9 MDT)
I totally understand, and we'll have a branch with this in it right
away -- and that branch will be called trunk. ;)
I will also branch off the 2.0 docs for polishing, and leave your new
docs in trunk.
--Mark Ramm
On Wed, Mar 18, 2009 at 1:28 PM, percious ch...@percious.com wrote:
By the
On Tue, Mar 17, 2009 at 4:56 PM, percious ch...@percious.com wrote:
I have begun work on our new extensions methodology. (Some call this
component architecture). I am working with Jorge and Jon to try and
[...]
websetup/
__init__.py : contains setup_app which will be a combination of
Works for me. We can try to shoehorn this into rc1 if we can get it
done in the next day or so -- otherwise it'll be a 2.1 feature.
I want it done now, but making that happen will require updating
several docs :/ So, I'm a bit hesitant to about just going for it
directly.
--Mark Ramm
On
two more +1s and this is a go.
On Mar 17, 11:53 am, Florent Aide florent.a...@gmail.com wrote:
On Tue, Mar 17, 2009 at 4:56 PM, percious ch...@percious.com wrote:
I have begun work on our new extensions methodology. (Some call this
component architecture). I am working with Jorge and Jon
make that one more +1.
I will update the necessary docs if you can point me to the right
pages.
On Mar 17, 12:06 pm, percious ch...@percious.com wrote:
two more +1s and this is a go.
On Mar 17, 11:53 am, Florent Aide florent.a...@gmail.com wrote:
On Tue, Mar 17, 2009 at 4:56 PM, percious
Also, while I am at it, I am going to add some comments to the
quickstart which will work as template hooks for extensions. I'm
not sure how many of these hooks we will need, or how we should
document them, but this is a work-in-progress.
cheers.
-chris
On Mar 17, 12:07 pm, percious
Also, while I am at it, I am going to add some comments to the
quickstart which will work as template hooks for extensions. I'm
not sure how many of these hooks we will need, or how we should
document them, but this is a work-in-progress.
Could you explain a little? Hooks for template
comments in the .py files so that extensions in inject their goodness.
in bootstrap.py:
# bootstrap.before.user.data
# bootstrap.after.user.data
in root.py:
# rootcontroller.after.class.statement
# rootcontroller.eof
etc.
On Mar 17, 12:19 pm, Mark Ramm mark.mchristen...@gmail.com wrote:
I have begun work on our new extensions methodology. (Some call this
component architecture). I am working with Jorge and Jon to try and
get a handle on how to extend TG's database system. We are developing
a light weight CMS called Pages.
This is good to hear! Just one comment: call it
On Tue, Mar 17, 2009 at 2:05 PM, Mark Ramm mark.mchristen...@gmail.com wrote:
Works for me. We can try to shoehorn this into rc1 if we can get it
done in the next day or so -- otherwise it'll be a 2.1 feature.
-1 I think this is all tg2.1 stuff (together with my controller split)
I want
On Tue, Mar 17, 2009 at 2:23 PM, percious ch...@percious.com wrote:
I don't like this idea a lot, I think we should rethink how the whole
paster template stuff is handled, maybe we should replace it with
something that supports updates and merging (input from several files)
comments in the .py
On Tue, Mar 17, 2009 at 8:41 PM, Daniel Fetchinson
fetchin...@googlemail.com wrote:
I have begun work on our new extensions methodology. (Some call this
component architecture). I am working with Jorge and Jon to try and
get a handle on how to extend TG's database system. We are developing
26 matches
Mail list logo
