On 11/06/16 17:45, PICCA Frederic-Emmanuel wrote:
> Hello Julien
>
>> Not as far as I know. I'd be happy to review a package if that would
>> help.
>
> I just pushed here my wip package
>
> git clone
> git+ssh://git.debian.org/git/python-modules/packages/python-qtconsole.git
>
> I have debian
Jupyter has been in experimental for a while and presumably will make it
to unstable in the not too distant future.
Once that is done, what is the correct way for packages providing a
jupyter kernel to install it?
* manually install kernel.json in /usr/share/jupyter/kernels/?
* build-depend on
On 05/08/16 15:17, Julien Puydt wrote:
> Hi,
>
> On 05/08/2016 14:07, Gordon Ball wrote:
>> Jupyter has been in experimental for a while and presumably will make it
>> to unstable in the not too distant future.
>
> I don't think that will happen that early... th
I request to join the DPMT, initially to work on jupyter-notebook.
My alioth username is chronitis-guest.
I have read and accept the relevant policy.
Gordon
irc:chronitis
signature.asc
Description: OpenPGP digital signature
On 09/11/16 16:49, Julien Puydt wrote:
> Hi,
>
> On 09/11/2016 16:24, Zack Weinberg wrote:
>> ipython(3)-notebook has been dropped from unstable with the transition
>> to ipython 5.0.0. What package now provides this functionality?
>
> Gordon Ball is working on
Hello
We currently have IPython 5.1 in the archive.
Upstream has announced [1][2] IPython/Jupyter 5.x as an LTS branch (36
months support, ending July 2019), and the last version to support
Python 2.7. The first releases of IPython 6 (supporting Python 3 only)
are now available.
There seem to be
for python2
support. (SageMath definitely needs it.)
X
Gordon Ball:
Hello
We currently have IPython 5.1 in the archive.
Upstream has announced [1][2] IPython/Jupyter 5.x as an LTS branch (36
months support, ending July 2019), and the last version to support
Python 2.7. The first releases of IPython 6
Hello
The following packages should be ready for upload, if someone would be
willing to check and sponsor the uploads:
* ipython 5.4.0-1
IPython 6.x is now available, but is python3 only. For the moment,
the existing ipython source package will be the 5.x series, and at
some point it w
On Tue, 29 Aug 2017, Julien Puydt wrote:
Hi,
Le 28/08/2017 à 23:56, Gordon Ball a écrit :
Hello
The following packages should be ready for upload, if someone would be
willing to check and sponsor the uploads:
* ipython 5.4.0-1
IPython 6.x is now available, but is python3 only. For
On Mon, 4 Sep 2017, Julien Puydt wrote:
Hi,
Le 28/08/2017 à 23:56, Gordon Ball a écrit :
* nbconvert: 5.2.1
waiting on python-pandocfilters >= 1.4 (already in dpmt git, but
not yet uploaded)
I updated it to latest upstream -- the build doesn't fail because of
python-pando
On 04/09/17 19:23, Julien Puydt wrote:
> Hi,
>
> Le 04/09/2017 à 18:17, Julien Puydt a écrit :
>
>> There are quite many things to fix to correct before uploading, though :
>> lintian is not happy.
>
> Lintian still complains about two things:
> W: nbconvert source: newer-standards-version 4.1.0
On 18/09/17 09:48, Stuart Prescott wrote:
> Hi Diane,
>
> On Sunday, 17 September 2017 22:14:18 AEST Diane Trout wrote:
>> I just did it that way because it was the least disruptive change I
>> could make that would let me build and test the package.
>
> Sure, that's entirely sensible.
>
>> In m
On 08/09/17 18:47, Julien Puydt wrote:
> Hi,
>
> old thread but new things.
>
> Le 28/08/2017 à 23:56, Gordon Ball a écrit :
>
>> * nbconvert: 5.2.1
>>
>>waiting on python-pandocfilters >= 1.4 (already in dpmt git, but
>>not yet uploa
On 17/10/17 13:31, Adam Cecile wrote:
> Hello Gordon,
>
> We are really interested in getting notebook 5, any progress on this ?
> Is it possible to get your not-uploaded-yet packages (I did not find
> them on mentors.debian.net).
I have just uploaded the current RFS packages (ipython,
jupyter-no
On 25/10/17 21:51, Julien Puydt wrote:
> Hi,
>
> Le 25/10/2017 à 21:01, Diane Trout a écrit :
>>
>>> I have just uploaded the current RFS packages (ipython,
>>> jupyter-notebook, jupyter-console, nbconvert) to mentors.d.n
>>
>> I just reviewed nbconvert
Thanks for looking!
>>
>> I got one lintia
On 09/11/17 15:27, Andreas Tille wrote:
> Hi,
>
> statsmodels upstream claims that #880245 is a ipython/jupyter issue.
>
> Is there anybody with some knowledge and knows how to fix this issue?
I just built statsmodels 0.8.0-6 in and amd64 sbuild chroot without
encountering this issue.
Looking a
On 10/11/17 17:28, Andreas Tille wrote:
> Hi,
>
> On Thu, Nov 09, 2017 at 08:48:02PM +0100, Gordon Ball wrote:
>>
>> I just built statsmodels 0.8.0-6 in and amd64 sbuild chroot without
>> encountering this issue.
>>
>> Looking at the trace in
On 06/12/17 22:14, Andreas Tille wrote:
> control: tags -1 help
>
> Hi,
>
> I've upgraded snakemake in Git to latest upstream but its featuring the
> same issue. I'm pretty sure you Python people know a simple answer for
> this issue.
To first order, the issue with the `export PATH` line can be
Almost-christmas RFS:
jupyter-core (4.3.0-1 -> 4.4.0-1)
New upstream; adds a new binary package ("jupyter", metapackage
depending on a sensible jupyter distribution).
jupyter-client (5.1.0-1 -> 5.2.0-1)
New upstream.
Packages can be found in mentors:
https://mentors.debian.net/package/jupyt
The library style guide [1] says under _Executables and library
packages_:
> Here are some recommendations. We do not have a standard (though maybe
> we should)
regarding whether a library with an associated executable should be
split across `foo` and `python3-foo` or just bundled into `python3-f
On Sat, Feb 08, 2020 at 02:42:11AM +, Scott Kitterman wrote:
>
>
> On February 7, 2020 3:59:46 PM UTC, Mattia Rizzolo wrote:
> >On Fri, Feb 07, 2020 at 11:36:00AM +0000, Gordon Ball wrote:
> >> I wonder if this split really makes sense; it feels like adding the
&
On Sat, Feb 08, 2020 at 08:54:27PM +0100, Ondrej Novy wrote:
> Hi,
>
> so 8. 2. 2020 v 20:51 odesílatel Gordon Ball napsal:
>
> > Perhaps this is worth making an explicit recommendation for new packages
> > of this type, given that anything new _should_ be python3-only
On Mon, Mar 02, 2020 at 09:14:52AM -0500, Sandro Tosi wrote:
> > The src:ipykernel-py2 package provides python-ipykernel, which is to be
> > removed for the Python 2 removal transition.
>
> Cc-ing Gordon explicitly: the last time we spoke, Gordon wanted to
> keep the python2 stack of ipython/ikern
On Tue, Mar 31, 2020 at 10:04:34AM -0400, Scott Kitterman wrote:
> On Tuesday, March 31, 2020 9:54:41 AM EDT Sandro Tosi wrote:
> > >> Maybe you can paste the list of 20 affected apps, though?
> > >
> > > I'm more interested in the 18 that are above 1000. Could you please just
> > > list them all
On Mon, May 11, 2020 at 10:37:47PM -0400, Sandro Tosi wrote:
> > Any trick to avoid those errors in general?
>
You can also do
$ gbp push
which will automatically push the main (master or debian/master),
upstream and pristine-tar branches. However, by default it does not push
UNRELEASED changes
Hello
Julien sent a request to move/archive the redundant ipython repo about
two weeks ago, but it looks like it got missed by anyone with admin.
Could someone with powers:
1. Archive python-team/packages/ipython
2. Rename python-team/packages/ipython4 -> python-team/packages/ipython
The split
On Mon, May 17, 2021 at 06:20:19PM +0200, Roland Mas wrote:
> Hi everyone,
>
> I've been contracted by Synchrotron Soleil to work on the packaging of
> Jupyterhub and its dependencies. This turns out to about 20 Python packages,
> most of which should probably go under the Debian Python Team umbre
Package: wnpp
Severity: wishlist
Owner: Gordon Ball
X-Debbugs-Cc: gor...@chronitis.net, debian-python@lists.debian.org
* Package name: python-stack-data
Version : 0.1.3
Upstream Author : Alex Hall
* URL : https://github.com/alexmojaki/stack_data
* License
Package: wnpp
Severity: wishlist
Owner: Gordon Ball
X-Debbugs-Cc: debian-python@lists.debian.org, gor...@chronitis.net
* Package name: python-pure-eval
Version : 0.2.1
Upstream Author : Alex Hall
* URL : https://github.com/alexmojaki/pure_eval
* License : MIT
pyyaml (aka python3-yaml) is an rdepend for >300 packages. We currently
have 5.4.1, but version 6 was released late last year, which does quite
a lot of cleanup (eg, dropping python 2 support) and disables unsafe
loading (arbitrary python code execution) unless explicitly opted into.
Unfortunately
On 07/10/2022 01:13, Timo Röhling wrote:
> Hi Gordon,
>
> * Gordon Ball [2022-10-07 00:10]:
>> * Upload to unstable and see what breaks?
>> * Request an archive rebuild with this version and see what breaks?
>> * File bugs against all likely affected packages with a
On 09/10/2022 21:39, Gordon Ball wrote:
On 07/10/2022 01:13, Timo Röhling wrote:
Hi Gordon,
* Gordon Ball [2022-10-07 00:10]:
* Upload to unstable and see what breaks?
* Request an archive rebuild with this version and see what breaks?
* File bugs against all likely affected packages with a
On 19/10/2022 22:30, Gordon Ball wrote:
On 09/10/2022 21:39, Gordon Ball wrote:
On 07/10/2022 01:13, Timo Röhling wrote:
Hi Gordon,
* Gordon Ball [2022-10-07 00:10]:
* Upload to unstable and see what breaks?
* Request an archive rebuild with this version and see what breaks?
* File bugs
33 matches
Mail list logo
