<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">I don’t have an opinion for now but do have some thoughts instead.</div><div class=""><br class=""></div><div class="">We use Pecan in Ironic.</div><div class="">I could say that it’s pretty nice when one needs to make something simple but requires some manual job to be done in more or less sophisticated cases.</div><div class="">On the other hand we have that the Pecan team is quire agile and open to other developers so we were able to merge our patches without any problems.</div><div class=""><br class=""></div><div class="">However, if there is a framework that fits Nailgun's needs without being patched, that may be easier for us to just use it.</div><div class=""><br class=""></div><div class="">There’s a political side of the question as well but I’d rather touch it only if both Flask and Pecan have the same pros and cons.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">- romcheg</div><div class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On 03 Dec 2014, at 14:22, Przemyslaw Kaminski <<a href="mailto:pkaminski@mirantis.com" class="">pkaminski@mirantis.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
  
    <meta content="text/html; charset=windows-1252" http-equiv="Content-Type" class="">
  
  <div bgcolor="#FFFFFF" text="#000000" class="">
    Yeah, didn't notice that. Honestly, I'd prefer both to be accessible
    as instance attributes just like in [1] but it's more of taste I
    guess.<br class="">
    <br class="">
    [1]
<a class="moz-txt-link-freetext" href="http://tornado.readthedocs.org/en/latest/web.html#tornado.web.RequestHandler.request">http://tornado.readthedocs.org/en/latest/web.html#tornado.web.RequestHandler.request</a><br class="">
    <br class="">
    P.<br class="">
    <br class="">
    <div class="moz-cite-prefix">On 12/03/2014 02:03 PM, Sebastian
      Kalinowski wrote:<br class="">
    </div>
    <blockquote cite="mid:CAGRGKG7-_O7WfrqeJ0ayggw07_1=XUVmSXra-L1ThteKw5Ga6g@mail.gmail.com" type="cite" class="">
      <div dir="ltr" class=""><br class="">
        <div class="gmail_extra">
          <div class="gmail_quote">2014-12-03 13:47 GMT+01:00 Igor
            Kalnitsky <span dir="ltr" class=""><<a moz-do-not-send="true" href="mailto:ikalnitsky@mirantis.com" target="_blank" class="">ikalnitsky@mirantis.com</a>></span>:<br class="">
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex"><span class="">> I
                don't like that Flask uses a global request object [3].<br class="">
                <br class="">
              </span>Przemyslaw, actually Pecan does use global objects
              too. BTW, what's<br class="">
              wrong with global objects? They are thread-safe in both
              Pecan and<br class="">
              Flask.<br class="">
            </blockquote>
            <div class=""><br class="">
            </div>
            <div class="">To be fair, Pecan could also pass request and response
              explicit to method [1]<br class="">
              <br class="">
              [1] <a moz-do-not-send="true" href="http://pecan.readthedocs.org/en/latest/contextlocals.html" class="">http://pecan.readthedocs.org/en/latest/contextlocals.html</a><br class="">
            </div>
          </div>
        </div>
      </div>
      <br class="">
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br class="">
      <pre wrap="" class="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
    </blockquote>
    <br class="">
  </div>

_______________________________________________<br class="">OpenStack-dev mailing list<br class=""><a href="mailto:OpenStack-dev@lists.openstack.org" class="">OpenStack-dev@lists.openstack.org</a><br class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br class=""></div></blockquote></div><br class=""></body></html>