Can't install the wheel file with pip while offline.

[besdollma]

Hi,
I am trying to install mkdocs-material in a computer that has no access to internet.
I have download the wheel file with pip and all the dependencies.
As it seems, mkdocs-material-extensions is a dependency for mkdocs-material.
Hence I perform first pip install mkdocs_material_extensions-1.0.1-py3-none-any.whl, this fails since it claims mkdocs-material must be installed. I know people have opened prior issues on circular dependencies, and they were closed. So can you please help on how to proceed ?
Thanks.

[squidfunk]

I'm definitely not a specialist on pip, so maybe somebody with deeper knowledge can help here.

[squidfunk]

The canonical way to use and install this project is pip, which resolves circular dependencies successfully. We can move the extensions code back into this repository to remove the circular dependency, but this is currently not a priority.

[facelessuser]

I approached this originally as an extension, not an integral part of Material. It was not desired to be placed in Material, so I treated it as an optional extra. I had thought that people would install it if they wanted the added benefit. That is why the extensions had a dependency added specifying a given Material version. What I thought was as an external extension has become more of an official module and an important piece of the main project. It doesn't ship without the extension.

It has become apparent that Material won't move forward breaking this extension's behavior without communication as it depends on this functionality. So I think letting Material manage versions of this plugin and such makes more sense than me managing it in the reverse.

Bazel's choice to support or not support circular dependencies is probably a much lower reason on my list as I am more concerned with what is officially supported.

Personally, I kind of think it makes sense to let Material absorb this extension since it won't ship without it anyways. That had always been my preferred choice, but at the time, @squidfunk was worried about supporting Python code in addition to the browser end. That may have changed now.

So, what I'll do is go ahead and remove the dependency. I will probably add an external check to throw an error if it is run with an unsupported Material version. If Material chooses to absorb the plugin, I'll be happy to help it do so.

[rafmagns-skepa-dreag]

Thank you for the resolution! You two have been very responsive and I really appreciate it. Thanks for your time and energy both on this issue and the packages.

[facelessuser]

I'll try to get the package updated no later than this weekeend.

[facelessuser]

https://github.com/facelessuser/mkdocs-material-extensions/releases/tag/1.0.2 has been tagged for release. Should be on PyPI shortly. I think this resolves everyone's issues.