eclipse-cyclonedds / eclipse-cyclonedds/cyclonedds-python
IDLC not generating usable modules when types are defined in parent files
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 110
- Forks
- 68
- Avg merge
- 1h 8m
- Merged PRs (30d)
- 1
Description
When running IDLC on the C2INAV IDL (C2INAV) after minor changes and provision of common files from OARIS an apparently successful conversion occurs. However, when attempting to import the generated module a NameError occurs due to missing type definitions.
Certain files, e.g. org__omg__c4i__Domain_Model__Navigation_Domain__Attitude__Offset_Report.idl, use types defined in their parent modules and appear to need relative import statements, e.g. from .._org__omg__c4i__Domain_Model__Navigation_Domain__Attitude import offset_report_key_type_kind, added to function correctly.
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 by reproducing the IDLC conversion for the C2INAV IDL and inspect the generated org__omg__c4i__Domain_Model__Navigation_Domain__Attitude__Offset_Report.idl module. Trace how it resolves types defined in parent modules, including offset_report_key_type_kind. Done means generated modules import successfully without NameError when parent-module types are used.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100