1. It uses some fancy import magic that doesn't work with py3.3+. 2. Used only by Bcryptor which seems to have no revdeps. 3. GitHub repo disappeared, seems to be only left on pypi with a single release from 2010. Suggest double lastrite :).
Update: I just got reply from Bcrypt upstream and he says he's not interested in Python stuff anymore. Since nothing seems to actually use Bcrypt, I think it'd be best if we lastrited both packages.
/usr/portage/dev-python/passlib/passlib-1.6.2.ebuild:RDEPEND="dev-python/bcrypt[${PYTHON_USEDEP}]" /usr/portage/dev-python/py-bcrypt/py-bcrypt-0.4.ebuild:RDEPEND="!dev-python/bcrypt" /usr/portage/dev-python/flask-security/flask-security-1.7.3.ebuild: dev-python/bcrypt[${PYTHON_USEDEP}] /usr/portage/dev-python/flask-security/flask-security-1.7.1.ebuild: dev-python/bcrypt[${PYTHON_USEDEP}] /usr/portage/dev-python/flask-security/flask-security-1.7.2.ebuild: dev-python/bcrypt[${PYTHON_USEDEP}] it is used, but if we can I'd be for it.
sorry, the c#1 was supposed to say dev-python/Bcryptor. I'd guess idella4 committed that think by mistake then...
Masked for removal then.
(In reply to Michał Górny from comment #3) > sorry, the c#1 was supposed to say dev-python/Bcryptor. I'd guess idella4 > committed that think by mistake then... It wasn't by mistake. however this is neither here nor there. FWIW the dep was initially made on Bcrypt which was set as the dep. On further working of passlib, it became apparent bcrypt was there better supported better functioning lib. By this time Bcrypt has already been added. This is purely for explanatory purposes. I never 'bothered' to then remove it, which I could have. It's fine for it to go, it's a lemon.
removed
