cachetool | CLI App and library to manage apc & opcache | Caching library

The error error: [Errno 2] No such file or directory: '/opt/anaconda3/lib/python3.8/site-packages/rtree/lib' was caused by py2app trying to build the program bundle using a non-existent interpreter. This means that even if you try to uninstall a manager like Anaconda, it still has option logs somewhere on your mac.

The fix:

1. Open the terminal and type the command type -a python.

• You will see similar lines

So in case anyone comes across similar for any reason with me encountering this probably due getting a new machine and IT doing their voodoo magic transferring my old stuff to this new machine.

Anyhow, there were a bunch of things I still needed to install after I got my new machine and i am not able to exactly pin point what caused issues from my question but in the end I was able to resolve. Follow me there below ...

Checking out my python.exe files I found 2 paths. First one added as environment variable

1. C:\Users-----\AppData\Local\Programs\Python\Python310
2. C:\Users----\AppData\Roaming\Python\Python310\

Second one not added. Adding roaming version to path variables did not solve the issue and gave additional errors instead: Fatal error in launcher: Unable to create process using '"C:\Program Files\Python310\python.exe"

So

1. I uninstalled python (done that before didnt help doing just that alone)

2. Deleted all environment variables pointing to python (here is what environment variables are just in case - https://www.computerhope.com/issues/ch000549.htm)

3. Uninstalled python extension from VS code (https://marketplace.visualstudio.com/items?itemName=ms-python.python)

4. Deleted Python folders mentioned in the two paths above

5. Then reinstalled python (clicked add to path during installation)

6. Reinstalled VS code python extension

7. Everything works now.

Best of luck

Sol 1 : In my case the problem was due exclusively to the "Queue Storage" function.
Once deleted from Local Sources, if I had managed to delete it from the APP Service everything would have worked again.
Sol 2: Sometimes issue in VSCode, I was building with with Python 3.7 even though 3.6 was installed. Uninstalling Python 3.7 and forcing 3.6 build resolved my issue.

For further ref1, ref2.

I reverted back to Xorg from wayland and its working, no more warnings

Here are the steps:

1. Disbled Wayland by uncommenting WaylandEnable=false in the /etc/gdm3/custom.conf
2. Add QT_QPA_PLATFORM=xcb in /etc/environment
3. Check whether you are on Wayland or Xorg using:

After a few days I was able to find the solution

Firstly, my code needed to be fixed to correctly call the params needed with the proper name

After doing some more research online I realized that installation of some packages is missed due to some existing packages. This issue helped me realize I need to reorder the position of google-cloud-tasks in my requirements.txt. So what I did was pretty simple, created a new virtualenv installed google-cloud-tasks as my first package and then installed everything else and finally the problem is solved.

Long story short the issue is the order in which packages are installed and that's why some packages are getting missed.

The problem was caused by jupyter/tensorflow being loaded in the background. The following solved the issue:

It happened the same to me last friday. I think it has something to do with Cuda instalation in Google Colab but I don't know exactly the reason

The error says MemoryError. You must upgrade your ec2 instance to something with more memory. tensorflow is very memory hungry application.