We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The documentation about packaging theme refers to somewhat outdated tools and practices.
I was wondering if you could update the documentation to use pyproject.toml and perhaps setup.cfg: https://packaging.python.org/en/latest/tutorials/packaging-projects/
I have an example pyproject.toml file:
[build-system] requires = ["setuptools"] build-backend = "setuptools.build_meta"
And example setup.cfg:
[metadata] name = mkdocs-<theme-name> version = attr: <theme_name>.__version__ author = author_email = url = description = long_description = file: README.md long_description_content_type = text/markdown keywords = mkdocs license = MIT classifiers = Programming Language :: Python :: 3 License :: OSI Approved :: MIT License Operating System :: OS Independent [options] packages = find: include_package_data = True zip_safe=False install_requires = mkdocs-<theme-parent> [options.entry_points] mkdocs.themes = <theme_name> = <theme_name> [options.extras_require] docs = markdown-include mkdocs [options.package_data] <theme_name> = *.html mkdocs_theme.yml
The text was updated successfully, but these errors were encountered:
Hi @sumau ; it would be useful if you could propose that change through a PR maybe?
Sorry, something went wrong.
No branches or pull requests
The documentation about packaging theme refers to somewhat outdated tools and practices.
I was wondering if you could update the documentation to use pyproject.toml and perhaps setup.cfg:
https://packaging.python.org/en/latest/tutorials/packaging-projects/
I have an example pyproject.toml file:
And example setup.cfg:
The text was updated successfully, but these errors were encountered: