Python on Wheels • Hacker News Board

Re: Python on Wheels

#41

Post by pythononwheels » Tue, Aug 14, 2012, 7:14 AM UTC

banana_bread wrote: post #38

pythononwheels wrote: post #26

One important remark: if you check it out from github, be sure to get the Beta1 branch. The master branch is really long behind the current development. I also stated that in the screencast. And as i think about it, some of the comments might refer to the master branch (like the one saying there is no directory structure) which is not the case in Beta1... Regards

Why is this better than Django or Flask, web2Py or CherryPy ect.

Doesn't want to be better but more generative, so quicker first app results. Idea is to add many rails-alike helpers like pagination, observation, etc... Easing small apps life .;)

Re: Python on Wheels

#42

Post by pythononwheels » Tue, Aug 14, 2012, 7:20 AM UTC

heretohelp wrote: post #36

Has this person never seen Flask before? Why bother? EDIT: OH GOD THE CODE, YOU MAKE KITTY SCARED

I think flask is ment to be really micro. Misses ( and wants to miss IMO ) the generative approach. Also misses ( and wants to ) the db layer etc So these approaches are really different.

Code: i will cleanup and DRY the generatots. But generated code is the one i was working on and that the user will work on and read. This is ways better.

Not scary at all ;)

Re: Python on Wheels

#43

Post by pythononwheels » Wed, Aug 15, 2012, 12:29 AM UTC

tbatterii wrote: post #35

pythononwheels wrote: post #30

Earlier quoted context omitted.

Intersting that you chose a different framework for almost any field. So there is room ;) I am thinking about a google app engine port but sqlalchemy is a showstopper here .. Need the models to talk GQL ... So i stopped that port for now. Much to do in the base.. Thx, regards, khz

how about just not using sqla and use ndb(distributed with the sdk) instead?

NDB is a good hint. But the problem remains that I want PoW to be able to support SQL DBs also. I think SQLAlchemy is a really mature framework for that area. So I need to generate the models in two ways.. I think I need to separate this as an extension since I do not want to have two PoWs, where one is for GAE and one for SQL.

Re: Python on Wheels

#44

Post by tbatterii » Wed, Aug 15, 2012, 8:37 PM UTC

pythononwheels wrote: post #43

tbatterii wrote: post #35

Earlier quoted context omitted.

how about just not using sqla and use ndb(distributed with the sdk) instead?

NDB is a good hint. But the problem remains that I want PoW to be able to support SQL DBs also. I think SQLAlchemy is a really mature framework for that area. So I need to generate the models in two ways.. I think I need to separate this as an extension since I do not want to have two PoWs, where one is for GAE and one for SQL.

that's the thing with gae, if you want to pretend you aren't going to use it and instead try to abstract away that fact, you are in for a world of pain. you either do gae, or not... no waffling.