1. Tarek Ziadé
  2. distribute
  3. Issues
Issue #333 wontfix

"Link ***BLOCKED***..." is a source of constant confusion for Buildout users

Alex Clark
created an issue

In Buildout when allow-hosts is set e.g.:

[buildout]
allow-hosts = *.python.org

Setuptools receives the "--allow-hosts" argument at which point it outputs loud messages.

Can we tone down the ***BLOCKED*** messages? E.g.

$ test-plone .
New python executable in ./bin/python
Installing distribute.................................................................................................................................................................................................done.
Installing pip................done.
Downloading/unpacking zc.buildout==1.6.3
…

Link to http://collective.github.com/buildout.bootstrap ***BLOCKED*** by --allow-hosts

…
Installing plone.

Link to http://github.com/plone ***BLOCKED*** by --allow-hosts


Link to https://github.com/aclark4life/zope2_bootstrap ***BLOCKED*** by --allow-hosts


Link to http://plone.org ***BLOCKED*** by --allow-hosts


Link to http://codespeak.net/svn/kukit/kss.core/trunk#egg=kss.core-dev ***BLOCKED*** by --allow-hosts


Link to http://kssproject.org ***BLOCKED*** by --allow-hosts


Link to http://kukit.org ***BLOCKED*** by --allow-hosts

Generated script '/private/var/folders/ks/sh5b4vj13q7_clr_h8tt0vj00000gn/T/tmpXOKuiA/bin/plone'.
Installing supervisor.

Link to http://supervisord.org/ ***BLOCKED*** by --allow-hosts


Link to http://dist.supervisord.org/ ***BLOCKED*** by --allow-hosts


Link to http://www.plope.com/software ***BLOCKED*** by --allow-hosts


Link to http://supervisord.org/dist/ ***BLOCKED*** by --allow-hosts


Link to http://www.plope.com/software/supervisor2/ ***BLOCKED*** by --allow-hosts


Link to http://www.plope.com ***BLOCKED*** by --allow-hosts


Link to http://www.plope.com/software/supervisor/supervisor-a3.tgz/download ***BLOCKED*** by --allow-hosts


Link to http://www.plope.com/software/meld3/ ***BLOCKED*** by --allow-hosts


Link to https://github.com/supervisor/meld3 ***BLOCKED*** by --allow-hosts


Link to http://dist.repoze.org/meld3/ ***BLOCKED*** by --allow-hosts


Link to http://svn.supervisord.org/meld3/ ***BLOCKED*** by --allow-hosts

…

The new text should be something like:

WARNING setuptools blocked host: hostname

Comments (15)

  1. Jason R. Coombs

    Is the issue with the wording or the number of messages? You suggested we change the wording, but there will still be the same large number of messages only with more polite wording. Is that okay?

  2. Domen Kožar

    (Reply via do...@dev.si):

    The issue is user gets confused (first time) what those BLOCKED messages mean. I think the best solution is to change wording in a way that doesn't scare new users.

    On Tue, Nov 27, 2012 at 1:11 AM, Jason R. Coombs <issues-reply@bitbucket.org

    wrote:

  3. Alfredo Deza

    I just hit this today and not being aware of what could trigger it I found the wording needs to be improved to point to a better explanation of what is going on.

    I suggest something like:

    WARNING: [FILE PATH TO DISTUTILS.CFG] allow_hosts directive (set to "example.com" option blocked install of [PACKAGE]  
    

    If by default the warnings were to be suppressed, a warning at the very end of the output could indicate that some dependencies/packages were not installed.

    The important thing here is to let the user know about allow-hosts and what is it doing so that a) one can fix it, or b) be ok with it

  4. Jason R. Coombs

    The first part of that warning is difficult. The --allow-hosts directive could have come from distutils.cfg in the distutils package, setup.cfg in the current directory, distutils.cfg (?) in the user's home directory, as a command-line argument, or specified in the setup.py itself.

    Also, it's not necessarily going to block installation of the package - it's just blocking one possible source of the package. It could still get it from elsewhere.

    So I think the best one could do is (a) indicate what the allow_hosts directive is set to, and (b) provide a link to docs indicating where distutils configuration might be found.

  5. Alex Clark reporter

    FWIW: I'm only interested in a wording change, starting with a change from: Link ***BLOCKED*** to: Warning: Link blocked by allow_hosts setting.

    Or something like that i.e. tone it down, please. Folks can figure out if allow_hosts is configured as a result of being reasonably informed of the block vs. being scared that something is broken. Extra points for linking to the documentation, perhaps.

  6. Donald Stufft

    FWIW the support for something similarly to this in pip (coming in 1.4) functions by only spewing these types of messages if -v has been passed, or if it was unable to find something to install it will instruct the user that something was blocked.

    Although pip's doesn't work on the host level and instead works on the package level.

  7. Log in to comment