Add py.typed marker to BNF package

[Copilot]

The BNF package (apyds-bnf) lacked PEP 561 compliance, preventing type checkers from recognizing its type annotations.

Changes

• Added py.typed marker file to apyds_bnf/ directory
• Updated .gitignore to track py.typed

The exported functions already have proper type signatures:

def parse(input: str) -> str: ...
def unparse(input: str) -> str: ...

With the py.typed marker file, external type checkers can now recognize the package's type information according to PEP 561.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>给bnf下的python包添加py.typed并检查导出的函数确实已经被typed</issue_title>
<issue_description></issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes 给bnf下的python包添加py.typed并检查导出的函数确实已经被typed #98

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[hzhangxyz]

不要做多余的事情，加上py typed文件，加到gitignore的例外里就行了，其他不要改

[Copilot]

不要做多余的事情，加上py typed文件，加到gitignore的例外里就行了，其他不要改

Reverted all extra changes. Only kept the py.typed file and .gitignore exception as requested. (commit f3cf2fe)

[Copilot]

Pull request overview

This PR adds PEP 561 compliance to the BNF package by introducing a py.typed marker file. The package already has properly typed exported functions (parse and unparse), and this change enables external type checkers to recognize the package's type information.

• Added empty py.typed marker file to signal PEP 561 compliance
• Updated .gitignore to ensure py.typed is tracked in version control

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File	Description
bnf/apyds_bnf/py.typed	Empty marker file added to indicate the package supports type checking per PEP 561
bnf/apyds_bnf/.gitignore	Updated to explicitly track py.typed alongside __init__.py, while still ignoring ANTLR-generated files

Note: While the changes in this PR are correct, complete PEP 561 compliance requires that py.typed be included in the package distribution configuration (typically via package-data in pyproject.toml). Since pyproject.toml was not modified in this PR, you may want to verify that the file will be included when the package is built and installed. Modern setuptools may or may not automatically include py.typed depending on configuration.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.