-
Notifications
You must be signed in to change notification settings - Fork 7
Deprecate and redirect to spork/argparse #12
Comments
I don't know what you mean by "deprecate", may be you wouldn't mind elaborating? On a side note, I think it's possible this repository is referenced as a dependency in existing projects, so I think it would make sense for at least the current state to remain available. |
At least mention that the code is also available in the spork, in the readme? And that the future development will be in that package? And add deprecation metadata to the functions? Not deleting the repository, that is for sure. @sogaiu, thank you for helping me define what I mean. |
I think the first point regarding mentioning that development will be continuing in spork makes sense 👍 I'm not sure about changes to the existing code. |
Ok, so summed: add one sentence to the readme about the spork, and that development will continue there. |
That seems sensible to me, but perhaps there are others with different thoughts :) |
Thank you very much. Indeed it is still a question, not given at all. |
As the functionality of this package is also present in the spork package, I would consider deprecating it and redirect any future users to spork.
My only reason is not to have duplicate work if we find any bugs or improvements.
The text was updated successfully, but these errors were encountered: