clib | a c library for rapid development | Infrastructure Automation library

Is this a good idea or possible to do?

No, that won't work because the C library - for obvious reasons - doesn't define the functions etc. within that namespace.

Why doesn't anybody seem to do it?

Because it doesn't work.

If you give up the desire to have a header-only wrapper library, then you can avoid "leaking" the C header since you could include it only within a translation unit of the wrapper library.

Note that this still doesn't solve all problems with name clashes since One Definition Rule applies across translation unit boundaries. If you link with a C library, then the external names of that library cannot be used by anything else. Hiding the C header does prevent macro-pollution.

I had this issue as well and for me installing pip packages with python -m pip install worked. So python -m pip install --upgrade pip==20.2 should work for you.

See here:

Got it to work by loading the pretrained model locally instead of from the hub.

My compliments on such an extensive report. Your issue lies probably in this weird setup you've got going on.

You don't say what version of ZeroBrane Studio you are using, but you'll need to use the latest one from the master branch in the repository, as there have been several openresty-related fixes applied to the debugger and merged recently .

Your wsgi.py had a wrong setting for the settings location

Change

Notice, you're getting a linker error, not a compile time error. Everything is fine as far as compilation goes, but you have not done quite enough to satisfy the entire toolchain. The issue is, you never gave a definition for the variable, and the linker fails to find it when it brings everything together.

This issue would go away if you were compiling with c++ 17. What is happening is that when you pass a.sprite to a function, the array decays to a pointer type (to the first element) and since it must have an address, is considered odr used. This means that the variable must have an unambiguous location in your application, and thus be explicitly declared (like any normal static variable that is odr-used.)

For static members of a class, if they are odr-used, they must be declared in one place in the application, usually in a cpp file:

We can use os module to create the pip list, then we use pandas.read_csv with \s+ as seperator to read the pip list into a dataframe:

The usual reason for problems with ctypes is not defining .argtypes and .restype for the functions being called. In particular, the return type defaults to an c_int (typically 32-bit) and on a 64-bit system your function would return a 64-bit pointer.