-
Notifications
You must be signed in to change notification settings - Fork 35
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
Overall improvements #15
Comments
I wholeheartedly agree. The current API is rather old style using python dicts and sometimes feels non-coherent. |
For the next steps, I would propose to change the API and cleanup things. Now the question is a bit overall organisatorial: Is it maybe worth to create an org in order to remove the duty from a single person? The point is that in case you may stop being active, the name in pip and repo cannot be accessed anymore. Or how do you see that? I would suggest to maybe even create a new package under 'pyopt' (everything small) or maybe a different name not to break the compatibility. Or what do you think? Are you still in contact with the original authors? I guess it would be interesting to know from them as well Btw can you maybe activate the discussion for the repo? That is better suited for this kind of texts |
I don't think pip has a procedure to transfer packages when the original owner stops maintaining. But your suggestion to start an organization sounds good.
pyopt on pypi is taken as well (https://pypi.org/project/pyopt/)
I'll do it right away. |
Yes I agree, that is then tricky with the name... |
Hey @madebr what do you think of 'py-nonlinopt' as the organization name? Is that fine? Then we'll create it and can discuss anything else there |
We've created an org, you should have gotten an invite for it. How would you like to proceed, to move the repo there or rather fork from it in the org? Feel free to go about as you wish, you do have full admin rights |
ping @madebr |
Since this seems to be a rather old project, it may be worth to completely overhaul such as renaming the methods and package to a more python conform way.
What is your general idea on this?
The text was updated successfully, but these errors were encountered: