Add caution message to readme before the repo gets archived. #330
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
facebook-github-bot
added
the
CLA Signed
Contributor
malfet
approved these changes
Jul 9, 2025
Contributor
Contributor
janeyx99
reviewed
Jul 9, 2025
|
|
||
| > [!CAUTION] | ||
| > MultiPy has been unmaintained for some time and is going to be archived soon. We recommend | ||
| > users to look at the new [Free Threaded CPython](https://docs.python.org/3/howto/free-threading-python.html) version available starting with CPthon 3.13 as a long term solution to enable efficient multi-threading inference in CPython. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is trying to clarify the maintenance status of multipy. In particular that it has been unmaintained for quite some time and there is no plans to invest in it going forward.
This is especially true with Free Threaded CPython becoming a reality and so the multithread limitations that multipy was trying to solve are becoming moot.
For users looking at LLM-like workloads, we also have much better solutions today (in particular vLLM) as they are more efficient and simpler than multipy.
You can see the rendering of the caution message at https://github.com/pytorch/multipy/tree/warn_dead