PUBLIC MARKS with search django

In an effort to make the code useful to as many people as possible, we've split it into several packages:

* The main package (probably the thing you're looking for) is the publishing system, known as ebpub.

* Second, the packages ebdata and ebgeo contain Python modules for processing data and making maps.

* Third, the packages ebinternal and everyblock round out the code that powers EveryBlock.com. They're internal tools and are likely not of general use, but we're including them to be complete.

* Finally, ebblog and ebwiki are our blog and wiki software, respectively. Because, dammit, the world needs another Django-powered blogging tool.

Microframeworks let you build an entire web application in a single file, usually with only one import statement. They are becoming increasingly popular for building small, self-contained applications that perform only one task—Service Oriented Architecture reborn as a combination of the Unix development philosophy and RESTful API design.

On my new homepage, a combined list of my tweets, bookmarks, and user comments on my site appear underneath my latest blog entries. I use a fun bit of Django code to pull these various items together, sorted by publication date, and I’d like to share how this bit of tumblelog-like functionality works.

mon propre service de redirections courtes. Ça prend une centaine de lignes en Python

On my Apache mod_wsgi setup, I got 235.65 requests per second. That was really good, I thought! However, with the Spawning setup, I got 347.20 requests per second.

another way of deploying WSGI apps with graceful code reloading.

Until recently, Pinax had two choices for a given external dependency:

1. use svn:externals and point to the external dependency's svn repository
2. include the external dependency code in the Pinax codebase

However, there are problems with this approach:

1. it largely relies on external dependencies being in svn and this is increasingly not the case (although it was when Pinax started)
2. it makes it difficult for Pinax itself to move away from svn
3. there is no management of dependencies between external dependencies, nor between particular projects in Pinax and their individual dependencies

To solve these problems and more, Pinax is switching to a distutils-based approach. This means:

1. externals dependencies are encouraged to be released as distutil-compliant packages with a valid setup.py and put on PyPI
2. development versions of dependencies can be pulled in in a variety of different ways including from git, hg or bzr repositories

svn:externals are evil

A world-class geographic web framework

Django using adapted to a GIS backend (like PostGIS)

Once we decide to go for PUT instead of POST, we step out the comfort zone of django, there is no mapped form filed, no validation, we have to deal with the raw WSGI interface by ourselves.