CI: use latest Python 3.10 instead of 3.10.0

[messense]

No description provided.

[netlify]

✅ Deploy Preview for maturin-guide ready!

Name	Link
🔨 Latest commit	c40717e
🔍 Latest deploy log	https://app.netlify.com/sites/maturin-guide/deploys/635f3c1ae58e5900088e7463
😎 Deploy Preview	https://deploy-preview-1228--maturin-guide.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[messense]

"/LIBPATH:C:\hostedtoolcache\windows\Python\3.10.0\x64\libs"

Odd, it installed 3.10.8 but the LIBPATH refers to 3.10.0.

[messense]

 --- stdout
  cargo:rerun-if-env-changed=PYO3_CROSS
  cargo:rerun-if-env-changed=PYO3_CROSS_LIB_DIR
  cargo:rerun-if-env-changed=PYO3_CROSS_PYTHON_VERSION
  cargo:rerun-if-env-changed=PYO3_CROSS_PYTHON_IMPLEMENTATION
  cargo:rerun-if-env-changed=PYO3_PRINT_CONFIG

  -- PYO3_PRINT_CONFIG=1 is set, printing configuration and halting compile --
  implementation=CPython
  version=3.10
  shared=true
  abi3=false
  lib_name=python310
  lib_dir=C:\hostedtoolcache\windows\Python\3.10.0\x64\libs
  executable=D:\a\maturin\maturin\test-crates\venvs\develop-pyo3-mixed-py-subdir-cpython\Scripts\python.exe
  pointer_width=64
  build_flags=
  suppress_build_script_link_lines=false

$ test-crates\venvs\develop-pyo3-mixed-py-subdir-cpython\Scripts\python.exe --version
3.10.8

I don't understand...

[messense]

Update to pyo3 main branch seems to have fixed the issue, is there any change related I didn't know?

[davidhewitt]

Looks probably related to #1214?

[davidhewitt]

Update to pyo3 main branch seems to have fixed the issue, is there any change related I didn't know?

I... don't think so. Do you think there's a way to repro locally? I can try to help debug this.

[messense]

Yes, I want to isolate the problem first, the current CI setup doesn't really test all supported Python versions, I hope to expand it in #1214

I... don't think so. Do you think there's a way to repro locally? I can try to help debug this.

No, it's Windows x64 I don't have a working environment. I suspect it might related to build cache, 6cdee75 also passes cargo nextest run.

[davidhewitt]

I have a Windows x64 machine that I can run some stuff on later in the week if you have a recommendation of what I'll need to run? 😄

[messense]

if you have a recommendation of what I'll need to run?

Unfortunately I don't have a recommendation at the moment. Without ssh like remote login support, debugging Windows build on GitHub Actions is quite painful 😓. Actually looks like action-tmate supports Windows.

[davidhewitt]

Hmm ok. If I get some time mid-week I can try to run this on my windows machine, no guarantee!

[messense]

I think it's related to #1219 (comment) as well

runneradmin@fv-az319-905 MINGW64 /d/a/maturin/maturin/test-crates/targets/develop-pyo3-mixed-py-subdir/debug/build
# cat pyo3-build-config-c0fb8d48463d7859/out/pyo3-build-config.txt
implementation=CPython
version=3.10
shared=true
abi3=false
lib_name=python310
lib_dir=C:\hostedtoolcache\windows\Python\3.10.0\x64\libs
executable=D:\a\maturin\maturin\test-crates\venvs\develop-pyo3-mixed-py-subdir-cpython\Scripts\python.exe
pointer_width=64
build_flags=
suppress_build_script_link_lines=false

The 3.10.0 is definitely coming from this cached pyo3-build-config.txt file thus removing build cache makes it work.

[messense]

@davidhewitt I think the repro steps are:

• Create an venv with older Python version say 3.10.0 (or 3.9.x) then run maturin develop with a non-abi3 extension module
• Recreate the venv at the same path with a newer Python version say 3.10.8, run maturin develop again to trigger the build error

[messense]

For now we can workaround the issue by deleting the problematic caches.

[messense]

@davidhewitt I think the repro steps are:

• Create an venv with older Python version say 3.10.0 (or 3.9.x) then run maturin develop with a non-abi3 extension module
• Recreate the venv at the same path with a newer Python version say 3.10.8, run maturin develop again to trigger the build error

I have a repro for Linux in PyO3/pyo3#2724