Skip to main content
This is a pre-production deployment of Warehouse. Changes made here affect the production instance of PyPI (pypi.python.org).
Help us improve Python packaging - Donate today!

Buildout recipe to set and get environment variables.

Project Description

Overview

This recipe allows to set and get environment variables during the execution of a buildout.

The recipe mirrors the current environment variables into its section, so that e.g. ${environment:USER} will give the current user.

To set an environment variable you just set it in the section.

The environment variables are set and get during the initialization of the Recipe instance, i.e. after buildout.cfg is read but before any recipe is installed or updated.

Example usage: Use an environment variable

We’ll start by creating a buildout that uses the recipe:

>>> write('buildout.cfg',
... """
... [buildout]
... parts = environment print
...
... [some-section]
... some-option = ${environment:SOME_VARIABLE}
...
... [environment]
... recipe = collective.recipe.environment
...
... [print]
... recipe = mr.scripty
... install =
...     ... print(self.buildout['some-section']['some-option'])
...     ... return []
... """)

The mr.scripty recipe is used to print out the value of the ${some-section:some-option} option.

Now we set the environment variable:

>>> import os
>>> os.environ['SOME_VARIABLE'] = 'some_value'

Running the buildout gives us:

>>> run_buildout()
START...
some_value
...END

Example usage: Set an environment variable

We’ll start by creating a buildout that uses the recipe:

>>> write('buildout.cfg',
... """
... [buildout]
... parts = environment print
...
... [some-section]
... some-option = value2
...
... [environment]
... recipe = collective.recipe.environment
... var1 = value1
... var2 = ${some-section:some-option}
...
... [print]
... recipe = mr.scripty
... install =
...     ... import os
...     ... for var in ('var1', 'var2'):
...     ...     print('%s = %s' % (var, os.environ[var]))
...     ... return []
... """)

The mr.scripty recipe is used to print out the values of the environment variables.

Running the buildout gives us:

>>> run_buildout()
START...
var1 = value1
var2 = value2
...END

Similar recipes

The functionality to mirror the environment variables into the recipe’s section is largely copied from gocept.recipe.env.

Regression test: Values containing variable substitution syntax breaks things

Problem: if an environment variable value contains something looking like variable substitution in Buildout syntax then things break. We fix this by escaping the variable substitutions using two dollar signs. Eg.: ${foo} becomes $${foo}.

Let’s see if it works.

Set environment variables:

>>> os.environ['PROBLEM_VAR_1'] = '${foo}'
>>> os.environ['PROBLEM_VAR_2'] = '${foo:bar}'
>>> os.environ['PROBLEM_VAR_3'] = 'Contains ${foo} and also ${foo:bar}.'
>>> os.environ['LEGAL_VAR_1'] = '$foo'
>>> os.environ['LEGAL_VAR_2'] = '{foo}'

Write a buildout using those variables:

>>> write('buildout.cfg',
... """
... [buildout]
... parts = environment print
...
... [some-section]
... option-1 = ${environment:PROBLEM_VAR_1}
... option-2 = ${environment:PROBLEM_VAR_2}
... option-3 = ${environment:PROBLEM_VAR_3}
... option-4 = ${environment:LEGAL_VAR_1}
... option-5 = ${environment:LEGAL_VAR_2}
...
... [environment]
... recipe = collective.recipe.environment
...
... [print]
... recipe = mr.scripty
... install =
...     ... section = self.buildout['some-section']
...     ... for (k, v) in sorted(section.items()):
...     ...     print('{} = {}'.format(k, v))
...     ... return []
...
... """)

Running the buildout gives us:

>>> run_buildout()
START...
option-1 = $${foo}
option-2 = $${foo:bar}
option-3 = Contains $${foo} and also $${foo:bar}.
option-4 = $foo
option-5 = {foo}
...END

Changelog

1.1.0 (2017-07-27)

New features:

  • Fix code for Python 3 compatiblity. [cas–]

1.0.0 (2017-07-20)

Breaking changes:

  • Fix bug: Values containing variable substitution syntax breaks things. This is a breaking change because problematic values are escaped, eg. “${foo}” becomes “$${foo}”.

0.2.0 (2012-08-21)

  • Now it’s possible to read environment variables.

0.1b1 (2011-08-18)

  • First release.
Release History

Release History

This version
History Node

1.1.0

History Node

1.0.0

History Node

0.2.0

History Node

0.1b1

Download Files

Download Files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
collective.recipe.environment-1.1.0.tar.gz (5.4 kB) Copy SHA256 Checksum SHA256 Source Jul 27, 2017

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting