Hi, I think such a big change requires blueprint. Before decision I would like to know answers to this questions:
- what's wrong with web.py - what are our requirements for web framework And another question is, why we don't follow community approach? As far as I know none of OS projects is using Flask. Pecan+WSME is already used by ceilometer, ironic and even tuskar. I also saw patch for nova to use pecan. Also if OSTF is using pecan we already have required "in home" knowledge. I never used pecan nor flask and personally I really don't care what we use, but as openstack community member I would like to follow common pattern. Regards On Wed, Aug 6, 2014 at 2:56 PM, Dmitriy Shulyak <dshul...@mirantis.com> wrote: > Hi, > > What do you mean - no json support? > Ostf is written in pecan - and it always replays with Content-type: > application/json > > I still prefer to use flask, as it is overall better framework with huge > user base, and a lot of plugins, that we can use in future. > For example we can add existing admin panel with nice interface, which > will be quite helpfull in development. > > > > On Wed, Aug 6, 2014 at 3:36 PM, Nikolay Markov <nmar...@mirantis.com> > wrote: > >> Last time I saw Pecan it didn't have JSON support at all, only text/plain >> and html. That's kinda strange for REST framework. >> >> >> On Wed, Aug 6, 2014 at 4:07 PM, Andrey Danin <ada...@mirantis.com> wrote: >> >>> What is the status of Pecan? Does it mature and used broadly in >>> OpenStack community? Or it's buggy like Oslo.messaging? >>> >>> >>> On Wed, Aug 6, 2014 at 1:59 PM, Nikolay Markov <nmar...@mirantis.com> >>> wrote: >>> >>>> Hello colleagues! >>>> >>>> As you may know, we really want to get rid of old web.py and go towards >>>> something new, especially because for now it's not really hard to rewrite >>>> our API as it became more abstract. Also, in Fuel 6.0 there will be >>>> multiple important changes in our API, so we definitely need to implement >>>> v2, and doing it using modern framework looks like a good start. >>>> >>>> I did some research on both Pecan and Flask, also we had a discussion >>>> on this subject with our Fuel-Python team yesterday, and looks like we're >>>> choosing Flask over Pecan, because there are almost no bad things anybody >>>> could say about it. >>>> >>>> What are your thoughts? I know there is a pull request on Pecan >>>> already, but my personal opinion is it doens't worth all this headache. >>>> >>>> -- >>>> Best regards, >>>> Nick Markov >>>> >>>> -- >>>> Mailing list: https://launchpad.net/~fuel-dev >>>> Post to : fuel-dev@lists.launchpad.net >>>> Unsubscribe : https://launchpad.net/~fuel-dev >>>> More help : https://help.launchpad.net/ListHelp >>>> >>>> >>> >>> >>> -- >>> Andrey Danin >>> ada...@mirantis.com >>> skype: gcon.monolake >>> >> >> >> >> -- >> Best regards, >> Nick Markov >> >> -- >> Mailing list: https://launchpad.net/~fuel-dev >> Post to : fuel-dev@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~fuel-dev >> More help : https://help.launchpad.net/ListHelp >> >> > > -- > Mailing list: https://launchpad.net/~fuel-dev > Post to : fuel-dev@lists.launchpad.net > Unsubscribe : https://launchpad.net/~fuel-dev > More help : https://help.launchpad.net/ListHelp > > -- Łukasz Oleś
-- Mailing list: https://launchpad.net/~fuel-dev Post to : fuel-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~fuel-dev More help : https://help.launchpad.net/ListHelp