Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"assertion failed: (left != right)" when initializing module #223

Closed
msanders opened this issue Sep 14, 2018 · 5 comments
Closed

"assertion failed: (left != right)" when initializing module #223

msanders opened this issue Sep 14, 2018 · 5 comments

Comments

@msanders
Copy link
Contributor

msanders commented Sep 14, 2018

🌍 Environment

  • macOS High Sierra
  • Your python version: 3.6 & 3.5
  • Python installation method: pyenv
  • Rust version: rustc 1.30.0-nightly (28bcffead 2018-09-01)
  • Are you using the latest pyo3 version? Have you tried using latest master (replace version = "0.x.y" with git = "https://github.com/PyO3/pyo3")?Yes, 0.4.1

💥 Reproducing

Hi, I'm running into the following assertion when compiling a module built via cibuildwheel using pyo3:

~ $ env RUST_BACKTRACE=1 pip uninstall -y autopy; and pip install --index-url https://test.pypi.org/simple/ autopy==1.0.1.dev48; and python -c 'import autopy'
Uninstalling autopy-1.0.1.dev48:
  Successfully uninstalled autopy-1.0.1.dev48
Looking in indexes: https://test.pypi.org/simple/
Collecting autopy==1.0.1.dev48
  Using cached https://test-files.pythonhosted.org/packages/90/63/2df192feed68c4c923f130f317fe94c0a5be79301b9a913e7659481f60e9/autopy-1.0.1.dev48-cp35-cp35m-macosx_10_6_intel.whl
Installing collected packages: autopy
Successfully installed autopy-1.0.1.dev48
thread '<unnamed>' panicked at 'assertion failed: `(left != right)`
  left: `0`,
 right: `0`', /Users/travis/.cargo/registry/src/jackfan.us.kg-1ecc6299db9ec823/pyo3-0.4.1/src/pythonrun.rs:42:13
note: Run with `RUST_BACKTRACE=1` for a backtrace.
fatal runtime error: failed to initiate panic, error 5
fish: 'and python -c 'import autopy'' terminated by signal SIGABRT (Abort)

This only happens on 3.5 and 3.6, but not 3.7 or 2.7. Any ideas on what the cause might be?

@konstin
Copy link
Member

konstin commented Sep 14, 2018

This looks another instance of #219. Could you try latest master?

@msanders
Copy link
Contributor Author

Thanks for the help @konstin, looks like that fixed it. When do you think the next release will be published?

@konstin
Copy link
Member

konstin commented Sep 17, 2018

Not to soon. There are bunch of breaking changes already, so release has to be a new minor version (0.5.0) and I'd like to get fixed #94 and #210 before publishing that. I could publish a prerelease though; That would still allow publishing on crates.io.

@msanders
Copy link
Contributor Author

A prerelease would be great, actually. Hoping to get a new version of my library out that depends on PyO3.

konstin added a commit that referenced this issue Sep 17, 2018
@konstin
Copy link
Member

konstin commented Sep 17, 2018

Done: https://crates.io/crates/pyo3/0.5.0-alpha.1 (Got the releasing procedure right on the first try 🎉 )

@konstin konstin closed this as completed Sep 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants