Here are some slides from a good talk by Martin Fowler about schemalessness and how there is always an 'implicit schema' http://martinfowler.com/articles/schemaless/

You can sort of do the same thing in just CSS by adding two small boxes as :after and :before pseudo elements.

See: http://i.imgur.com/aSnjEYx.png Not perfect, but pretty close.

Relevant SASS:

  $boxSize:30px

  &:hover:after, &:hover:before
    content: " "
    display: block
    position: absolute
    top: 50%
    right: -$boxSize
    height: $boxSize
    width: $boxSize
    background-color: transparent
    z-index: 1000
  
  &:hover:before
    right: auto
    left: -$boxSize

My normal settings structure is as follows:

  * settings/__init__.py
  * settings/base.py
  * settings/development.py
  * settings/staging.py.
  * settings/production.py
  * settings/credentials.py

This allows me to have a base settings file which the others inherit from, and all settings are tracked in git apart from passwords which are stored in credentials.py.

Unlike some other approaches, installed apps are just defined once (in the base), but apps can be added/removed for each environment.

Check out cuisine https://github.com/sebastien/cuisine It is a good companion for fabric to handle user creation and package installs.

More info after slide 42 here: http://www.slideshare.net/ffunction/fabric-cuisine-and-watch...

I am currently doing a similar sort of website, but trying to limit it to popular projects only. Also trying to group together a lot of the python 3 related articles and porting tips.

My current research can be found here: http://goo.gl/SCImr

Any corrections, or ideas for what can be on the site would be appreciated.

You're welcome to use content from https://bitbucket.org/pypy/compatibility. There is a growing list of dependencies at https://bitbucket.org/pypy/compatibility/wiki/depends.yaml.

That just saved me a hell of a lot of work. Thank you!

You're welcome. You can even clone that and make a wiki for py3k from it if you want. There's a script (in the wiki repo) to parse the wiki into YAML, so reuse of the current content should be easy no matter what format you want.