CyberSource / CyberSource/cybersource-rest-samples-python
ModuleNotFoundError: No module named 'CyberSource.logging'
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 29
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
Configuration has been setup. Trying to run a sample PayerAuthentication script.
Traceback (most recent call last):
File "samples/PayerAuthentication/authentication-with-new-account.py", line 7, in <module>
configuration = SourceFileLoader("module.name", config_file).load_module()
File "<frozen importlib._bootstrap_external>", line 462, in _check_name_wrapper
File "<frozen importlib._bootstrap_external>", line 962, in load_module
File "<frozen importlib._bootstrap_external>", line 787, in load_module
File "<frozen importlib._bootstrap>", line 265, in _load_module_shim
File "<frozen importlib._bootstrap>", line 702, in _load
File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 783, in exec_module
File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
File "/home/user/foomanchu/projects/cybersource-rest-samples-python/data/Configuration.py", line 2, in <module>
from CyberSource.logging.log_configuration import LogConfiguration
ModuleNotFoundError: No module named 'CyberSource.logging'
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with samples/PayerAuthentication/authentication-with-new-account.py and data/Configuration.py, then trace how the Python client exposes the CyberSource.logging module used by the configuration. Reproduce the sample’s import failure and verify that the sample can load its configuration without the reported ModuleNotFoundError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100