Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Multiple directories with same name

未关闭
  • 哪里不对？
#1,197 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
38/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
python
领域
tooling

调研方向

Review the linked fork branch and the existing add_package implementation, then inspect tests under tests/unit/ to find where package discovery is covered. First reproduce the duplicate directory name case and check how the proposed path argument selects a vunit_pkg.toml. Done means the behavior and its tests are clear and the unit test suite runs; the issue reports that pytest currently fails on both master and the branch.

由索引模型根据 Issue 内容生成。

描述

I have a problem with directories with the same name, and proposed a solution.

Our directory structure:

project_root
├── generallib
│   ├── rtl
│   ├── sim
│   └── tb
└── specific
    ├── comp1
    │   ├── rtl
    │   ├── sim
    │   └── tb
    └── comp2
        ├── rtl
        ├── sim
        └── tb

The issue is regarding directories containg vunit_pkg.toml.

  • rtl and tb folders contains vunit_pkg.toml.
  • sim folders contains run.py

Normal python import handles __init__.py fine via:

import comp1
import comp1.rtl
import comp1.tb

I have created a branch (on my forked repo):
https://github.com/VUnit/vunit/compare/master...mrlogic-dk:vunit:feature-add_package-via_path

Problem solved by this patch:

  • Multiple packages with the same directory name, e.g. rtl / tb.
    • Original add_package("package_name") will just insert the first found.
    • Enhanced package, with `path` argument,
      add_package(path"../../general-lib/tb")= will insert that
      specific package via vunit_pkg.toml

Whot do you think about the change with respect to functionality and implementation?

I can't run the test `pytest tests/unit/` neither on `master` or with my changes.

I don't know where to add test to test the behaviour.

I can't push to VUnit/vunit.

主要语言
VHDL
星标
850
派生
305
平均合并
2 天 10 小时
30 天内合并 PR
7

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

VUnit/vunit 的其他 Issue

查看 VUnit/vunit 的全部 Issue

相似的 Issue

更多 DevTools Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。