aio-libs / aio-libs/sphinxcontrib-asyncio

Ownership of `sphinxcontrib/__init__.py`

オープン
#12 コメント 3 件 リアクション 0 件 担当者 0 名 GitHub で見る
主要言語
Python
スター
21
フォーク
5
PR マージ指標
30日以内にマージされた PR はありません

説明

This project installs a file to the parent namespace, `sphinxcontrib/__init__.py`. In Fedora, this has [caused a problem for us](https://bugzilla.redhat.com/show_bug.cgi?id=2036438), because sphinxcontrib-zopeext does likewise, and the two files differ. I brought this up on the Fedora developer's mailing list, and Elliott Sales de Andrade has this to say:

```
I think these packages are wrong upstream. The `sphinxcontrib` directory is provided by python3-sphinx, and it specifically doesn't have `__init__.py` there. Those extensions should not be adding one, so as to keep the implicit namespace package nature of that directory: https://packaging.python.org/en/latest/guides/packaging-namespace-packages/#native-namespace-packages

By the contents of the files, it appears they are trying to force it to be a pkg_resources-style namespace package: https://packaging.python.org/en/latest/guides/packaging-namespace-packages/#pkg-resources-style-namespace-packages

But since Sphinx didn't do that in the first place, there's no guarantee that other packages will contain `__init__.py` (and indeed most do not).
```

Does sphinxcontrib-asyncio need that `__init__.py` file for some reason?

コントリビューションガイド

コントリビューションガイドを開く

評価

この issue はまだ評価されていません。

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。