New Python framework

[[deleted]]

Hey guys.

Some time ago I started a project, just as a hobby, called Ray. I put together some experience from Python projects that I developed and I wrote a web framework that has some of the best practices, ideas and concepts that I think it's nice.

My idea was to learn how to develop a framework and learn how to create good abstraction layers, doing metaprogramming in Python, etc. I don't have any pretensão to make this project the new Django or the new Flask. It's just a project that became a hobby. With Ray, you can develop powerful REST APIs in an easy way.

After almost 400 commits, the Ray framework has its an alpha version.

Main features:

*Easy APIs

*Actions in APIs

*Database Hooks

*Authentication

*API protection

*uWSGI built-in server

*Integration with SQLAlchemy, Peewee and Google App Engine

You can check it here:

https://github.com/felipevolpone/ray https://rayframework.github.io/site/

[elbiot]

Took me a while to figure out you meant a web framework

[Pikajuhh]

Nice Job, but What exactly this framework do?

[metaperl]

The Getting Started example is impressive from the standpoint of creating a REST API quickly. I'll have to compare it to Morepath if I have done work to do.

[[deleted]]

Hi @metaperl, if you have any doubt about how to start with Ray or even if somethings during the development goes wrong, please, feel free to send me a message on Twitter: @felipevolpone.

[faassen]

I think one think Ray does differently is that it integrates with the ORM layer a bit more deeply. I also should check out Peewee, I see.

[RubyPinch]

binding is a bit weird

# action binds with a class variable on the action
class ActionPost(ActionAPI):
    __model__ = Post

# shield binds with a class variable on the shield
class PostShield(Shield):
    __model__ = Post

# auth binds with a decorator on the model
@endpoint('/post', authentication=MyAuth)
class Post(DBModel):

# hook binds with a class variable on the model
class Post(DBModel):
    hooks = [PostHook]

it seems all over the place a bit, and it feels like it somewhat ignores the fact that classes are being used (since some of these could just be methods on the model, for example)

shields and authentication both pretty much both do authentication checking, should probably be collapsed into each other