On Sat, Sep 26, 2015 at 5:21 AM, Donald Stufft wrote stuff
Thanks for the summary, it sounds like the Python community is slowly
moving towards a setup that is more closely aligned with Debian's
values and setup.
--
bye,
pabs
https://wiki.debian.org/PaulWise
On September 26, 2015 at 5:30:35 AM, Paul Wise (p...@debian.org) wrote:
> On Fri, 2015-09-25 at 19:25 -0400, Donald Stufft wrote:
>
> > Because the way Python packaging currently is and historically has
> > been, binary packages are not something that is widely available or
> > viable.
>
> Hmm, I
On Fri, 2015-09-25 at 19:25 -0400, Donald Stufft wrote:
> Because the way Python packaging currently is and historically has
> been, binary packages are not something that is widely available or
> viable.
Hmm, I thought eggs have been around for ages (seems about 8 years)?
--
bye,
pabs
https:/
On September 25, 2015 at 8:21:39 PM, Ben Finney (ben+deb...@benfinney.id.au)
wrote:
> Donald Stufft writes:
>
> > On September 25, 2015 at 7:24:30 PM, Paul Wise (p...@debian.org) wrote:
> > > Why are end users using source packages instead of binary packages
> > > and then complaining that the s
Donald Stufft writes:
> On September 25, 2015 at 7:24:30 PM, Paul Wise (p...@debian.org) wrote:
> > Why are end users using source packages instead of binary packages
> > and then complaining that the source tarballs aren't ready-to-run
> > binary packages?
>
> Because the way Python packaging cu
On September 25, 2015 at 7:24:30 PM, Paul Wise (p...@debian.org) wrote:
> On Thu, Sep 24, 2015 at 1:17 PM, Thomas Kluyver wrote:
>
> > That's my point ;-). From our upstream point of view, it's not a bug
> > that the distributions we put on PyPI contain generated/bundled files -
> > we do it that
On Thu, Sep 24, 2015 at 1:17 PM, Thomas Kluyver wrote:
> That's my point ;-). From our upstream point of view, it's not a bug
> that the distributions we put on PyPI contain generated/bundled files -
> we do it that way deliberately, so that end users can install without
> needing Javascript devel
On Thu, Sep 24, 2015, at 03:30 AM, Paul Wise wrote:
> Source tarballs containing generated/bundled files is a bug that
> should be fixed.
That's my point ;-). From our upstream point of view, it's not a bug
that the distributions we put on PyPI contain generated/bundled files -
we do it that way d
On Sun, Sep 20, 2015 at 12:47 PM, Thomas Kluyver wrote:
> However, my hope in that sentence was that other packaging will come not
> to rely on Python sdists containing a setup.py file. Using sdists for
> Debian packaging is already somewhat dubious, because they can contain
> generated and bundle
On Sat, Sep 19, 2015, at 09:36 AM, Barry Warsaw wrote:
> There have been countless attempts at moving the Python packaging
> infrastructure to a declarative syntax over the years. I remember
> talking to
> Tarek at a Pycon *many* years ago about this. Maybe this time it'll
> catch
> on. :)
I thi
On Sep 19, 2015, at 12:35 AM, Thomas Kluyver wrote:
>By the way, I am also upstream for flit, and I'm prepared to help build
>some tooling to use it for distro packaging. I know it will cause some
>inconvenience in the short term because there's infrastructure around
>setup.py packaging, but ultim
On Sat, Sep 19, 2015, at 01:05 AM, Julien Puydt wrote:
> Yes, you're also upstream for ptyprocess and terminado :-P
Guilty as charged ;-) I work for Jupyter/IPython, so there are several
dependencies from that that I'm responsible for.
> I have nothing against declarative -- it's just that I sus
Hi,
Le samedi 19 sept. 2015 à 00:35:49 (-0700), Thomas Kluyver a écrit :
> On Fri, Sep 18, 2015, at 11:56 PM, Julien Puydt wrote:
> > here is a new way to package modules for Python:
> > https://github.com/takluyver/flit
> >
> > It means that something packaged using it doesn't use a setup.py or
On Fri, Sep 18, 2015, at 11:56 PM, Julien Puydt wrote:
> here is a new way to package modules for Python:
> https://github.com/takluyver/flit
>
> It means that something packaged using it doesn't use a setup.py or some
> such, but a flit.ini ; see for example:
> https://github.com/jupyter/testpat
Hi,
here is a new way to package modules for Python:
https://github.com/takluyver/flit
It means that something packaged using it doesn't use a setup.py or some
such, but a flit.ini ; see for example:
https://github.com/jupyter/testpath
I'm not sure how to package something like this (and testpa
15 matches
Mail list logo
