&dhucpackage; &dhsection;

&dhpackage;

Python XML Schema Bindings Generator

                &dhpackage;
                command
                [options]
                [more schema locations...]

## DESCRIPTION

This manual page documents briefly the `&dhpackage;` command.

This manual page was written for the &debian; distribution because the original program does not have a manual page.

`&dhpackage;` is a program that generates Python bindings from XML schema files or WSDL input.

## Generic Options

`--version`

- Show program’s version number and exit.

`--help`

- Show help message and exit.

## Identifying Schema

Specify and locate schema for which bindings should be generated.

`-u `FILE_or_URL`` `--schema-location=`FILE_or_URL``

- Add the location of an entrypoint schema. The provided value should be a URL. If it does not have a URL scheme (e.g., http:), it is assumed to be a file, and if it is not an absolute path is located relative to the schemaRoot.

`--schema-root=`DIRECTORY``

- The directory from which entrypoint schemas specified as relative file paths will be read.

`--schema-stripped-prefix=`TEXT``

- Optional string that is stripped from the beginning of schemaLocation values before loading from them. This applies only to the values of schemaLocation attributes in import and include elements. Its purpose is to convert absolute schema locations into relative ones to allow offline processing when all schema are available in a local directory. See schemaRoot.

`--location-prefix-rewrite=`TEXT``

- Add a rewrite entry for schema locations. Parameter values are strings of the form pfx=sub. The effect is that a schema location that begins with pfx is rewritten so that it instead begins with sub.

`--uri-content-archive-directory=`DIRECTORY``

- The directory path into which any content retrieved by URI will be written. This serves as a local cache, and to give you an opportunity to inspect material retrieved from some other system.

## Configuring Bindings

Specify where generated bindings should be written, and how they will be accessed from Python.

`-m `MODULE`` `--module=`MODULE``

- Add a module name corresponding to an entrypoint schema. The namespace defined by the corresponding schema will be written to a binding using the given module name, adjusted by modulePrefix.

`--module-prefix=`MODULE``

- The prefix for binding modules. The base name for the module holding a binding is taken from the moduleList, moduleMap, or an XMLNS prefix associated with the namespace in a containing schema. This value, if present, is used as a prefix to allow a deeper module hierarchy.

`--binding-root=`DIRECTORY``

- The directory path into which generated bindings will be written.

`--write-for-customization`

- Indicates whether the binding Python code should be written into a sub-module for customization. If enabled, a module path.to.namespace will be written to the file path/to/raw/namespace.py, so that the file path/to/namespace.py can import it and override behavior. This option turns on the feature.

`--no-write-for-customization`

- Indicates whether the binding Python code should be written into a sub- module for customization. If enabled, a module path.to.namespace will be written to the file path/to/raw/namespace.py, so that the file path/to/namespace.py can import it and override behavior. This option turns off the feature (default).

## SEE ALSO

pyxbdump(1), pyxbwsdl(1).

## AUTHOR

This manual page was written by &dhusername; &dhemail; for the &debian; system (and may be used by others). Permission is granted to copy, distribute and/or modify this document under the terms of the &gnu; General Public License, Version 2 any later version published by the Free Software Foundation.

On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL.

manpage.1'. You may view the manual page with: `docbook-to-man manpage.sgml | nroff -man | less'. A typical entry in a Makefile or Makefile.am is: manpage.1: manpage.sgml docbook-to-man $< > $@ The docbook-to-man binary is found in the docbook-to-man package. Please remember that if you create the nroff version in one of the debian/rules file targets (such as build), you will need to include docbook-to-man in your Build-Depends control field. --> Michael"> Fladischer"> 12 July 2013"> 1"> FladischerMichael@fladi.at"> CELERY"> Debian"> GNU"> GPL"> ]>
&dhucpackage; &dhsection;

&dhpackage;

Celery Worker Daemon

                &dhpackage;
                command

                -A/--app=APP
                -b/--broker=BROKER
                --loader=LOADER
                --config=CONFIG
                --workdir=WORKING_DIRECTORY
                -q/--quiet
                -C/--no-color
                --version
                --help

## DESCRIPTION

This manual page documents briefly the `&dhpackage;` command.

This manual page was written for the &debian; distribution because the original program does not have a manual page.

`&dhpackage;` is a program that manages the Celery Worker Daemons and their queues.

## COMMANDS

All inspect commands supports a --timeout argument, This is the number of seconds to wait for responses. You may have to increase this timeout if you’re not getting a response due to latency.

shell

- Drop into a Python shell. The locals will include the celery variable, which is the current app. Also all known tasks will be automatically added to locals (unless the --without-tasks flag is set). Uses Ipython, bpython, or regular python in that order if installed. You can force an implementation using --force-ipython|-I, --force-bpython|-B, or --force-python|-P.

status

- List active nodes in this cluster.

result `-t `task name`` `uuid`

- Show the result of a task. Note that you can omit the name of the task as long as the task doesn’t use a custom result backend.

purge

- Purge messages from all configured task queues. Warning: There is no undo for this operation, and messages will be permanently deleted!

inspect active

- List active tasks. These are all the tasks that are currently being executed.

inspect scheduled

- List scheduled ETA tasks. These are tasks reserved by the worker because they have the eta or countdown argument set.

inspect reserved

- List reserved tasks. This will list all tasks that have been prefetched by the worker, and is currently waiting to be executed (does not include tasks with an eta).

inspect revoked

- List history of revoked tasks.

inspect registered

- List registered tasks.

inspect stats

- Show worker statistics.

control enable_events

- Enable events.

control disable_events

- Disable events.

migrate `from` `to`

- Migrate tasks from one broker to another (EXPERIMENTAL). This command will migrate all the tasks on one broker to another. As this command is new and experimental you should be sure to have a backup of the data before proceeding. The value for each broker should be a URL.

## OPTIONS

This program follows the usual &gnu; command line syntax, with long options starting with two dashes (`-'). A summary of options is included below.

`-A `APP`` `--app=`APP``

- App instance to use (e.g. module.attr_name).

`-b `BROKER`` `--broker=`BROKER``

- URL to the broker. Default is 'amqp://guest@localhost//'.

`--loader=`LOADER``

- name of custom loader class to use.

`--config=`CONFIG``

- Name of the configuration module.

`--workdir=`WORKING_DIRECTORY``

- Optional directory to change to after detaching.

`--quiet`

`-C` `--no-color`

`--version`

- Show program's version number and exit.

`-h` `--help`

- Show help message and exit.

## Reading Namespace Archives

Locating and loading (or inhibiting load of) namespace archives.

`--archive-path=`PATH``

- A colon-separated list of paths from which namespace archives can be read. The default path is the contents of the PYXB_ARCHIVE_PATH environment variable, or the standard path configured at installation time. Any file with the extension .wxs found in one of these directories is examined to see whether it is a namespace archive.

`--pre-load-archive=`FILE``

- Name of a file containing a stored archive from which namespaces should be read prior to processing schema. Files to be pre-loaded are not affected by noLoadNamespace.

`--no-load-namespace=`URI``

- Mark that the specified namespace should not be loaded from an archive. Use this when you are generating bindings for an application that has a restricted profile of a namespace that would otherwise be read from an archive. Be aware that this removes any knowledge of any archive in which this namespace is present as a non-private member.

## Writing Namespace Archives

Control the location and content of a namespace archive corresponding to a binding generation.

`--archive-to-file=`FILE``

- Optional file into which the archive of namespaces will be written. Subsequent generation actions can read pre-parsed namespaces from this file, and therefore reference the bindings that were built earlier rather than re-generating them. The file name should normally end with .wxs.

`--public-namespace=`URI``

- Indicates, for specific namespaces, whether their visibility in the archive should be public or private. This option adds the namespace as a public archive member.

`--private-namespace=`URI``

- Indicates, for specific namespaces, whether their visibility in the archive should be public or private. This option adds the namespace as a private archive member.

`--default-namespace-public`

- Indicates whether unmentioned namespaces will be public or private (default) in the archive. A namespace is mentioned if it is the target namespace of an entrypoint schema, or appears in a namespace visibility specification. I.e., this default applies only to namespaces that are modified as a result of including some schema, which is generally a local customization of something. This option makes the default public (default).

`--default-namespace-private`

- Indicates whether unmentioned namespaces will be public or private (default) in the archive. A namespace is mentioned if it is the target namespace of an entrypoint schema, or appears in a namespace visibility specification. I.e., this default applies only to namespaces that are modified as a result of including some schema, which is generally a local customization of something. This option makes the default private.

## Configuring Binding Code Generation

Control the style and content of the generated bindings. This is not well-supported, and you are advised to pretend these options don’t exist.

`--validate-changes`

- Indicates whether the bindings should validate mutations against the content model. This option turns on validation (default).

`--no-validate-changes`

- Indicates whether the bindings should validate mutations against the content model. This option turns off validation.

## Miscellaneous Options

`--logging-config-file=`FILE``

- A file provided to L{logging.config.fileConfig} to control log messages. In the absence of other configuration the Python standard logging infrastructure is used in its default configuration.

## WSDL Options

Options relevant to generating bindings from WSDL service descriptions.

`-W `FILE_or_URL`` `--wsdl-location=`FILE_or_URL``

- Generate bindings for the types stanza of the WSDL at this location. This option is equivalent to retrieving the WSDL, extracting the schema part of its types block to a file, and using that file as a --schema-location.

## SEE ALSO

pyxbdump(1), pyxbwsdl(1).

## AUTHOR

This manual page was written by &dhusername; &dhemail; for the &debian; system (and may be used by others). Permission is granted to copy, distribute and/or modify this document under the terms of the &gnu; General Public License, Version 2 any later version published by the Free Software Foundation.

On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL.