Closed peteflorence closed 5 years ago
To clarify this breaks the docker build
I believe this is fixed by not --upgrade
for jupyter
. If everything works I can PR.
That would be great! This hit another reponI have under CI and I've been putting off dealing with it... I'm happy to prioritize fixing it myself if its an issue.
Seems like everything works if just dont have --upgrade on jupyter
On Fri, Oct 19, 2018 at 4:37 PM Gregory Izatt notifications@github.com wrote:
That would be great! This hit another reponI have under CI and I've been putting off dealing with it... I'm happy to prioritize fixing it myself if its an issue.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/gizatt/pydrake_kuka/issues/2#issuecomment-431491733, or mute the thread https://github.com/notifications/unsubscribe-auth/AFYQqJo29B03O8Bx9hi_0VwGTus4WW1_ks5umjgHgaJpZM4XxXvs .
I suspect the particular cause is that ipykernel v5.0.0 released around a month ago, and dropped Python 2.7 support. I'm waiting for CI to confirm this suspicion (just removing --upgrade
doesn't fix CI, only people who have old ipykernel versions sitting around).
Fixed by #3