#82: Clarify version numbers in requirements.txt ------------------------+-------------------------- Reporter: sumanah | Owner: Type: enhancement | Status: new Priority: major | Milestone: Beta version Version: | Keywords: ------------------------+-------------------------- Right now, only a few of the requirements in the requirements.txt files specify version numbers. I would be happy to add some details with >= so we are clear about what we are backwards-compatible with -- what should those numbers be? This will make installation a lot easier.
It looks like we can use the same trick for specifying mailman.client in the !HyperKitty requirements as in kittystore. Also, I'd particularly like guidance on the Beautiful Soup installation requirements; given that we only use Beautiful Soup in a few tests in tests/views/test_thread.py, it seems to me that we could probably clarify this and only install beautifulsoup4.
!HyperKitty:
{{{ django-gravatar2 django-social-auth>=0.7.1 djangorestframework>=2.2.0 mailman>=3.0.0b2 kittystore South django-crispy-forms rjsmin cssmin robot-detection pytz django-paintstore django-compressor BeautifulSoup<4.0 django-browserid>=0.10.1 mailmanclient beautifulsoup4 }}}
kittystore:
{{{ mailman>=3.0.0b2 zope.interface # sqlalchemy 0.9.8 because this needs to be fixed: https://bitbucket.org/zzzeek/sqlalchemy/issue/3199/ sqlalchemy>=0.9.8 alembic # python-dateutil 2.0+ is for Python 3 python-dateutil < 2.0 mock networkx Whoosh dogpile.cache # mailmanclient is not yet in PyPI bzr+lp:mailman.client#egg=mailmanclient
}}}