Which Pyramid based "Development Environment"/Framework should I be considering?

[Randy Syring]

I've always rolled my own frameworks, but as my company grows, I think it's time to consider adopting a framework that already exists.  I've typically leaned towards Flask and friends in the past, but due to the way releases are being handled, I'm shopping. 

I'd be great if we could pick up on some already best-of-breed decisions regarding authentication, forms, etc.  Therefore, I've been looking at the "Development Environments" that Pylons lists here:

http://docs.pylonsproject.org/en/latest/docs/pyramid.html#pyramid-add-ons

Being a bit out-of-touch with the Pylons community, I'd appreciate any thoughts the crowd could give regarding which environment would be a good long-term bet for basing some new applications on.

Some of my considerations:

• Has to be SQLAlchemy based.
• Would prefer deform (I think) for forms, but might be persuaded otherwise.
  
• Track record of good development decisions and actively being developed.
• Big enough community that it's not likely to be abandoned in the near future.

Thanks in advance.

[Andreas Kaiser]

On 18 May 2015, at 22:25, Randy Syring wrote:

> Some of my considerations:
>
> - Has to be SQLAlchemy based.
> - Would prefer deform (I think) for forms, but might be persuaded
> otherwise.
> - Track record of good development decisions and actively being
> developed.
> - Big enough community that it's not likely to be abandoned in the
> near
> future.

Kotti matches all of the above. It's a stable and fun to work with
environment.

Disclaimer: I'm one of Kotti's core developers and therefore absolutely
biased.


Andreas

[Michael Merickel]

If you are used to rolling your own then Pyramid is a great place to
start. I would recommend starting from core Pyramid unless you find
one of the more opinionated solutions fits your needs.

> --
> You received this message because you are subscribed to the Google Groups
> "pylons-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pylons-discus...@googlegroups.com.
> To post to this group, send email to pylons-...@googlegroups.com.
> Visit this group at http://groups.google.com/group/pylons-discuss.
> For more options, visit https://groups.google.com/d/optout.

[Vincent Catalano]

I stumbled across this Pyramid starter project recently and it has been an immense help for me: https://github.com/mazz/kifu. Although it's fairly opinionated with its architecture and library choices, its quite a bit leaner than a lot of the other Development Environments.

-Vincent

--
You received this message because you are subscribed to the Google Groups "pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discus...@googlegroups.com.
To post to this group, send email to pylons-...@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/d/optout.

--

Vincent Catalano
Software Engineer and Web Developer,
(520).603.8944

[wilk]

On 18-05-2015, Randy Syring wrote:
> ------=_Part_793_1541699878.1431980742515
> Content-Type: multipart/alternative;
> boundary="----=_Part_794_1959648491.1431980742515"
>
> ------=_Part_794_1959648491.1431980742515
> Content-Type: text/plain; charset=UTF-8

>
> I've always rolled my own frameworks, but as my company grows, I think it's
> time to consider adopting a framework that already exists. I've typically
> leaned towards Flask and friends in the past, but due to the way releases
> are being handled, I'm shopping.

I was in the same situation with my own framework. With Pyramid i didn't
throw away my framework. Instead i replace gradually each part of my
framework with Pyramid equivalent. The flexibility of Pyramid is perfect
for this.

For good development decision I look at http://substanced.net It doesn't
use sqlalchemy but it show some good practices.

You don't need to worry about the long term support of Pyramid, the code
is very clear, short and documented. In the worse case it will be
possible to maintain it like your own framework (i found it more
documented than my own home-framework !).

If you don't see a lot of activity in the community it's because it just
work. The stability of functionalities is a feature (my interpretation).

Welcome !

--
William

[wilk]

On 18-05-2015, Randy Syring wrote:

> I've typically leaned towards Flask and friends in the past, but due
> to the way releases are being handled, I'm shopping.

Just out of curiosity what is this way ?

--
William

[tonthon]

+1
It makes it easier to understand the choices made for you in the
different Dev environments.

In our case we chose Kotti because it was very close to what we ended up
writing in our first Pyramid projects.