*Hey guys*, this is my first topic started on the mailing list and i use it to ask around about your habits concerning binary plugins (.mll) in your pipeline?
I recently felt like they are a huge pain to replace / version up since you cannot just delete and replace them as you could do with a python package as long as anybody in production has his Maya open and therefor the program has a handle to it. *A few solutions that quickly come to my mind:* *1. Control an env. var. that points to the binary plugin dir*. You can swap the directory in there for production and wait a few days (weeks...) till everybody closed his current Maya session.......Pretty unacceptable! *2. Force the handle to be removed with another program. (Unlocker etc.)*. That doesnt seem like a clean solution too me. What implications will that have to currently open Maya sessions? *3. Announce "Update Times" for the production* where people know they should close their Maya session for updates to be deployed and if they dont their session might crash because handles are removed forcibly.......Hmm, not too elegant either.. Maybe i am missing something very evident here? How do you handle the replacement/update of your binary plugin suite? (Not just for Maya but also Houdini, Nuke etc.) Cheers, Timm -- *Timm Wagener* *Technical Artist / 3D Generalist* *www.timmwagener.com <http://www.timmwagener.com>* Email: *[email protected] <[email protected]>* Phone: *0178-2810920* -- 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/CA%2Bj65ips9_s_w4-q%2BHPZ57RfBkajbgcYuq0FC5%3DGFv6e_Qzyxg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
