cross-posted from: https://sh.itjust.works/post/27097438

I store my programs in a cryptomator vault which uses a fuse virtual drive (The default on Linux), but when trying to update pip inside a venv I get an error, then any subsequent use of pip also throws an error and {path_to_venv}/lib/python3.12/site-packages/pip/ becomes empty.

I imagine this is an issue that would happen in any FUSE drive although I don't know how to test that.

Here are the logs

• OS : Fedora 40
• pip version: 23.3.2 updating to 24.2
• python version: 3.12.7

I already made a bug report on the github

Does anyone know a temporary workaround for this ?

Do you know libraries to write simple guis that are flexible and largely adopted so I can find guides and examples? No need to design any part of it, just a rigid table-like carcass for buttons and elements.

I'm yet to dip my toe in anything graphical, but I thought that my current learning project could use a simple interface. I'm just afraid I'd give up if it would be too complicated to implement and wire to my now terminal-controlled code.

Can you suggest something for a beginner?

Hi, I'm trying to save a plotly image as a static .svg file using kaleido. I have kaleido-0.2.1 installed, but when I run this code on jupyter: fig1.write_image("../figures/supp1A.svg", format="svg", engine="kaleido")
I get this error:

ValueError: 
Image export using the "kaleido" engine requires the kaleido package,
which can be installed using pip:
    $ pip install -U kaleido

Why does this happens even tho kaleido is installed?

I saw a previous post saying "hey, we'll help you with problems." I have a problem! I dunno if its python.

I'm trying to damn install a kernel driver so that my Cintiq 16 works on Nobara OS.

• I follow this site: https://github.com/linuxwacom/input-wacom/wiki/Installing-input-wacom-from-source

• I input this command: if test -x ./autogen.sh; then ./autogen.sh; else ./configure; fi && make && sudo make install || echo "Build Failed"

I get this error: BUILD ENVIRONMENT: linux kernel - yes 4.5 kernel source - yes /lib/modules/6.3.7-200.fsync.fc37.x86_64/source

NOTE: The kernel drivers included in this package are only tested with the X Wacom driver built from xf86-input-wacom. If you are running an X server version older than 1.7, please use the drivers provided by the linuxwacom package.

Please run 'make && make install'. make all-recursive make[1]: Entering directory '/home/USER/Downloads/Figuring_out_Wacom/input-wacom-1.0.0' Making all in 4.5 make[2]: Entering directory '/home/USER/Downloads/Figuring_out_Wacom/input-wacom-1.0.0/4.5' Building input-wacom drivers for 4.5 kernel. make -C /lib/modules/6.3.7-200.fsync.fc37.x86_64/source M=/home/USER/Downloads/Figuring_out_Wacom/input-wacom-1.0.0/4.5 make[3]: Entering directory '/usr/src/kernels/6.3.7-200.fsync.fc37.x86_64' CC [M] /home/USER/Downloads/Figuring_out_Wacom/input-wacom-1.0.0/4.5/wacom_sys.o /home/USER/Downloads/Figuring_out_Wacom/input-wacom-1.0.0/4.5/wacom_sys.c: In function ‘wacom_update_name’: /home/USER/Downloads/Figuring_out_Wacom/input-wacom-1.0.0/4.5/wacom_sys.c:38:41: error: implicit declaration of function ‘hid_is_using_ll_driver’; did you mean ‘wacom_is_using_usb_driver’? [-Werror=implicit-function-declaration] 38 | #define wacom_is_using_usb_driver(hdev) hid_is_using_ll_driver(hdev, &usb_hid_driver) | ^~~~~~~~~~~~~~~~~~~~~~ /home/USERr/Downloads/Figuring_out_Wacom/input-wacom-1.0.0/4.5/wacom_sys.c:2275:21: note: in expansion of macro ‘wacom_is_using_usb_driver’ 2275 | if (wacom_is_using_usb_driver(wacom->hdev)) { | ^~~~~~~~~~~~~~~~~~~~~~~~~ /home/USER/Downloads/Figuring_out_Wacom/input-wacom-1.0.0/4.5/wacom_sys.c:38:71: error: ‘usb_hid_driver’ undeclared (first use in this function); did you mean ‘to_hid_driver’? 38 | com_is_using_usb_driver(hdev) hid_is_using_ll_driver(hdev, &usb_hid_driver) | ^~~~~~~~~~~~~~

/home/USER/Downloads/Figuring_out_Wacom/input-wacom-1.0.0/4.5/wacom_sys.c:2275:21: note: in expansion of macro ‘wacom_is_using_usb_driver’ 2275 | if (wacom_is_using_usb_driver(wacom->hdev)) { | ^~~~~~~~~~~~~~~~~~~~~~~~~ /home/USER/Downloads/Figuring_out_Wacom/input-wacom-1.0.0/4.5/wacom_sys.c:38:71: note: each undeclared identifier is reported only once for each function it appears in 38 | com_is_using_usb_driver(hdev) hid_is_using_ll_driver(hdev, &usb_hid_driver) | ^~~~~~~~~~~~~~

/home/USER/Downloads/Figuring_out_Wacom/input-wacom-1.0.0/4.5/wacom_sys.c:2275:21: note: in expansion of macro ‘wacom_is_using_usb_driver’ 2275 | if (wacom_is_using_usb_driver(wacom->hdev)) { | ^~~~~~~~~~~~~~~~~~~~~~~~~ /home/USER/Downloads/Figuring_out_Wacom/input-wacom-1.0.0/4.5/wacom_sys.c: In function ‘wacom_probe’: /home/USER/Downloads/Figuring_out_Wacom/input-wacom-1.0.0/4.5/wacom_sys.c:38:71: error: ‘usb_hid_driver’ undeclared (first use in this function); did you mean ‘to_hid_driver’? 38 | com_is_using_usb_driver(hdev) hid_is_using_ll_driver(hdev, &usb_hid_driver) | ^~~~~~~~~~~~~~

/home/USER/Downloads/Figuring_out_Wacom/input-wacom-1.0.0/4.5/wacom_sys.c:2829:13: note: in expansion of macro ‘wacom_is_using_usb_driver’ 2829 | if (wacom_is_using_usb_driver(hdev)) { | ^~~~~~~~~~~~~~~~~~~~~~~~~ cc1: some warnings being treated as errors make[4]: *** [scripts/Makefile.build:252: /home/USER/Downloads/Figuring_out_Wacom/input-wacom-1.0.0/4.5/wacom_sys.o] Error 1 make[3]: *** [Makefile:2037: /home/USER/Downloads/Figuring_out_Wacom/input-wacom-1.0.0/4.5] Error 2 make[3]: Leaving directory '/usr/src/kernels/6.3.7-200.fsync.fc37.x86_64' make[2]: *** [Makefile:43: all] Error 2 make[2]: Leaving directory '/home/USER/Downloads/Figuring_out_Wacom/input-wacom-1.0.0/4.5' make[1]: *** [Makefile:372: all-recursive] Error 1 make[1]: Leaving directory '/home/USER/Downloads/Figuring_out_Wacom/input-wacom-1.0.0' make: *** [Makefile:307: all] Error 2 Build Failed [[email protected]]$

... If anybody understands why it fails at line 38 and 2275 and so forth, please halp!

I started python almost 10 years ago now (jesus that makes me feel old). During that time, r/learnpython was incredibly helpful in that journey, and I learned a lot from the folks there.

I can't wait to build the same thing here, and I want to offer my services as best I can to do so. If you have an issue, question or problem, post! You can reply here if it's just a quick clarification, but feel free to make your own post and include your code. I'll do my best to read it when I can and give any help I can. I don't have "all the knowledge" - but I'm pretty proud of myself for being a near expert with the language.

So hit me, how can I help?