Jaroslaw Zabiello wrote:
Dnia 24 Sep 2005 22:48:40 -0700, [EMAIL PROTECTED] napisał(a):
You should give TurboGears a try.
This project is good only for fun and playing not for enterprise.
That's my kind of project :)
--
http://mail.python.org/mailman/listinfo/python-list
If you are looking for something pythonic, full featured and very easy
to use, you should check this out: http://karrigell.sourceforge.net
Give it a try and let me know how it goes...
Cheers,
Luis
--
http://mail.python.org/mailman/listinfo/python-list
I'm a python guy, so I haven't tried rails myself (I did read the
tutorial though). I tried Django and didn't like it somewhat. One thing
I don't like about it is that you have to write the same things twice,
for ex. specify url resolver and reference it in config. Django is not
bad but not
James wrote:
I actually like the framework to reflect on my database. I am more of a
visual person. I have tools for all my favorite databases that allow me
to get a glance of ER diagrams and I would rather develop my data
models in these tools rather than in code. Further more I rather like
On 2005-09-15, Jonathan Ellis [EMAIL PROTECTED] wrote:
James wrote:
I actually like the framework to reflect on my database. I am more of a
visual person. I have tools for all my favorite databases that allow me
to get a glance of ER diagrams and I would rather develop my data
models in these
Jacob Smullyan [EMAIL PROTECTED] writes:
I have mixed feelings about automagical schema introspection. PyDO
supports it, and will probably do so increasingly robustly if people
use it. But part of me feels that explicit is better than implicit
may win out over DRY here, because the ORM
On 2005-09-15, Jorge Godoy [EMAIL PROTECTED] wrote:
I just wonder when it becomes bad having to declare everything. For example,
we have databases with 600 tables.
[snip]
Having the introspection is great in this case (even though it is boring
having to declare all those classes and tell
Jacob Smullyan [EMAIL PROTECTED] writes:
Granted. Also, if the tables share structure, another option would be
to simplify their description with inheritance.
It would be great if relationships could be mapped this way too. Something
like ...
Diez B. Roggisch wrote:
- rails/subway reflect over a existing table. They create OR-mappings
based on that. You only specify exceptional attributes for these mappings.
- django specifies the whole meta-model in python - and _generates_
the SQL/DDL to populate the DB. So obviously you
My opinion, as posted there, was pretty immediate and only going off of
surface values. I just saw in Django what I had seen too much of in my
own code. I've written similar things in Zope and Formulator that did
all sorts of fancy automatic 'admin screen' generation, DBMS CRUD
statements. I even
I actually like the framework to reflect on my database. I am more of a
visual person. I have tools for all my favorite databases that allow me
to get a glance of ER diagrams and I would rather develop my data
models in these tools rather than in code. Further more I rather like
the idea of
Hello!
On 7 Sep 2005 20:56:28 -0700 flamesrock wrote:
On the other, Rails seems to have a brighter future,
Why that? Django is not yet released and everybody is talking about it.
Like it happened with RoR.
How difficult would it be to learn Ruby+Rails, assuming that someone is
already
Diez B. Roggisch wrote:
I tried to find out if subway and
rails can do the same - that is, generate the sql. For subway the lack
of documentation prevented that, and I didn't find it in rails , too.
In Rails you can do that with the command:
$ rake db_structure_dump
However I think it's not
Wow- thanks for all of the replies. I'm torn.
On the one hand, I'm fluent in Python and love it.
On the other, Rails seems to have a brighter future, and is a bit more
featureful (at this time.) However the only Ruby I know is what I've
already learnt with Python(even though I would like to
gene tani wrote:
http://griddlenoise.blogspot.com/2005/07/python-off-rails.html
I don't think that opinion is very founded - especially what he thinks
metaprogramming is about, and what not.
What he seems not to grasp is the crucial difference between django and
rails/subway (at least in the
Here's another, (i'm just flipping thru del.icio.us and furl tags, not
endorsing any viewpoints. I've never looked at Django or Subway, but I
do need to look at zope 3, i think):
http://www.magpiebrain.com/archives/2005/08/14/rails_and_django
Diez B. Roggisch wrote:
gene tani wrote:
Dnia 5 Sep 2005 19:06:51 -0700, flamesrock napisał(a):
Firstly, this topic is NOT intended for trolling or starting any flame
wars.
I want to know if anyone has experience with these frameworks, and if
so, how do they compare? Which one do you prefer?
Django's ORM does not work with SQL
flamesrock wrote:
D H,
'flamesrock' refers to the Calgary Flames, not the act of flaming.
It was just a joke about your statement and your name. I thought it was
obvious enough that a smiley wasn't necessary. I don't care though,
flames happen on comp.lang.python all the time.
Go with
D H wrote:
(snip)
Go with Rails. Django is only like a month old.
Please take time to read the project's page. Django has in fact three
years of existence and is already used on production websites, so it's
far from pre-alpha/planning stage.
--
bruno desthuilliers
python -c print
[D H]
Go with Rails. Django is only like a month old.
[bruno modulix]
Please take time to read the project's page. Django has in fact three
years of existence and is already used on production websites, so it's
far from pre-alpha/planning stage.
But the APIs still aren't 100% stable.
bruno modulix wrote:
D H wrote:
(snip)
Go with Rails. Django is only like a month old.
Please take time to read the project's page. Django has in fact three
years of existence and is already used on production websites, so it's
far from pre-alpha/planning stage.
Don't make any
D H wrote:
bruno modulix wrote:
D H wrote:
(snip)
Go with Rails. Django is only like a month old.
Please take time to read the project's page. Django has in fact three
years of existence and is already used on production websites, so it's
far from pre-alpha/planning stage.
just to make it really easy, there's some really good blogs and
detailed analyses of the frameworks, competition is good:
http://del.icio.us/tag/rails+django
gene tani wrote:
Here's another, (i'm just flipping thru del.icio.us and furl tags, not
--
bruno modulix [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
D H wrote:
(snip)
Go with Rails. Django is only like a month old.
Please take time to read the project's page. Django has in fact three
years of existence and is already used on production websites, so it's
far from
Firstly, this topic is NOT intended for trolling or starting any flame
wars.
I want to know if anyone has experience with these frameworks, and if
so, how do they compare? Which one do you prefer?
Going back to school in a few days, I simply don't have the time to try
both.
-thanks
flamesrock wrote:
Firstly, this topic is NOT intended for trolling or starting any flame
wars.
Whatever you say, flamesrock.
--
http://mail.python.org/mailman/listinfo/python-list
http://griddlenoise.blogspot.com/2005/07/python-off-rails.html
http://www.boddie.org.uk/python/web_frameworks.html
flamesrock wrote:
Firstly, this topic is NOT intended for trolling or starting any flame
wars.
--
http://mail.python.org/mailman/listinfo/python-list
Thanks for the links, gene tani.
D H,
'flamesrock' refers to the Calgary Flames, not the act of flaming.
--
http://mail.python.org/mailman/listinfo/python-list
28 matches
Mail list logo
