v0.29.0

[Paebbels]

New Features

• New RecordElementSymbol.
• Adding resolution of record element subtypes in packages #78 by @Tcenova
• Add unary reduction expressions #84 by @Tcenova

Changes

• Bumped dependencies.
• Added Nullable if a parameter has a default value of None.
  Older versions implicitly inferred nullable/optional, but new version if mypy request it explicitly.
• Changed many properties from @property to @readonly.
• Added and improved usage of parent parameter to be forwarded down to ModelEntity.

Bug Fixes

• Fix importing of objects with multiple identifiers.
  See Fix package namespace bugs #82 by @Tcenova

Documentation

• Enhanced layout by CSS overrides.
• Added doc-strings to many methods.
• Described algorithms of:
  • AddDocument
  • IterateDesignUnits
  • IndexDeclaredItems
  • Analyze
  • AnalyzeDependencies
  • AnalyzeObjects
  • CreateDependencyGraph
  • CreateCompileOrderGraph
  • LinkArchitectures
  • LinkPackageBodies
  • IndexPackages
  • IndexPackageBodies
  • IndexEntities
  • IndexArchitectures
  • CreateHierarchyGraph
  • IterateDocumentsInCompileOrder

---

Related PRs:

• Adding resolution of record element subtypes in packages #78
• Fix package namespace bugs #82
  • fixes Constant in pkg files cause issues in AnalyzeObjects due to _identifiers vs _identifier #80
  • fixes Subtype resolution is not finding subtype when defined in another pkg file in another library #81
• Add unary reduction expressions #84

[Paebbels]

Discussion from #84:

I dont have any other planned things to push to this repo for now. If you could create a release, I can ensure the PR to GHDL updates the version required. Do you have a preference on which branch of GHDL I use as a base? I would assume I should use your updated-tests branch since it should work with the updates in this repo?

OK, I'll create a release.

---

I need to check for a good GHDL base. I'm a bit out of sync. One I have that long ongoing side branch with some failing tests, because GHDL added more features to the sanity checking files - but pyGHDL.DOM can't handle it. OTOH, I'm working on a new pipeline, which was also forced to integrate some changes due to pyTooling v6.x.x.

I suspect I should get the pipeline rework merged and then update/rebase my other branch.

[Tcenova]

I suspect I should get the pipeline rework merged and then update/rebase my other branch.

Do you have an approximate ETA on when this might occur? Is the pipeline work needed to build pyGHDL if I were to try and merge enough locally for my needs?

[Paebbels]

@Tcenova I had some detours with other packages and I faced some self-made and some "other-made" problems. So unfortunately I have some delay.

One of my main problems was a dependency cycle within my own packages by "dog feeding". So I use my own packages and code that I provide as libraries and tools in my own pipelines. With this, I locked my self out from being able to push new packages :). The problem is now understood and since almost 2 weeks I'm able to release again.

Having solved this major issue, I can go back to GHDL's pipeline. The last piece I want to achieve is an upgrade to latest pyVHDLModel (there have been some maintenance releases) and getting the asset upload working.

I expect currently 1-2 more week(end)s.