- Incrementing didn't work properly when extending multiple files.
  https://bugs.launchpad.net/zc.buildout/+bug/421022

  The standard Python -m option didn't work for custom interpreters.

  Scripts run using generated interpreters didn't have __file__ set correctly.

  Scripts generated with relative-paths eanbled couldn't be
  symbolocally linked to other locations and still work.

  Option incrementing and decrementing didn't work for options
  specified on the command line.

No commit message

- When doing variable substitutions, you can omit the section name to
  refer to a variable in the same section (e.g. ${:foo}).

- When doing variable substitution, you can use the special option,
  ``_buildout_section_name_`` to get the section name.  This is most handy
  for getting the current section name (e.g. ${:_buildout_section_name_}).

- A new special option, ``<`` allows sections to be used as macros.

refer to a variable in the same section (e.g. ${:foo}).

When doing variable substitution, you can use the special option,
``_buildout_section_name_`` to get the section name.  This is most handy
for getting the current section name (e.g. ${:_buildout_section_name_}.

(Also removed some extra imports and made formatting changes.)

Conflicts:
	CHANGES.txt
	src/zc/buildout/buildout.py

  could be inserted into sys.path if a relative path was used to run
  the generated script.

Also fixed some spurious failures in the bootstrap test.

``zc.buildout.testing.buildoutSetUp`` installs a new handler in the python root logging facility. This handler is now removed during tear down as it might disturb other packages reusing buildout's testing infrastructure.

isn't really stable (failing tests, hanging test)

o Avoids deprecation warnings in Python 2.6.  See:

  http://docs.python.org/library/subprocess.html#replacing-os-popen-os-popen2-os-popen3

  [buildout]
  develop = ./local-checkouts/*

  of md5 module, which is deprecated in Python 2.6.

Signed-off-by: Georgy Berdyshev - Георгий Бердышев <codingmaster@gmail.com>

- Of course, it only makes sense to run this test if os.symlink exists.
  Also, add an entry to CHANGES.txt

  substitutions are used to name standard directories, as in::

[buildout]
    eggs-directory = ${buildout:directory}/develop-eggs