Hi,
ok, but are you ok with us moving ahead? Is ipython generally ready to
migrate? What about the other related packages (ipykernel,
jupyter_client, jupyter_core, nbconvert, nbformat). Should they all
migrate together? Are they ready (up to questions of transition)?
I did another attempt to buil
Iustin Pop writes:
> Reading
> https://wiki.debian.org/Python/LibraryStyleGuide#Building_python_-dbg_packages,
> there is some hints to this
The introduction of ‘foo-dbgsym’ automatic generated packages makes me
quite sure those instructions are obsolete. But perhaps they are not?
> but it's no
❦ 11 octobre 2016 10:38 CEST, Ben Finney :
>> Reading
>> https://wiki.debian.org/Python/LibraryStyleGuide#Building_python_-dbg_packages,
>> there is some hints to this
>
> The introduction of ‘foo-dbgsym’ automatic generated packages makes me
> quite sure those instructions are obsolete. But per
Vincent Bernat writes:
> The page seems up-to-date
It makes no reference to why ‘foo-dbgsym’ is not enough, so the reader
doesn't have any guidance on which practice overrules the other.
> and already explains why Python is different (presence of a debug
> interpreter)
As I said, that doesn't
Hi,
On 11/10/2016 09:27, Tobias Hansen wrote:
ok, but are you ok with us moving ahead? Is ipython generally ready to
migrate? What about the other related packages (ipykernel,
jupyter_client, jupyter_core, nbconvert, nbformat). Should they all
migrate together? Are they ready (up to questions of
5 matches
Mail list logo