jnrbase
Evolution¶
The idea for jnrbase
began in January 2014, and lasted throughout the year in
a rather idling on the back burner way. The problem was simply one of support,
if you wanted to support users who depended on pip or setuptools you couldn’t
reliably use extras
on dependencies. And without extras
you either had
to break the project up in to many tiny ones, or force all the optional
dependencies on all the users.
Two — nearly three — years later, and the ecosystem has changed somewhat.
Given the combination of pip now supporting extras
and, frankly, it
becoming far less common for installation in the circles I move in, it is
therefore time to resurrect this project.
The future¶
As of 2017-10-25, branches already exist for all my public projects. jnrbase
support hasn’t been merged to master
on all of them yet, but it is just
a matter of time.
Should the functionality show itself to be useful, or should I feel the need to
add dependencies on jnrbase
on group maintained projects, the trajectory could
change. So, consider it fluid for now and if you have questions feel free to
ask!