spaCy: Create repository, merge bugs

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

spaCy: Create repository, merge bugs

Andreas Tille-5
Control: merge 894629 835854

I have created a git repository for spacy at

    https://salsa.debian.org/science-team/spacy

since I might need python3-spacy for one of my target packages.

Next step should probably be to package spaCy predependency

    https://github.com/explosion/cymem

Volunteers would be extremely welcome

     Andreas.

PS: I've also added spacy to linguistics and machine-learning task.

--
http://fam-tille.de

Reply | Threaded
Open this post in threaded view
|

Re: spaCy: Create repository, merge bugs

Mo Zhou
Hi Andreas,

Please always search on Salsa before really starting to package any
dependency of spaCy. IIRC I've finished nearly all the dependencies,
except for thinc. There are around ten packages but I aborted the whole
package chain because thinc, the backend of spaCy, is yet another deep
learning framework.

spaCy is indeed used in my recent research, but note some of its
dependencies look not actively maintained, and I'm not interested
in maintaining hundreds of DL frameworks for Debian... That's exactly
how I aborted it.

The dependency chain is basically ready to be uploaded. Specifically,
for thinc and spaCy, please drop my name from control if there is any.

On Wed, Nov 28, 2018 at 09:42:30AM +0100, Andreas Tille wrote:

> Control: merge 894629 835854
>
> I have created a git repository for spacy at
>
>     https://salsa.debian.org/science-team/spacy
>
> since I might need python3-spacy for one of my target packages.
>
> Next step should probably be to package spaCy predependency
>
>     https://github.com/explosion/cymem
>
> Volunteers would be extremely welcome
>
>      Andreas.
>
> PS: I've also added spacy to linguistics and machine-learning task.
>
> --
> http://fam-tille.de
>

Reply | Threaded
Open this post in threaded view
|

Re: spaCy: Create repository, merge bugs

Andreas Tille-5
Hi Lumin,

On Thu, Nov 29, 2018 at 02:05:33AM +0000, Mo Zhou wrote:

> Hi Andreas,
>
> Please always search on Salsa before really starting to package any
> dependency of spaCy. IIRC I've finished nearly all the dependencies,
> except for thinc. There are around ten packages but I aborted the whole
> package chain because thinc, the backend of spaCy, is yet another deep
> learning framework.
>
> spaCy is indeed used in my recent research, but note some of its
> dependencies look not actively maintained, and I'm not interested
> in maintaining hundreds of DL frameworks for Debian... That's exactly
> how I aborted it.
>
> The dependency chain is basically ready to be uploaded. Specifically,
> for thinc and spaCy, please drop my name from control if there is any.
(Uhmmm, I see I left it on thinc when uploading to new - I'll fix it in
Git meanwhile.)

Just to be sure: spaCy needs msgpack-numpy and I can't find it prepared
on salsa.  Am I missing something?

Thanks for the good preparation which was very helpful!

Kind regards

        Andreas.

--
http://fam-tille.de

Reply | Threaded
Open this post in threaded view
|

Re: spaCy: Create repository, merge bugs

Mo Zhou
On Thu, Nov 29, 2018 at 03:06:14PM +0100, Andreas Tille wrote:
> > The dependency chain is basically ready to be uploaded. Specifically,
> > for thinc and spaCy, please drop my name from control if there is any.
> (Uhmmm, I see I left it on thinc when uploading to new - I'll fix it in
> Git meanwhile.)
>
> Just to be sure: spaCy needs msgpack-numpy and I can't find it prepared
> on salsa.  Am I missing something?

I'm sure there is no packaging repo for msgpack-numpy.

In my fuzzy memory that is merely a single python script. I didn't
bother to create a package for such a single and short python script.
At that time I was defenitely thinking of embedding it to the package
that needs it.

I don't remember if this script is specific to spaCy. If not, someone
may jump out and argue that embedding scripts is a bad practice. In that
case, it is still quite simple and straightforward to create a package
for it.
 
> Thanks for the good preparation which was very helpful!

Thanks for taking over my historical WIPs.