Daniele Nicolodi

> `//` should work, but perhaps it's more practical to just state that whatever the final number is, we apply either `round()` or `int()` to it? It depend on whether...

The issue is that the `+` operator forces the generic path (I don't know what the real object name is) returned by `py.get_install_dir()` to be coerced into a string. Therefore,...

Investigating the Meson side of things: `py.get_install_dir()` returns a `OptionString` object that inherits from the `String` object but holds a concrete path and a path wit placeholders for installation directories...

@eli-schwartz After reading the original reply (from the GitHub notification email) I thought that I didn't explain well what I meant. Reading the edited version of the reply, I'm not...

There is the precedent of `bool.to_string()` and `int.to_string()`. However, from the Meson documentation it seems that the users should not be aware of `OptionString` objects, which should behave as `str`...

I was just writing that `py.get_install_dir()` should be used in a few more place, with `install_subdir()` probably the most popular for installing Python packages. I would cover `install_subdir()` in the...

I don't think calling this a bug is fair. Cross compilation is not supported by the Python packaging ecosystem. And apparently "crossenv monkey patches some things" to make it work,...

The first obvious issue I can think about is that we use `sys.maxsize` to determine if the target Python interpreter is 32 or 64 bits. How do you plan to...

Well, meson-python implements PEP 517, which does not have any provision for cross-compiling. It assumes that the Python interpreter used for the build, is the one you are building for....

> So, there's a benefit to emulating just the json dumper and then running the rest of the build natively. I completely agree, but while it makes sense for Meson...