QuickSearch 3.01 serial key or number

In Mozilla-based browsers, try creating a bookmark with URL (substituting with your Jira instance's URL) and keyword (such as 'j'). Now, typing 'j my open bugs' in the browser URL bar will search your Jira instance for your open bugs. Or simply type your search term in the Quick Search box, then right-click on the Quick Search box (with your search term shown) and select "Add a Keyword for this search...".

Note

It is necessary to specify to enabled pbr functionality.

Note

While one can pass any arguments supported by setuptools to setup(), any conflicting arguments supplied in setup.cfg will take precedence.

Note

Comments may be used in setup.cfg, however all comments should start with a # and may be on a single line, or in line, with at least one white space character immediately preceding the #. Semicolons are not a supported comment delimiter. For instance:

files¶

The section defines the install location of files in the package using three fundamental keys: , , and .

A list of top-level packages that should be installed. The behavior of packages is similar to in that it recurses the python package hierarchy below the given top level and installs all of it. If is not specified, it defaults to the value of the field given in the section.

Similar to , but is a list of packages that provide namespace packages.

A list of files to be installed. The format is an indented block that contains key value pairs which specify target directory and source file to install there. More than one source file for a directory may be indicated with a further indented list. Source files are stripped of leading directories. Additionally, pbr supports a simple file globbing syntax for installing entire directory structures, thus:

[files]data_files=etc/pbr=etc/pbr/*etc/neutron=etc/api-paste.inietc/dhcp-agent.inietc/init.d=neutron.init

will result in /etc/neutron containing api-paste.ini and dhcp-agent.ini, both of which pbr will expect to find in the etc directory in the root of the source tree. Additionally, neutron.init from that dir will be installed in /etc/init.d. All of the files and directories located under etc/pbr in the source tree will be installed into /etc/pbr.

Note that this behavior is relative to the effective root of the environment into which the packages are installed, so depending on available permissions this could be the actual system-wide /etc directory or just a top-level etc subdirectory of a virtualenv.

pbr¶

The section controls pbr specific options and behaviours.

A boolean option controlling whether pbr should generate an index of modules using sphinx-apidoc. By default, all files except setup.py are included, but this can be overridden using the option.

A list of modules to exclude when building documentation using sphinx-apidoc. Defaults to . Refer to the sphinx-apidoc man page for more information.

A boolean option controlling whether pbr should itself generates documentation for Python modules of the project. By default, all found Python modules are included; some of them can be excluded by listing them in .

A list of modules to exclude when building module documentation using pbr. fnmatch style pattern (e.g. myapp.tests.*) can be used.

build_sphinx¶

The section is a version of the setuptools plugin provided with Sphinx. This plugin extends the original plugin to add the following:

• Automatic generation of module documentation using the apidoc__ tool

• Automatic configuration of the project, version and release settings using information from pbr itself

• Support for multiple builders using the configuration option

  Note

  Sphinx 1.6 adds support for multiple builders using the default builder option. You should refer to this file for more information.

The version of provided by pbr provides a single additional option.

A space or comma separated list of builders to run. For example, to build both HTML and man page documentation, you would define the following in your setup.cfg:

[build_sphinx]builders=html,mansource-dir=doc/sourcebuild-dir=doc/buildall-files=1

For information on the remaining options, refer to the `Sphinx documentation`__. In addition, the , , and options in the section will affect the output of the automatic module documentation generation.

entry_points¶

The section defines entry points for generated console scripts and python libraries. This is actually provided by `setuptools`__ but is documented here owing to its importance.

The general syntax of specifying entry points is a top level name indicating the entry point group name, followed by one or more key value pairs naming the entry point to be installed. For instance:

Will cause a console script called pbr to be installed that executes the main function found in pbr.cmd. Additionally, two entry points will be installed for pbr.config.drivers, one called plain which maps to the Plain class in pbr.cfg.driver and one called fancy which maps to the Fancy class in pbr.cfg.driver.

Note

The ‘requirements-pyN.txt’ file is deprecated - ‘requirements.txt’ should be universal. You can use Environment markers for this purpose.

Extra requirements¶

Groups of optional dependencies, or “extra” requirements, can be described in your setup.cfg, rather than needing to be added to setup.py. An example (which also demonstrates the use of environment markers) is shown below.

Environment markers¶

Environment markers are conditional dependencies which can be added to the requirements (or to a group of extra requirements) automatically, depending on the environment the installer is running in. They can be added to requirements in the requirements file, or to extras defined in setup.cfg, but the format is slightly different for each.

For :

This will result in the package depending on only if it’s being installed into Python 2.6

For extras specified in setup.cfg, add an section. For instance, to create two groups of extra requirements with additional constraints on the environment, you can use: