Skip to content

Conversation

@Carreau
Copy link
Member

@Carreau Carreau commented Nov 8, 2021

This makes it annoying to test whether IPython breaks IPykernel.
I'm almost always on IPython master branch and I'd like to know when/if
I break things.

Prompted by ipython/ipython#13252,
which is not breaking ipykernel, but it's better to decouple where we
can.

This makes it annoying to test whether IPython breaks IPykernel.
I'm almost always on IPython master branch and I'd like to know when/if
I break things.

Prompted by ipython/ipython#13252,
which is not breaking ipykernel, but it's better to decouple where we
can.
@blink1073
Copy link
Contributor

We had added the pin as a failsafe in case there are breaking API changes, I'd feel better about removing it if ipython had a downstream test on ipykernel.

@Carreau
Copy link
Member Author

Carreau commented Nov 9, 2021

Thanks for the pointer, the pyargs and --upgrade-strategy=only-if-needed are useful.

Should I test both master an released or just released ?

@blink1073
Copy link
Contributor

I'd say just master, since then we can update ipykernel prior to the release to be compatible.

@Carreau
Copy link
Member Author

Carreau commented Nov 13, 2021

I just merged ipython/ipython#13266 that test upstream master.

@blink1073
Copy link
Contributor

Nice, thanks!

@blink1073 blink1073 merged commit b74ab37 into ipython:master Nov 13, 2021
@blink1073 blink1073 added this to the 6.5 milestone Nov 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants