I usually make a venv out of a matching Python version and then just inject the path into Mayapy...not what you're looking for I know but it was the compromise I found was easiest.
On Thursday, March 8, 2018 at 3:09:22 PM UTC-5, Robert White wrote: > > The only time I've gotten virtualenv to operate was using a custom python > build that matched the runtime environment of Maya (I was on windows, which > meant compiling with a newer compiler), and then manually doing the dirty > work to set all the paths and environment variables properly so that it > could find all the maya packages and dlls. > > In was a fun experiment, but felt like way more work than what I got out > of it. > > > On Thursday, March 8, 2018 at 12:17:08 PM UTC-6, James Deschenes wrote: >> >> Yeah that's what I'm beginning to understand as well. I also need to >> manage the plug-in environment as well as some other things which will >> likely go beyond the scope of Python virtual environments. Thanks for >> confirming my suspicions. >> > -- 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/891ade17-449f-4089-845f-9e50fe18dd76%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
