1.0 Release
#562
Replies: 2 comments 2 replies
-
So any dependant extension/tool using sphinxcontrib.needs.api (for e.g. to create needs with add_node) needs to adapt to using sphinx_needs.api then, correct ? |
Beta Was this translation helpful? Give feedback.
1 reply
-
To be consistent, we could take the chance and rename it to How about renaming the repo to What do you think? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, all Sphinx-Needs friends,
I'm planning a Sphinx-Needs 1.0 change, which has some breaking API changes.
Mainly
sphinxcontrib.needs
is moved tosphinx_needs
.This is primarily because of bugs with
pip install -e
and thesphinxcontrib.needs
package structure.In most cases, you could not install Sphinx-Needs in "develop" mode, which makes it hard to debug.
With the new structure, this is now possible and I have the feeling that also the poetry dependency resolver is now much faster.
However, as
sphinxcontrib.needs
is history with1.0
, I want your thoughts about renaming:useblocks/sphinx-needs
sphinx-needs.readthedocs.io
Any thoughts on this?
Beta Was this translation helpful? Give feedback.
All reactions