On Tue, Nov 14, 2017, 1:53 AM Panupat Chongstitwattana
wrote:
> Thank you Justin! You're right env.dic was my mistake.
>
> Is the security risk a thing we should be concerned in a studio
> environment? Im trying to set up a system that would load the correct
> version of plug-ins for each projec
On Tue, Nov 14, 2017, 6:01 AM johan Borgström wrote:
> Hi,
>
> I am testing Sphinx and the autodoc feature. It seems like no
> documentation is generated when a class is extending a mocked module. (In
> my conf.py i am using autodoc_mock_imports = ['pymel', 'pyside2'])
>
> Does anyone have any ti
Hi,
I am testing Sphinx and the autodoc feature. It seems like no documentation
is generated when a class is extending a mocked module. (In my conf.py i am
using autodoc_mock_imports = ['pymel', 'pyside2'])
Does anyone have any tips for generating docs for mocked modules?
Best,
Johan
--
You
Thank you Justin! You're right env.dic was my mistake.
Is the security risk a thing we should be concerned in a studio environment?
Im trying to set up a system that would load the correct version of plug-ins
for each project by launching Maya with custom Env.
--
You received this message bec
Hello Michael,
Thanks for the support on this it is much appreciated.
I was not aware that I was using API 1.0, I have been reading the C++ docs
for my reference so I assumed it was the correct API. I will make the
switch to 2.0.
The selection of the UVs is just a visual test to check that I am
