docs: mention python _ctypes support #2383
Conversation
✅ Deploy Preview for dlt-hub-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
| ```sh | ||
| `python -c "import _ctypes"` | ||
| ``` | ||
| If this fails, you need to install the [libffi](https://sourceware.org/libffi/)-package |
There was a problem hiding this comment.
more context:
if libffi is mostly included by default,libffi-dev is for compiling software from source. when python versions are managed (and installed) with pyenv (at least thats how i did it), then python gets installed but without the _ctypes module.
There was a problem hiding this comment.
@djudjuu did you verify that this is also needed for python 3.12?
There was a problem hiding this comment.
I will verify it, but I dont want to mess with my system by removing the libffi-dev package, so I think I will use mutlipass to spin up fresh ubuntu images and test it there. Its probably a good thing to be able to do that anyways
There was a problem hiding this comment.
so I've verified that it occurs only if, you have build from source (e.g. using pyenv) (i tried with 3.12 and 3.13) when libffi-dev is not on the system. I am not sure this is a likely state, since usually libffi-dev is part of the packages that one has on the system if one compiles C stuff. But somehow that was the case for me, so maybe its not THAT unlikely.
during the 3.1x installation with pyenv I also did get a warning that C support was missing, so in some ways there already is a warning, so maybe this comment in the docs shouldnt be that prominent.
There was a problem hiding this comment.
not sure if that makes it necessary at all to mention it then...maybe lets discuss it live real quick
|
hmm. i am seeing my change locally, but when I click on the netllify-deploy preview its not there :/ |
you need to switch to the devel docs in the deployed preview to see your changes, check the button with the version on the top. |
closes #2382
UPDATE: maybe not that needed as its a bit of an edge case to and there is no fitting section in the docs (e.g. general troubleshooting). maybe having an issue with
_ctypestext is already some kind of hint for devs running into the same issue