#python dependencies

[simoluan]

the license to the rescue!

As an epilogue to my earlier quandary regarding dependencies, I may have found a good solution:

Just include the source code of the library within sims3py suite!

I can legally do this because the dependency in question is released with permissive Apache License 2.0. So, as long as I properly specify the 'credits' (including proper copyright attribution), and include the necessary LICENSE/NOTICE file(s) and explicitly state what changes (if any) I do to the code, I'm legally allowed to include the source code.

Problem solved ☺

Now, I still need to ensure that there will be NO dependency on binary libraries, before I can include the dependency in the sims3py suite, but that would be relatively a simple job.

[simoluan]

to depend or not to depend...

There's a class that might be very useful for sims3py. But using that class means sims3py is no longer independent, and now depends on an additional package. I'm torn between wanting to use that class, or just go my way without that class but causing the tools to (probably) run slower. Why is depending on a separate package not preferred? There are two reasons from my perspective. One, the package might rely on a binary library, and this might cause problems with cross-platform compatibility. Two, it forces users (and devs) to install "something else" before being able to run the tools in sims3tools. Without dependencies, sims3py can simply be extracted into a folder and executed using "python -m" from within the extraction directory.