Re: Asking for help Poetry

2020-11-22 Thread Emmanuel Arias
Hi everyone,

In the last week I re-take this work.

But, we need to discuss the poetry situation. First of all, poetry upstream
doesn't consider
adding vendor libs to the source. They have their reasons about this
situation. I recommend
you read this [0] [1].

The problem here, is that poetry need some dependencies that are not in
Debian yet,
and that dependencies have more dependencies (not in Debian).

Here there're some possibilities that from my point of view we can follow.
If you read [0] @abn recommend use `sonnet` script to build poetry
but is not maintained. In the other hand we can can try to package
poetry-core
that is a more pip similar case with the vendor libs.

In this week I want to make some tests using `sonnet` and look poetry-core
with the aim to  package poetry before freezing Debian.

I can send you (not today) the list of the dependencies that will be need
package if we want poetry in Debian.

This is my analysis about poetry (from a not so experienced DM) I will
happy to listen to more experienced people about this, and if you consider
correct that I mention, please.

Thanks!

[0] https://github.com/python-poetry/poetry/issues/2607
[1] https://github.com/python-poetry/poetry/issues/2346


Cheers,
Arias Emmanuel
@eamanu
yaerobi.com


On Thu, Nov 19, 2020 at 12:16 PM Bastian Venthur  wrote:

> Hi,
>
> I see some updates on the salsa repository, any chance we can get this
> package ready before the next freeze so we'll have it in the next stable
> release?
>
>
> Cheers,
>
> Bastian
>
> On 29.06.20 06:04, Scott Kitterman wrote:
> >
> >
> > On June 29, 2020 3:08:53 AM UTC, Emmanuel Arias 
> wrote:
> >> Hi,
> >>
> >> I'm working on poetry packaging, I created on salsa de repository [0].
> >>
> >> Note that there are many packages that are not in Debian like cachy,
> >> cleo,
> >> etc.
> >>
> >> I RFS python-cachy [1] and now I'm working on cleo, which depends on
> >> clikit
> >> that is not on Debian (if I search correctly).
> >>
> >> Bastian Venthur note me that pienv, pip have vendors folder with the
> >> dependencies
> >> but looking on poetry that _vendor folder is empty.
> >>
> >> So, looking for I more experienced opinion, do you think that we would
> >> try
> >> convince
> >> to upstream to make available vendors on the release (if that is
> >> necessary)
> >> or
> >> we need to package all the missing dependencies?
> >
> > Definitely they should be packaged.
> >
> > At least for pip none of the vendored libs are used in Debian's
> package.  Fortunately upstream supports use of system libs with only minor
> patching.
> >
> > Scott K
> >
> >
>
>
> --
> Dr. Bastian Venthur  http://venthur.de
> Debian Developer venthur at debian org
>
>


Bug#975509: ITP: nbdime -- Jupyter Notebook Diff and Merge tools

2020-11-22 Thread Joseph Nahmias
Package: wnpp
Severity: wishlist
Owner: Joseph Nahmias 

* Package name: nbdime
  Version : 2.1.0
  Upstream Author : Jupyter Development Team 
* URL : https://nbdime.readthedocs.io/
* License : BSD
  Programming Lang: Python
  Description : Jupyter Notebook Diff and Merge tools

nbdime provides tools for diffing and merging of Jupyter Notebooks.
.
  * nbdiff - compare notebooks in a terminal-friendly way
  * nbmerge - three-way merge of notebooks with automatic conflict resolution
  * nbdiff-web - shows you a rich rendered diff of notebooks
  * nbmerge-web - gives you a web-based three-way merge tool for notebooks
  * nbshow - present a single notebook in a terminal-friendly way