You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Ryan Ollos <ry...@gmail.com> on 2014/12/04 22:38:15 UTC
Bloodhound on PyPI
(Resending since email from my Apache alias didn't post to list)
---------- Forwarded message ---------
From: Ryan J Ollos <rj...@apache.org>
Date: Tue Dec 02 2014 at 8:08:03 PM
Subject: Bloodhound on PyPI
To: dev@bloodhound.apache.org <de...@bloodhound.apache.org>
I'm planning to publish Bloodhound to PyPI (1) with this release. Please
let me know if you have any comments about this.
For the devs, if you'd like to have Owner permissions for the package on
PyPI so that you can publish new versions and update the page, please let
me know. I'll plan to add Gary and anyone else that speaks up.
(1) https://pypi.python.org/pypi
Re: Bloodhound on PyPI
Posted by Olemis Lang <ol...@gmail.com>.
On Fri, Dec 5, 2014 at 4:58 PM, Ryan Ollos <ry...@gmail.com> wrote:
> On Fri, Dec 5, 2014 at 9:23 AM, Olemis Lang <ol...@gmail.com> wrote:
>
> [...]
> > e.g. Trac is downloaded from t.e.o
> > , is it worth to check what's been done in that case ?
> >
>
> The Trac packages get uploaded to the PyPI servers, I just did this when
> releasing 0.12.6 and 1.0.2 last month. The files listed on the page live on
> the PyPI servers:
> https://pypi.python.org/pypi/Trac/1.0.2
>
> Anyway, we may be getting sidetracked because I don't think anyone has
> raised concerns about putting the package on PyPI, I think it was just
> assumed that the downloads needed to be hosted elsewhere.
>
>
>
TBH , since long time ago I only install from the repository but I recall I
saw things like this in a few logs once upon a time e.g. [1] [2] [3]
> > Nevertheless my main concern is that easy-installation might not be a
> > result of publishing it on PyPI . Bloodhound installation is not a
> setup.py
> > driven process . There are some scripts involved and I'm not sure PyPI
> > provides support for such scenarios ... maybe it's worth investigating
> the
> > wheel format [1]_ looking for a few answers and also to decide whether to
> > adopt it as an (alternative | official) packaging format .
> >
> > The risk associated with (lack of) easy-installability is that users end
> up
> > with an unstable system immediately after installation .
> >
> > .. [1] http://legacy.python.org/dev/peps/pep-0427/
> >
>
> That is a good point. Gary did some work recently to "make the installer
> installable". We'll need to do some testing to see if it's possible or
> useful to easy_install. PyPI has a test server we can utilize, avoiding the
> need to make the package public while we evaluate:
> https://wiki.python.org/moin/TestPyPI
>
+1
.. [1] http://pastebin.com/KhBNJ9sQ
.. [2] http://pastebin.com/bAxWUhd2
.. [3] http://pastebin.com/axguEWEE
--
Regards,
Olemis - @olemislc
Apache(tm) Bloodhound contributor
http://issues.apache.org/bloodhound
http://blood-hound.net
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
Re: Bloodhound on PyPI
Posted by Ryan Ollos <ry...@gmail.com>.
On Fri, Dec 5, 2014 at 9:23 AM, Olemis Lang <ol...@gmail.com> wrote:
> On Fri, Dec 5, 2014 at 1:44 AM, Ryan Ollos <ry...@gmail.com> wrote:
>
> > On Thu Dec 04 2014 at 2:15:47 PM Branko Čibej <br...@wandisco.com>
> wrote:
> >
> >
>
> [...]
>
> > >
> > > Are you going to post a link to the package on
> > > archive.apache.org, or something else?
> >
> >
> > PyPI allows packages to be directly uploaded to their site. I'm not sure
> if
> > there's an option to host a package elsewhere, but I suspect not.
> >
> >
> >
>
>
> ... there should be one such option because I've seen packages retrieved
> from e.g. sourceforge servers . AFAICR , e.g. Trac is downloaded from t.e.o
> , is it worth to check what's been done in that case ?
>
The Trac packages get uploaded to the PyPI servers, I just did this when
releasing 0.12.6 and 1.0.2 last month. The files listed on the page live on
the PyPI servers:
https://pypi.python.org/pypi/Trac/1.0.2
Anyway, we may be getting sidetracked because I don't think anyone has
raised concerns about putting the package on PyPI, I think it was just
assumed that the downloads needed to be hosted elsewhere.
> Nevertheless my main concern is that easy-installation might not be a
> result of publishing it on PyPI . Bloodhound installation is not a setup.py
> driven process . There are some scripts involved and I'm not sure PyPI
> provides support for such scenarios ... maybe it's worth investigating the
> wheel format [1]_ looking for a few answers and also to decide whether to
> adopt it as an (alternative | official) packaging format .
>
> The risk associated with (lack of) easy-installability is that users end up
> with an unstable system immediately after installation .
>
> .. [1] http://legacy.python.org/dev/peps/pep-0427/
>
That is a good point. Gary did some work recently to "make the installer
installable". We'll need to do some testing to see if it's possible or
useful to easy_install. PyPI has a test server we can utilize, avoiding the
need to make the package public while we evaluate:
https://wiki.python.org/moin/TestPyPI
Re: Bloodhound on PyPI
Posted by Olemis Lang <ol...@gmail.com>.
On Fri, Dec 5, 2014 at 1:44 AM, Ryan Ollos <ry...@gmail.com> wrote:
> On Thu Dec 04 2014 at 2:15:47 PM Branko Čibej <br...@wandisco.com> wrote:
>
>
[...]
> >
> > Are you going to post a link to the package on
> > archive.apache.org, or something else?
>
>
> PyPI allows packages to be directly uploaded to their site. I'm not sure if
> there's an option to host a package elsewhere, but I suspect not.
>
>
>
... there should be one such option because I've seen packages retrieved
from e.g. sourceforge servers . AFAICR , e.g. Trac is downloaded from t.e.o
, is it worth to check what's been done in that case ?
Nevertheless my main concern is that easy-installation might not be a
result of publishing it on PyPI . Bloodhound installation is not a setup.py
driven process . There are some scripts involved and I'm not sure PyPI
provides support for such scenarios ... maybe it's worth investigating the
wheel format [1]_ looking for a few answers and also to decide whether to
adopt it as an (alternative | official) packaging format .
The risk associated with (lack of) easy-installability is that users end up
with an unstable system immediately after installation .
.. [1] http://legacy.python.org/dev/peps/pep-0427/
--
Regards,
Olemis - @olemislc
Apache™ Bloodhound contributor
http://issues.apache.org/bloodhound
http://blood-hound.net
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
Re: Bloodhound on PyPI
Posted by Ryan Ollos <ry...@gmail.com>.
On Thu Dec 04 2014 at 2:15:47 PM Branko Čibej <br...@wandisco.com> wrote:
> On 04.12.2014 22:38, Ryan Ollos wrote:
> > (Resending since email from my Apache alias didn't post to list)
> >
> > ---------- Forwarded message ---------
> > From: Ryan J Ollos <rj...@apache.org>
> > Date: Tue Dec 02 2014 at 8:08:03 PM
> > Subject: Bloodhound on PyPI
> > To: dev@bloodhound.apache.org <de...@bloodhound.apache.org>
> >
> >
> > I'm planning to publish Bloodhound to PyPI (1) with this release. Please
> > let me know if you have any comments about this.
> >
> > For the devs, if you'd like to have Owner permissions for the package on
> > PyPI so that you can publish new versions and update the page, please let
> > me know. I'll plan to add Gary and anyone else that speaks up.
>
>
> Sounds good. Are you going to post a link to the package on
> archive.apache.org, or something else?
PyPI allows packages to be directly uploaded to their site. I'm not sure if
there's an option to host a package elsewhere, but I suspect not.
> In general, it's a good idea to
> somehow make users download the source from a mirror, not our
> dist/archive servers. There's a script somewhere to get the nearest
> Apache mirror, but I'm not sure how much control you have over that on
> PyPI.
>
> It'd be a good idea to ask infra@ (or #asfinfra) for guidance.
>
Thanks, I'll do a search of the archives and then ask on infra if the topic
hasn't been raised before.
>
> -- Brane
>
Re: Bloodhound on PyPI
Posted by Gary Martin <ga...@wandisco.com>.
On 04/12/14 22:13, Branko Čibej wrote:
> On 04.12.2014 22:38, Ryan Ollos wrote:
>> (Resending since email from my Apache alias didn't post to list)
>>
>> ---------- Forwarded message ---------
>> From: Ryan J Ollos <rj...@apache.org>
>> Date: Tue Dec 02 2014 at 8:08:03 PM
>> Subject: Bloodhound on PyPI
>> To: dev@bloodhound.apache.org <de...@bloodhound.apache.org>
>>
>>
>> I'm planning to publish Bloodhound to PyPI (1) with this release. Please
>> let me know if you have any comments about this.
>>
>> For the devs, if you'd like to have Owner permissions for the package on
>> PyPI so that you can publish new versions and update the page, please let
>> me know. I'll plan to add Gary and anyone else that speaks up.
>
> Sounds good. Are you going to post a link to the package on
> archive.apache.org, or something else? In general, it's a good idea to
> somehow make users download the source from a mirror, not our
> dist/archive servers. There's a script somewhere to get the nearest
> Apache mirror, but I'm not sure how much control you have over that on PyPI.
>
> It'd be a good idea to ask infra@ (or #asfinfra) for guidance.
>
> -- Brane
I agree, I think this is a great idea. I doubt that we would turn out to
be the first ASF project to be on PyPI after all.
On the assumption that this will be a standard part of the release
process, it would be good to see more PMC members interested in having
owner permissions.
Cheers,
Gary
Re: Bloodhound on PyPI
Posted by Branko Čibej <br...@wandisco.com>.
On 04.12.2014 22:38, Ryan Ollos wrote:
> (Resending since email from my Apache alias didn't post to list)
>
> ---------- Forwarded message ---------
> From: Ryan J Ollos <rj...@apache.org>
> Date: Tue Dec 02 2014 at 8:08:03 PM
> Subject: Bloodhound on PyPI
> To: dev@bloodhound.apache.org <de...@bloodhound.apache.org>
>
>
> I'm planning to publish Bloodhound to PyPI (1) with this release. Please
> let me know if you have any comments about this.
>
> For the devs, if you'd like to have Owner permissions for the package on
> PyPI so that you can publish new versions and update the page, please let
> me know. I'll plan to add Gary and anyone else that speaks up.
Sounds good. Are you going to post a link to the package on
archive.apache.org, or something else? In general, it's a good idea to
somehow make users download the source from a mirror, not our
dist/archive servers. There's a script somewhere to get the nearest
Apache mirror, but I'm not sure how much control you have over that on PyPI.
It'd be a good idea to ask infra@ (or #asfinfra) for guidance.
-- Brane
Re: Bloodhound on PyPI
Posted by Tetsuya Morimoto <te...@gmail.com>.
+1. It makes Python users easy to find Bloodhound.
On Fri, Dec 5, 2014 at 6:38 AM, Ryan Ollos <ry...@gmail.com> wrote:
> (Resending since email from my Apache alias didn't post to list)
>
> ---------- Forwarded message ---------
> From: Ryan J Ollos <rj...@apache.org>
> Date: Tue Dec 02 2014 at 8:08:03 PM
> Subject: Bloodhound on PyPI
> To: dev@bloodhound.apache.org <de...@bloodhound.apache.org>
>
>
> I'm planning to publish Bloodhound to PyPI (1) with this release. Please
> let me know if you have any comments about this.
>
> For the devs, if you'd like to have Owner permissions for the package on
> PyPI so that you can publish new versions and update the page, please let
> me know. I'll plan to add Gary and anyone else that speaks up.
>
> (1) https://pypi.python.org/pypi