{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreift7urdcjnb2u4gj7okyihv7gby3vtbrkh5fxj7ipyjdeedkl2p6i",
    "uri": "at://did:plc:4n6wgsqsqm6q2hjncgwmreey/app.bsky.feed.post/3mpn33kvqvyz2"
  },
  "path": "/post/52875681",
  "publishedAt": "2026-07-02T03:07:44.000Z",
  "site": "https://programming.dev",
  "tags": [
    "Python",
    "AstroLightz",
    "0 comments",
    "Python Packaging User Guide"
  ],
  "textContent": "submitted by AstroLightz to python\n3 points | 0 comments\n\nSo I have a Python package following the project structure outlined by the Python Packaging User Guide (Without the `tests/` directory). Let’s call it **Package A**.\n\nThis package can be used alongside another package, **Package B** , however no proper compatibility exists in **Package A** to support **Package B** ’s rendering system.\n\nI want to make a compatibility package, **Package AB** , to make **Package B** ’s systems work with **Package A**. It shares the same dependencies as **Package A** , however it has **Package B** as a dependency.\n\nHow should I setup my project structure for **Package AB**? Should it be its own project directory? Should it be nested inside **Package A** ’s `src` directory?\n\nAdditionally, I have Sphinx /w Hatch setup with **Package A** for documentation. Depending on the setup chosen above, how should I setup documentation for **Package AB**?\n\nSome things to note:\n\n  * **Package AB** would use classes and methods from **Package A** and **Package B**\n  * **Package B** ’s license (MIT) is compatible with **Package A** (GPLv3). **Package AB** would be licensed under the same as **Package A**\n\n\n\nIf more details are required, let me know.",
  "title": "Project structure for compat package with different dependency?"
}