-
Notifications
You must be signed in to change notification settings - Fork 130
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
Cannot call Connection from the pyrfc import or any other object #361
Comments
SAP NW RFC SDK libraries must be registered on Linux. Either add To verify SAP NW RFC SDK libraries registration, run the RFC SDK version number test: cd $SAPNWRFC_HOME/bin
./startrfc -v When it works, PyRFC should work as well. |
The hotifx should not be installed, unless requested by SAP Support. If not requested, please uninstall RFC SDK and install/register PL12, without hotfix. Then create new virtualenv and run pip install pyrfc there. Just to ensure the pynwrfc leftovers do not cause issues. The so format is ok, here how it looks in test system $ cd ...site-packages
$ tree pyrfc
pyrfc
├── _cyrfc.cpython-311-x86_64-linux-gnu.so
├── _exception.py
├── __init__.py
└── _utils.py |
@IsmaelAlvarez, the error is different, it looks like pyrfc is not installed. Is it listed in |
|
no idea yet. Could you please open new issue because the symptom is different and provide requested info on platform, python, sdk |
Describe the bug
I'm trying to implement pyrfc in my python project, but after all the installations of the library, and the nw rfc sdk package, I can't call the connection through import.
I've seen some, if not all, of the issues with related problems and they say to use pip install pynwrfc, but I've also seen on https://pypi.org/project/pynwrfc/ that it's been yanked. So I really don't understand what to do.
The issue I saw was from 2020, should I use what pynwrfc or pyrfc? Can you help me, please?
To Reproduce
I've done the installations that README.md tells me to, and I've tried to start coding.
Screenshots
Environment
The text was updated successfully, but these errors were encountered: