From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] setuptools (python) - how to disable the sandbox ?
Date: Sat, 9 Dec 2017 12:21:26 -0500 [thread overview]
Message-ID: <CAJ0EP40d=6RhrG6jzqLECXYbwBanVbbT1uzOqVnx_GmT47xtPg@mail.gmail.com> (raw)
In-Reply-To: <6UESCRXA.B36IA2HN.T77Z27Z2@VB3QY6SJ.ET4MT7MQ.PNOK6H5J>
On Sat, Dec 9, 2017 at 11:17 AM, Helmut Jarausch <jarausch@skynet.be> wrote:
> Hi,
> I want to create an ebuild for a package that's not in the tree
> (http://pypi.python.org/pypi/grako)
>
> Unfortunately, this always fails due to
>
> File "/usr/lib64/python3.6/site-packages/setuptools/sandbox.py", line 411,
> in _violation
> raise SandboxViolation(operation, args, kw)
> setuptools.sandbox.SandboxViolation: SandboxViolation:
> open('/var/tmp/portage/dev-python/grako-3.99.9/work/grako-3.99.9-python3_6/lib/ptr.py',
> 'wb') {}
>
> I wouldn't mind the package to write to its own working directory
> /var/tmp/portage/dev-python/grako-3.99.9/work
> but I cannot find out how to disable setuptools.sandbox
>
> I've tried addwrite "$S" and FEATURES=-usersandbox -sandbox
>
> but nothing helps.
The setup.py file for grako contains this line:
setup_requires=['pytest-runner'],
You probably forgot to add a dependency on dev-python/pytest-runner to
your ebuild, or forgot to install it before testing.
A better solution yet is to patch setup.py to remove this line
altogether. It is only there to ensure that running "setup.py test"
will work, which is unimportant in an ebuild.
prev parent reply other threads:[~2017-12-09 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-09 16:17 [gentoo-user] setuptools (python) - how to disable the sandbox ? Helmut Jarausch
2017-12-09 16:43 ` Michael Orlitzky
2017-12-09 16:50 ` Michael Orlitzky
2017-12-09 17:21 ` Mike Gilbert [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ0EP40d=6RhrG6jzqLECXYbwBanVbbT1uzOqVnx_GmT47xtPg@mail.gmail.com' \
--to=floppym@gentoo.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox