-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
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
Deprecate after Material 9.4 Releases #27
Comments
9.4.0 is out! Thanks for maintaining the extension for the last years. I'll take it from here |
@facelessuser did you have a chance to look at this? We could deprecate the extension and remove it in the next major release. I think a deprecation notice when somebody is referencing the extension in |
I can probably make it a priority. I didn't know how fast you were wanting to move with this. I can up the priority of this and get it out soonish. |
I don't want to pressure you, just wanted to know whether you're still considering this. The deprecation notice is mandatory for us to incentivize people to move to the new extension, and we better have a long deprecation period, because I suspect that many people are using it. After a sufficiently long deprecation period, we will remove the extension. |
Yep still planning it, just hadn't done it yet. Makes sense to do it sooner rather than later. |
I've created a PR. I need to test it locally before merging, but it should resolve this issue. |
I just tried it, and the deprecation is shown:
However, an error is triggered. The error is only triggered when both I installed as follows:
|
Yeah, I reworked the deprecation approach, tests should be passing now. |
Jup, the error is gone! You are fast 😎 |
Does it apply warnings as expected? I haven't run it in a project yet. |
Hmm. Doesn't seem it bubbles up. |
I may have to force some mkdocs logging... |
It emits on |
No, it's just not generating for me in the project I'm testing it in. |
I don't think MkDocs logs random deprecation warnings from the Python Markdown level. We'd have to somehow send a message to the MkDocs logger. |
I can tap into the MkDocs logging. I just need to approach it from an angle where we don't spam the warning on every file. |
Ok, great! |
Logging will be a
|
Perfect! Glad you solved it. I will bump the minimum required version to 1.3 once it is out. |
I imagine I can get it out later this evening (my time). |
Released |
Thanks! I just bumped to 1.3 and can confirm that it works! Thanks again for maintaining this project for such a long time! |
We've long felt that this work should live in the MkDocs Material repo, but we provided it as a courtesy as Material was uncomfortable maintaining this extension.
With the upcoming release of MkDocs Material 9.4, the maintainer now feels confident enough to maintain this extension. Once this release is made, and everything has been confirmed to have 1:1 behavior, we will deprecate this extension and generate a warning to use the Material's version.
This is a much better arrangement moving forward as Material will have all the "Material" support baked in and we can focus on Pymdown Extensions.
The text was updated successfully, but these errors were encountered: