Hi @ocelma ,
I currently "own" (but do not use) the recsys package name on PyPI. recsys was the name I wanted to use when I was developing Surprise, but I later realized that it would conflict with your own python-recsys package, whose import-time name is also recsys. (so I had to come up with a more far-fetched acronym! 😅).
@jiwidi recently reached out to me, asking if I'd be open to transferring the PyPI recsys name to him. I don't use the namespace myself so I'm happy to transfer; that being said, @jiwidi and I both agree that it's best to reach out to you first.
Is it fine with you for @jiwidi to own and use the recsys name on PyPI? (that means users will install and use the project with pip install recsys / import recsys). We also reached out to you via email a few weeks ago, so feel free to follow up there if you prefer.
Thank you!
Hi @ocelma ,
I currently "own" (but do not use) the
recsyspackage name on PyPI.recsyswas the name I wanted to use when I was developing Surprise, but I later realized that it would conflict with your ownpython-recsyspackage, whose import-time name is alsorecsys. (so I had to come up with a more far-fetched acronym! 😅).@jiwidi recently reached out to me, asking if I'd be open to transferring the PyPI
recsysname to him. I don't use the namespace myself so I'm happy to transfer; that being said, @jiwidi and I both agree that it's best to reach out to you first.Is it fine with you for @jiwidi to own and use the
recsysname on PyPI? (that means users will install and use the project withpip install recsys / import recsys). We also reached out to you via email a few weeks ago, so feel free to follow up there if you prefer.Thank you!