UsdUtils Pipeline docs example can't be parsed.

[ilpoldo]

Description of Issue

When pasting the config example from the UsdUtils Pipeline docs (source)

I get json parsing errors:

>>> from pxr import UsdUtils
>>> UsdUtils.GetRegisteredVariantSets()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
pxr.Tf.ErrorException: 
	Error in 'pxrInternal_v0_19__pxrReserved__::{anonymous}::_ReadPlugInfoObject' at line 182 in file /tmp/build/pxr/base/lib/plug/info.cpp : 'Plugin info file /user_data/my_plugin/plugInfo.json couldn't be read (line 9, col 31): Missing a comma or ']' after an array element.'

With a couple of syntax tweaks everything seems to work.

    "UsdUtilsPipeline": {
        "RegisteredVariantSets": {
            "modelingVariant": {
                "selectionExportPolicy": "always"
            },
            "standin": {
                "selectionExportPolicy": "never"
            }
        }
    }

Steps to Reproduce

1. copy the example from the docs in a plugInfo.json file in a folder (/user_data/my_plugin).
2. launch python picking up the plugin env PXR_PLUGINPATH_NAME=$PXR_PLUGINPATH_NAME:/user_data/my_plugin python
3. run from pxr import UsdUtils; UsdUtils.GetRegisteredVariantSets()

System Information (OS, Hardware)

CentOS Linux release 7.6.1810

Package Versions

USD 19.11

[ilpoldo]

I am using an old version of usd, but the example in the docs is still the same: https://openusd.org/dev/api/pipeline_8h.html

If it is of any help I can put a PR in. Really minor, but the example in the Kind docs https://openusd.org/dev/api/kind_page_front.html#mainpage_kind includes the outer "Info" key, which seems to be required for the registered variant sets too. Should the UsdUtils pipeline example match the scope and wording of the Kinds one?

[spiffmon]

Unless you already have a CLA in place, Leandro, it _may_ be easier for us to just fix it. Thanks for pointing it out - yes, it should be like the Kind plugInfo.

On Thu, Mar 16, 2023 at 1:34 PM Leandro Pedroni ***@***.***> wrote: I am using an old version of usd, but the example in the docs is still the same: https://openusd.org/dev/api/pipeline_8h.html If it is of any help I can put a PR in. Really minor, but the example in the Kind docs https://openusd.org/dev/api/kind_page_front.html#mainpage_kind includes the outer "Info" key, which seems to be required for the registered variant sets too. Should the UsdUtils pipeline example match the scope and wording of the Kinds one? — Reply to this email directly, view it on GitHub <#2346 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABPOU2CN3XOICJPKQLAV34LW4N2O3ANCNFSM6AAAAAAV5WLVPU> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- --spiffiPhone

[tallytalwar]

Filed as internal issue #USD-8133