Ah, I didn’t think about this. Thanks for the explanation!

I like the problem solving description, I actually went through a similar learning process leading to bitset recently. It was very satisfying!

However, I just have to ask a question: What is the reason you didn’t just use UUID?

Since you have all your shutil.copytrees and sys.path manipulation at the top level of the test modules, they are executed the moment those modules are imported. unittest likely imports all discovered test modules before actually executing the tests so the set up of both modules is executed in random order before the tests are run. The correct way to perform test setup is using setUp and setUpClass methods of unittest.TestCase. Their counterparts tearDown and tearDownClass are used to clean up after tests. You probably will be able to get this to work somehow using those methods.

However, I’m fairly certain that this entire question is an example of the XY problem and you should be approaching this whole thing differently. Copying the modules and their mock dependencies into a temporary directory and manipulating sys.path seems like an absolute nightmare and it will be a massive PITA even if you get it to a working state. I don’t know what problem exactly you’re trying to solve but I think you should really read up on unittest.mock and even more importantly on dependency injection.

This is great news but I just have to say it: we need Proton Drive on Linux. Still very happy though.

Software development and computer stuff in general is my passion. I enjoy doing it as a hobby even after doing it at work. If I didn’t have to work for money, I would probably work on some open source software. In fact that’s kinda my dream / goal - achieve financial independence and work on open source as I please.

But… How do you even know you can smell ants? Why did you try it? Or can you smell them from meters away?