Skip to content
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

Update the compatibility policy #12168

Merged
merged 2 commits into from May 6, 2024
Merged

Update the compatibility policy #12168

merged 2 commits into from May 6, 2024

Conversation

twm
Copy link
Contributor

@twm twm commented May 6, 2024

Fix various formatting issues and introduce NEXT placeholders where applicable.

Scope and purpose

Fixes #12167.

I noticed that the reST syntax for notes was mangled, resulting in the note content being hidden. I restored these notes.

I also removed language about "new-style" classes because old-style classes are mercifully a thing of the past and reworded/rearranged some sections.

Fix various formatting issues and introduce NEXT placeholders where
applicable.
@twm twm force-pushed the 12167-deprecation-next-docs branch from 3d37d7d to ed3bd5c Compare May 6, 2024 07:00
Copy link
Member

@adiroiban adiroiban left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Thanks!


Functions and methods
^^^^^^^^^^^^^^^^^^^^^
Pass ``Version("Twisted", "NEXT", 0, 0)`` `incremental placeholder <https://github.com/twisted/incremental#updating>`_ to the to indicate the upcoming release.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't we recommand a single placeholder ?

I would go with Twisted NEXT as it should be valid for both Python or RST code.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They're not interchangeable: Version(...) is what you pass to the APIs; Twisted NEXT is what you use in docstrings and/or assertions.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the info.
I see why you might want to have an increment Version instance in Python... but I always felt that this is an overengineering ... at least for the deprecation warning message.

docs/development/compatibility-policy.rst Show resolved Hide resolved
Co-authored-by: Adi Roiban <adiroiban@gmail.com>
@twm twm enabled auto-merge May 6, 2024 19:31
@twm twm merged commit 625a86c into trunk May 6, 2024
24 checks passed
@twm twm deleted the 12167-deprecation-next-docs branch May 6, 2024 19:46
@twm
Copy link
Contributor Author

twm commented May 6, 2024

Thanks Adi!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Deprecation docs should use NEXT placeholders
3 participants