Add the capability to load gunicorn.base.Application without the loading
of the arguments of the command line.
Add an example for the gunicorn.app.base.BaseApplication
  Fix for issue #693
  - Made changes to read and fetch code object from .pyc files.
  - Error message "Non-ASCII character '\xf3' in file" is resolved.
  Fix for issue #693
  - Override older behavior of execfile_ with one with pyc patch
	Fix for issue #693
	- Remodeled the logic to use imp module to validate the python
	  gunicorn config file
	Fix for issue #693
	- Added changes to file read, as per review comments
Merge pull request #696 from jerynmathew/fix/693-config-pyc

Fix for #693
Add Jeryn Mathew to thanks

Thanks, @jerynmathew
Fix microseconds logging, add decimal seconds.

Apache will log %D microseconds over 1 million for requests that take over a second, this change sync's that access log behavior since the formatting seems to be based on that. So a request that takes 1 second and 30 milliseconds will have 1000030 for this atom.

This pull request  also adds a %L atom for decimal seconds for a quick human-readable latency number. In the above example it would output 1.000030 to the log.
add `--threads` param
Export logo svg as plain svg
Typo
Merge pull request #723 from zyegfryed/patch-1

Typo
add fdevents module

This module add a new cross platform event poller to gunicorn. It allows
you to listen on different fds in an efficient manner.

On linux it's using epoll, bsd/darwin kqueue...
Merge pull request #719 from bobzilladev/access-timing

Fix microseconds logging, add decimal seconds.
Remove incompatible SSL option in Python 2.6

An exposed SSL option, `ciphers`, was added in Python 2.7 and breaks older
versions of Python with an unexpected kwargs error.

I'm not sure if this is the best way to fix this, and I'm happy to consider
other approachs. Some things I'm a bit up in the air about are:

  i) This is only broken for Python 2.6 and older whose ssl module doesn't
  expose this. Do the other types of workers not use ssl module, and thus might
  be able to make use of the `cipher` kwarg?

  ii) Should we silently or explicity fail? I couldn't find a nice way to do
  this because the configuration setting has a default value and resulted in
  stringy code to special case the one setting`.

What I would really like to do would add a "python_version" validator that
could intelligently handle this, but I went off into the weeds figuring out
how the SettingsMeta class works. :)
Define `Ciphers` config conditionally

We only expose the `Ciphers` config parameter in versions of Python that
support it (i.e., >= Python 2.7).
Add an example of a standalone app
Fix code.djangoproject.com/ticket/20185

This change favors `python2` over `python3` by reversing the try/except order. 

Untested in `python3`, as most Django packages are not yet `python3`-compatible.
Works in `python2`, `Django 1.5.4`, `gunicorn 18.0`.

When running `gunicorn` in python 2, if a django model doesn't validate, the `gunicorn` will fail to display informative error messages about your model and instead complain about `str`/`unicode`:

Django was falsely accused of [this bug](https://code.djangoproject.com/ticket/20185)
Merge pull request #728 from hobson/master

Fix code.djangoproject.com/ticket/20185