pyecoregen 0.5.1

Command line interface

After installation an executable script pyecoregen has been installed. Assuming library.ecore is your Ecore XMI file, and you want to generate the classes in some/folder, you can do:

$ pyecoregen -vv -e library.ecore -o some/folder

The -vv is optional to raise verbosity to log level DEBUG. You should see output like this:

2017-05-26 08:06:54,303 INFO [multigen.generator] Generating code to '/here/some/folder'.
2017-05-26 08:06:54,304 DEBUG [multigen.generator] <pyecore.ecore.EPackage object at 0x000001DCF3C61E80> --> '/here/some/folder/library/__init__.py'
2017-05-26 08:06:54,363 DEBUG [multigen.generator] <pyecore.ecore.EPackage object at 0x000001DCF3C61E80> --> '/here/some/folder/library/library.py'

The pyecoregen command line interface also allows you to generate the classes from a remote Ecore XMI file if its “path” starts with http(s)://. The usage does not change:

$ pyecoregen -e "http://path/towards/my/ecore" -o some/folder

Programmatic interface

If you need to generate code from an in-memory representation of a pyecore model, you instantiate the EcoreGenerator class and call the generate method. Assuming you have loaded above model and hold it’s root package in library_pkg, you would generate with:

generator = EcoreGenerator()
generator.generate(library_pkg, 'some/folder')

Generator options

The end user can control some of the features how the metamodel code is generated. This can be done at the command line as well as via programmatic invocation. A command line parameter --my-param is then turning into a keyword argument my_param.

--auto-register-package (Default: False)

If enabled, the generated packages are automatically added to pyecore’s global namespace registry, which makes them available during XMI deserialization.

--user-module (Default: None)

If specified, the given string is interpreted as a dotted Python module path. E.g. --user-module my.custom_mod will make the generated code import mixin classes from a module my.custom_mod. A generated class with name <name> then derives from a mixin <name>Mixin, which is expected to be part of the user module. If this option is used, the generator also produces a skeleton file which contains all required mixin classes and methods. Usually you copy parts of this template to your own module, which is then checked into version control all your other code.

--with-dependencies (Default: False)

If enabled, the generator also generates code from all metamodels that are dependencies of the input metamodel. A metamodel dependency is typically a reference from the input metamodel to another .ecore file. Please note that this option introduces slower code generation as all metamodels must be scanned in order to determine dependencies.