David Reilly
David Reilly
This is something I've noticed with discord relative timestamps in general. Even if you do time = 0 it will say Dec 31 1969.
Oddly, even using -DCLANG_INSTALL_PREFIX=/usr/lib/llvm-3.8 -DLibclang_LIBRARY=/usr/lib/llvm-3.8/lib/libclang-3.8.so.1 -DLibclang_INCLUDE_DIR=/usr/lib/llvm-3.8/include as mentioned above to force the use of LLVM/Clang 3.8, it still somehow ended up using LLVM 8 (with -I/usr/lib/llvm-8/include being the telltale sign)...
> Why prefer LLVM 3.8 to LLVM 8? Only because I mistakenly thought that was the recommended version and didn't want two LLVM's taking up space. :) It's working now...
I like the logo. Thanks for sending it @AABur !
>  How about this logo? What's the license for the logo?
Note: I think the teason for this might be that we have imported lru_cache in a different file. Howver, it seems that it should not be registering as a duplicate?...
Also, I converted the error to a warning for the moment, but feel free to change it back if you want
Make relative imports and use(relative_path) work inside a module pulled from the web - use(git(..))
Would we need to add something to sys.meta_path to enable us to dynamically download and resolve these imports, probably at the very end of the list so that any possible...
Make relative imports and use(relative_path) work inside a module pulled from the web - use(git(..))
Clarifying my above comment with some API details: Our special resolver is actually a `finder` with one method: ```python def find_module(abs_name: str, parent_pkg_path: str = None) -> loader: ``` -...
@jonbesga @pavlukivan Were you able to use it at all, or did it immediately show the error? Incidentally, I've been trying to recover the maze editor source code, so there's...