-
-
Notifications
You must be signed in to change notification settings - Fork 20
BLD: Pin requirements. #205
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
BLD: Pin requirements. #205
Conversation
Well, that build failed the tests pretty hard. IIRC, when @ftsalamp did #185, I had to upgrade to Tornado 5 (and indeed, my local virtualenv for this app is running 5.0.2). I thought the production service was also updated, but I’m looking at it now and it’s not, so I’m worried about what failures are failing worse than they should or what edge cases we have luckily not tripped over. FWIW, the output of
And in production: asn1crypto==0.22.0
beautifulsoup4==4.6.0
certifi==2017.7.27.1
cffi==1.10.0
chardet==3.0.4
conda==4.3.30
cryptography==2.0.3
diff-match-patch-python==1.0.2
docopt==0.6.2
html-tree-diff==0.1.2
html5lib==0.999999999
htmldiffer==0.25.1
idna==2.6
lxml==4.1.1
numpy==1.13.3
pandas==0.21.0
pycosat==0.6.2
pycparser==2.18
pyOpenSSL==17.2.0
PySocks==1.6.7
python-dateutil==2.6.1
pytz==2017.3
requests==2.18.4
ruamel-yaml==0.11.14
six==1.10.0
toolz==0.8.2
tornado==4.5.2
tqdm==4.19.4
tzlocal==1.4
urllib3==1.22
web-monitoring==0+untagged.428.g811f701
webencodings==0.5.1 |
This PR should also update |
…and lo, the version numbers did instantly demonstrate their value! |
283d30d
to
14189b9
Compare
And alphabetically sort them while we are at it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
W00t! \o/
Pinned to versions in my local dev environment that work, just to start. If the
tests pass we can upgrade from there using dependency monitoring.
Closes #195