-
Notifications
You must be signed in to change notification settings - Fork 336
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
Regression of pyVim import fails on macOS because of capital 'V' #487 #2247
Comments
Pyvmomi library build and tested only on 3.12 version maximum, if you look at https://github.com/vmware/pyvmomi Try to use this collection with 3.12. |
I agree with @ihumster, the problem is probably that pyVmomi isn't available for Python 3.13. BTW I see pyVim==3.0.3 in your requirements.txt. This is not what the collection needs. The pyVim package that the collection needs is part of pyVmomi. Which, see above, isn't available for Python 3.13. And I think we should ignore @lattaai9. The account has been created 2 hours ago. This looks suspicious to me. At the very least, this is some kind of spam. But it looks like some AI bullshit, and I'm not sure what is worse... |
@mariolenz I already reported @lattaai9 for spamming to GitHub. Hope they're going to delete that crap soonish.
Could be, but still doesn't explain why it sometimes works and sometimes doesn't. Let's see if others are having similar problems and may have additional information then.
Is it bundled within pyVmomi or pulled in as a dependency? (And on another note, I'm still searching for a good way to vendor an entire python environment with dependencies that isn't docker, for air gapped environments as well as being able to reproduce todays environment in e.g. one year from now or when stuff got deleted/DMCAed/supply-chain-attacked/...). |
Yes, this is indeed weird.
I think it's part of pyVmomi, not just a dependency that's pulled in and installed. At least, that's how it looke like to me:
|
SUMMARY
importing pyVim on MacOS sometimes fails (M3 Macbook)
ISSUE TYPE
COMPONENT NAME
community/vmware/plugins/module_utils/vmware.py
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
MacOS
STEPS TO REPRODUCE
It worked when I recreated the venv for the 2nd time. Therefore I don't know what exactly caused this fluke. In both cases I did:
python -m venv venv
using Python 3.13.0source venv/bin/activate; pip install -r requirements.txt
)community.vmware.vmware_host_facts
(see below)requirements.txt
EXPECTED RESULTS
Correct module output
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: