messense

That looks a lot like what [ouroboros](https://github.com/joshua-maros/ouroboros) does for self-referential struct.

I was able to get something working with [ouroboros](https://github.com/joshua-maros/ouroboros) using self-referential struct to remove the lifetime parameter: https://github.com/messense/crfs-rs/pull/3

Hitting this again in https://github.com/messense/tree-sitter-py/blob/05d5adde312afd22c8ac9f59f07731e17cf9a71a/src/lib.rs#L116-L122 but this time `ouroboros` can't help. The error message when uncommented is ``` error[E0495]: cannot infer an appropriate lifetime for autoref due to conflicting requirements...

Never tried running pyo3 code directly in virtualenv before. Here is a sysconfig dump of a venv in macOS ``` Platform: "macosx-11.2-arm64" Python version: "3.9" Current installation scheme: "posix_prefix" Paths:...

Something like this could work? ```diff diff --git a/src/gil.rs b/src/gil.rs index 37e0ed2495..397f9560b0 100644 --- a/src/gil.rs +++ b/src/gil.rs @@ -71,6 +71,28 @@ pub fn prepare_freethreaded_python() { if ffi::Py_IsInitialized() == 0 {...

Looks like PyPy doesn't support PEP 489. ``` = note: /usr/bin/ld: /home/runner/work/pyo3/pyo3/target/x86_64-unknown-linux-gnu/debug/deps/libpyo3-5c3820f48b335551.rlib(pyo3-5c3820f48b335551.pyo3.839e673f-cgu.2.rcgu.o): in function `pyo3_ffi::modsupport::PyModule_FromDefAndSpec': /home/runner/work/pyo3/pyo3/pyo3-ffi/src/modsupport.rs:146: undefined reference to `PyModule_FromDefAndSpec2' /usr/bin/ld: /home/runner/work/pyo3/pyo3/target/x86_64-unknown-linux-gnu/debug/deps/libpyo3-5c3820f48b335551.rlib(pyo3-5c3820f48b335551.pyo3.839e673f-cgu.5.rcgu.o): in function `pyo3::impl_::pymodule::ModuleDef::make_module': /home/runner/work/pyo3/pyo3/src/impl_/pymodule.rs:80: undefined reference to `PyModule_ExecDef'...

Maybe we should feature-gate it? See also https://github.com/cython/cython/issues/2343: > Require users to explicitly enable this feature with a compiler directive, as Cython cannot safely determine that a module supports this...

Looks like https://github.com/PyO3/pyo3/issues/1444

https://github.com/peaceiris/actions-gh-pages#%EF%B8%8F-keeping-existing-files-keep_files > With the v3, this option does not support working with the force_orphan option. The next major release (version 4) will support this Oops, `keep_files` does not work with...

Moving to Netlify will require a DNS change, but we can try it out first with Netlify subdomain.