Newbie control of an Existing Rez Install

[Saatchi3D]

I apologize for this newbie question(s). We need to migrate from Python 2 to Python 3 and Rez to current. First some details:

Air-gapped, Windows 10, VFX network
Rez: 2.16. Installed 2017(?)
Python 2.7

The programmer that installed and initially configured Rez is gone. I'm the team lead and am starting the migration process. My goal is to create a "stand alone" env with Python 3, and Qt/PySide for my team to use to do the migration and testing to Python 3.

I've installed Rez 2.83 and python 3.9 and, for the most part, the beginnings of a standalone env. I say "mostly", because references to rez 2.16 still show up in the pathing created by 'rez env' so I'm guessing I don't have rez 2.83 installed correctly.

My first question, of many, what is the proper upgrade procedure? I created a .cmd file that starts a new command session with the rez environment variables pointing to a local copy 2.83 and PATH set appropriately. This is so I can setup the test environment without disrupting my day to day work. I'm taking guesses and black boxing this whole migration process. If you can point me to doc, examples, give suggestions, that would be most helpful.

I am a big fan of Rez and am hoping that upgrading will improve some of the inherent performance issues with the set up environments (PATH and PYTHONPATH length). I've been reading some of the discussion on that on this forum. What ever I learn I can document and pass on to the rest of my team so the knowledge isn't lost again.

Thanks
John Morrison
3D Programmer - Lead
ThePub
Publicis Groupe

[davidlatwe]

I've installed Rez 2.83 and python 3.9 and, for the most part, the beginnings of a standalone env. I say "mostly", because references to rez 2.16 still show up in the pathing created by 'rez env'

Hi @Saatchi3D , could you provide a bit more detail on this ? You mean the the rez --version print out different version once inside a rez-env resolved context ?

[Saatchi3D]

Hi David. Sorry to be such a bad newbie. I found the problem and corrected it. I didn't update the forum entry. The old Rez was showing up in the PATH ahead of the new one. Here's why.... I created script (setupPy3.cmd) to START a new command session with the environment vars set for Rez 2.83, and the PATH pointing to Rez 2.83 and Python 3.9. Rez -V showed 2.83.0 as it should. Python -V showed 3.9 also as it should. This all worked fine until I did a rez env. At this point, since Rez STARTs a new command session, the old PATH which included Rez 2.16 got pulled back in. The correction was to remove Rez 2.16 from the PATH at the top (Windows) level so any session started would not get it. I then created an additional "setupPy2" script for Python 2 which included Rez 2.16. This solved the problem for me. We are working on the monumental task of converting from Python 2 to Python 3. I'm creating a test environment so the rest of my team can migrate our code base and apps. I hope the long-winded explanation above makes sense. I'll be back here again, I sure, as I run into issues due to lack of knowledge. Thank you. John Morrison

…

________________________________ From: David Lai ***@***.***> Sent: Friday, May 21, 2021 1:06 AM To: nerdvegas/rez ***@***.***> Cc: John Morrison ***@***.***>; Mention ***@***.***> Subject: Re: [nerdvegas/rez] Newbie control of an Existing Rez Install (#1069) This email has been sent from a source external to Publicis Groupe. Please use caution when clicking links or opening attachments. Cet email a été envoyé depuis une source externe à Publicis Groupe. Veuillez faire preuve de prudence lorsque vous cliquez sur des liens ou lorsque vous ouvrez des pièces jointes. I've installed Rez 2.83 and python 3.9 and, for the most part, the beginnings of a standalone env. I say "mostly", because references to rez 2.16 still show up in the pathing created by 'rez env' Hi @Saatchi3D<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSaatchi3D&data=04%7C01%7Cjohn.morrison%40saatchi.com%7Cd5b7de7477944b64117f08d91c2f477f%7Cd52c9ea17c2147b182a333a74b1f74b8%7C1%7C0%7C637571811659607774%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=RY0gsB8FizBXvebz3jV%2FPMlNpGqbkZAnAgCWPZb4Qeo%3D&reserved=0> , could you provide a bit more detail on this ? You mean the the rez --version print out different version once inside a rez-env resolved context ? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnerdvegas%2Frez%2Fdiscussions%2F1069%23discussioncomment-767089&data=04%7C01%7Cjohn.morrison%40saatchi.com%7Cd5b7de7477944b64117f08d91c2f477f%7Cd52c9ea17c2147b182a333a74b1f74b8%7C1%7C0%7C637571811659607774%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=QgeavKxSOinjRm9OnFegdHWCoiEOyexSxDDbktgwy4w%3D&reserved=0>, or unsubscribe<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAEBZ2GATOWWH6DR2LIDLOGDTOYH6XANCNFSM44HSDFOA&data=04%7C01%7Cjohn.morrison%40saatchi.com%7Cd5b7de7477944b64117f08d91c2f477f%7Cd52c9ea17c2147b182a333a74b1f74b8%7C1%7C0%7C637571811659617762%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=sBRm5rzAVmSi3ctG0F1jkOgdiM7wdzikWD%2FWhcuK8fQ%3D&reserved=0>.

------------------------------------------------------------------------ Disclaimer The information in this email and any attachments may contain proprietary and confidential information that is intended for the addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, retention or use of the contents of this information is prohibited. When addressed to our clients or vendors, any information contained in this e-mail or any attachments is subject to the terms and conditions in any governing contract. If you have received this e-mail in error, please immediately contact the sender and delete the e-mail.

[instinct-vfx]

For some context, the issue here is likely that Rez is actually pulling PATH from the registry rather than the parent shell. The reason is to make sure the Rez execution environment, the resolved environments and nested environments are strictly separated. If this was not the case you might end up in situations that have conflicting variants on PYTHONPATH for example.

[Saatchi3D]

Thanks Thorsten, If I had thought about it, I should have realized that Windows keeps the "official" PATH(s) in the registry. And I should have said that that was the PATH that I removed the Rez 2.16 pathing from. Thanks John Morrison

…

________________________________ From: Thorsten Kaufmann ***@***.***> Sent: Friday, May 21, 2021 9:47 AM To: nerdvegas/rez ***@***.***> Cc: John Morrison ***@***.***>; Mention ***@***.***> Subject: Re: [nerdvegas/rez] Newbie control of an Existing Rez Install (#1069) This email has been sent from a source external to Publicis Groupe. Please use caution when clicking links or opening attachments. Cet email a été envoyé depuis une source externe à Publicis Groupe. Veuillez faire preuve de prudence lorsque vous cliquez sur des liens ou lorsque vous ouvrez des pièces jointes. For some context, the issue here is likely that Rez is actually pulling PATH from the registry rather than the parent shell. The reason is to make sure the Rez execution environment, the resolved environments and nested environments are strictly separated. If this was not the case you might end up in situations that have conflicting variants on PYTHONPATH for example. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnerdvegas%2Frez%2Fdiscussions%2F1069%23discussioncomment-769277&data=04%7C01%7Cjohn.morrison%40saatchi.com%7C8e6adb5831994237b5e808d91c782da4%7Cd52c9ea17c2147b182a333a74b1f74b8%7C1%7C0%7C637572124769624454%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ajKpSmkLT3QwzqMvndPAZnK5Z3oYrJRxGxOcE%2FlWEd0%3D&reserved=0>, or unsubscribe<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAEBZ2GHKX6MXWFZFYNKCGFLTO2FDRANCNFSM44HSDFOA&data=04%7C01%7Cjohn.morrison%40saatchi.com%7C8e6adb5831994237b5e808d91c782da4%7Cd52c9ea17c2147b182a333a74b1f74b8%7C1%7C0%7C637572124769634450%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=pyu8cFnodakrmuxOZZ46wQPHSjGYawyBUDbLCuZr1Ws%3D&reserved=0>.

------------------------------------------------------------------------ Disclaimer The information in this email and any attachments may contain proprietary and confidential information that is intended for the addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, retention or use of the contents of this information is prohibited. When addressed to our clients or vendors, any information contained in this e-mail or any attachments is subject to the terms and conditions in any governing contract. If you have received this e-mail in error, please immediately contact the sender and delete the e-mail.