If the tutorial just said plainly that the goal is to raise any exception if validation fails, that would be clear enough.
Not sure if you missed it, or if you think the current phrasing isn’t enough, but it does include that any exception is ok. “We indicate failure by throwing exceptions of any kind, including assertions.” http://forums.pyblish.com/t/learning-pyblish-by-example/108/15 Do you think there would be any value is splitting up the different types of processing for clarity? Funnily enough, this is how things started out. https://github.com/pyblish/pyblish/issues/127 DI got implemented on a provisional basis primarily to reduce the learning curve for beginners; not having to explain the Context and Asset concepts before writing your first plug-in. The hello world example would have been quite a bit more substantial without it, for example. Having said that, I am definitely open to alternatives. Here’s some of the current logic to preserve. 1. Process the world 2. Process sections of the world in isolation 3. Process sections based on their type It’s essentially three conflicting requirements that all must align for a plug-in to run. Given a plug-in architecture, where identical plug-ins may run in multiple environments, such as Maya and Houdini or standalone, how *could* this be implemented otherwise? -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CAFRtmOANWQALHbVppMzpuP%3DJ6oHanfzVtGEMLCmM6t9d85iC6g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
