Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Section attributes

Open
#93 16 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
api

Research direction

Start by reviewing the odml.Section() and odml.Property() constructors and how their parent and reference attributes are used. Clarify whether Section should accept parent and reference, and define the desired API behavior before making changes; the issue is done when that design is agreed and consistently implemented.

Written by the indexing model from the issue text.

Description

Currently odml.Section() takes name, type, parent and definition.

For me parent does not make sense here. Especially since odml.Property() does not have a parent args.

Another thing: a Section object has a reference attribute, but it can't be defined when creating the Section like it can be done for a Property. In general I think that the reference (if interpreted as reference from where metadata are coming from) is an attribute which should only belong to Properties and not Sections. A Section could contain Properties with metadata coming from different sources.

What do you think?

Dominant language
Python
Stars
25
Forks
30
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from G-Node/python-odml

All issues in G-Node/python-odml

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.