schleppy_oc

I think my time ended shortly before Angelo’s began, but my experience with Central Tech (worked mostly with Steve L. and Guarav) was that they were very talented generalists. They were the team you dropped in to work on C++ game code, Lua UI code, Erlang server code, or Python scripts. They were a resource to work on anything you needed and you could give them a task knowing it would be done well.

The director of development at BeachHead studios originally applied for Central Tech.

As is “nasty”, “snapping”, “blowing up at”, “dramatic”, and “passive agressive.” Oh, and let’s not forget “horrible.”

Have you ever dealt with bad docs? Seriously!!!

The best Ops people I have worked with (looking at you Dennis and Alan) repeat everything back that I say. More than once I have caught mistakes in my approach simply by hearing someone else repeat back exactly what I just said.

This is the exact name I was going to suggest. Kudos to you.

The Any -> Unit definitely defies the current name.

I second this. The people I met at GopherCon were among the top group for any community built around a language.

I spoke at length with someone there about Martini, and had pretty much the same take on it as Jeremy now professes. The stuff he did with the dependency injection was really solid, but as he admits, it is not very idiomatic. I applaud his new effort while maintaining the existing project that so many are using.

This... exactly. Presentation was great. Presenters were really good. Gobot looks solid.

Phabricator was one of the first tools I brought to my latest company. We primarily use it for Differential because the arcanist command line tool is so easy to use. Even those that are somewhat git challenged benefit as it handles merging commands for you when you land a review.

The IRC channel is a great place for Q&A and epriestley et. al. are always there to offer help.

Before you bash it for being written in PHP, take a look at the source; it is unlike any other PHP code I have ever seen.

I am pretty certain that he, the_mitsuhiko (aka. Armin Ronacher), being the main developer behind Werkzeug and Flask knows exactly how long bottle.py is.

Why not just use a simple csrf stored in a session? You already have an "authenticiy_token" in the request data, why not use it, or add another value for csrf?

FYI, it looks like plans for porting werkzeug / flask to Python 3 may be close at hand. https://twitter.com/mitsuhiko/status/323177177367601152

Straight from the horses mouth:

The big difference is that Flask is based on other technologies such as Werkzeug and Jinja2 that exist for a longer time and it does not try to reinvent things. Bottle on the other hand tries to stick to the one-file approach. I want to merge them but the Bottle developer does not seem to be very happy about the idea of stepping away from the “one file” requirement.

Regarding flexibility: there are no reasons you shouldn't be able to use flask with other template engines if that's what you're after. In fact, things like Flask-Genshi exist: Flask-Genshi and it's incredible easy to use mako with it, even without extension if you want to.

Bias warning: I am the developer of Flask, Werkzeug and Jinja2.

http://stackoverflow.com/questions/4941145/python-flask-vs-b...

In my own experience, both are great, and similar. For a simple REST API bottle has an added advantage of being a single file which is nice to just include with all of your other code rather than having to install anything. Flask, however, is my go-to framework. I used it extensively at a previous job and still do today with my current employer (and the app is pretty substantial). Flask also has a lot of extension support now. A pip freeze | grep Flask yields the following for one project.

  Flask==0.9
  Flask-Admin==1.0.5
  Flask-Assets==0.8
  Flask-Babel==0.8
  Flask-Cache==0.10.1
  Flask-Classy==0.5.2
  Flask-DebugToolbar==0.7.1
  Flask-Gravatar==0.3.0
  Flask-Login==0.1.3
  Flask-Principal==0.3.4
  Flask-SQLAlchemy==0.16
  Flask-WTF==0.8.2

Out of curiosity, how do you inject your own request_handler if you are running behind something like uwsgi/nginx where you only specify the wsgi container and don't ever call run yourself? It appears the request_handler is only passed on through to werkzeug via run(kwargs).

LOL "Error establishing a database connection"