Package Details: python-restrictedpython 8.0-1

Git Clone URL: https://aur.archlinux.org/python-restrictedpython.git (read-only, click to copy)
Package Base: python-restrictedpython
Description: A restricted execution environment for Python to run untrusted code
Upstream URL: https://github.com/zopefoundation/RestrictedPython
Licenses: ZPL
Submitter: bmwinger
Maintainer: bmwinger
Last Packager: bmwinger
Votes: 1
Popularity: 0.000004
First Submitted: 2019-08-11 00:06 (UTC)
Last Updated: 2025-03-01 19:47 (UTC)

Latest Comments

1 2 Next › Last »

Dornhoeschen commented on 2025-03-02 23:56 (UTC)

installs fine now - thank you!

bmwinger commented on 2025-03-02 22:41 (UTC)

Even with 8.0? Check the error message: if it still says setuptools<74 then that can't be restrictedpython 8.0, as they updated the pin to 75.6, and that was patched out in the only version of the 8.0 PKGBUILD I pushed. I suspect you're just re-installing the same thing (or maybe the sed pattern isn't working for some reason).

Dornhoeschen commented on 2025-03-02 20:57 (UTC) (edited on 2025-03-02 20:58 (UTC) by Dornhoeschen)

As I tried to fix the portmod, I uninstalled restrictedpython. Now I cannot install it anymore due to the described error. I force a rebuild on my helper - no change.

bmwinger commented on 2025-03-01 18:38 (UTC)

It needs updating anyway, but are you using a AUR helper that caches the PKGBUILDs? I'd updated it to patch out the <74 requirement, but I didn't bump the pkgrel since it wasn't something that would affect successful installs, so presumably you're using the previous PKGBUILD without that patch.

Dornhoeschen commented on 2025-03-01 18:31 (UTC)

I am unable to install this anymore

I am getting this error

==> Starting build()...
* Getting build dependencies for wheel...
running egg_info
creating src/RestrictedPython.egg-info
writing src/RestrictedPython.egg-info/PKG-INFO
writing dependency_links to src/RestrictedPython.egg-info/dependency_links.txt
writing requirements to src/RestrictedPython.egg-info/requires.txt
writing top-level names to src/RestrictedPython.egg-info/top_level.txt
writing manifest file 'src/RestrictedPython.egg-info/SOURCES.txt'
reading manifest file 'src/RestrictedPython.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
adding license file 'LICENSE.txt'
writing manifest file 'src/RestrictedPython.egg-info/SOURCES.txt'

ERROR Missing dependencies:
    setuptools<74
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: python-restrictedpython-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
python-restrictedpython - exit status 4

This lets me fail the portmod build.

Any suggestion how to fix?

bunburya commented on 2020-10-01 21:57 (UTC) (edited on 2020-10-01 21:59 (UTC) by bunburya)

Sorry, nevermind. I was getting a ModuleNotFoundError: No module named 'brotli' whenever I tried to install this package, but upon closer inspection that error is actually being thrown by py.test on my system (regardless of context), apparently due to some other package.

bmwinger commented on 2020-09-28 18:09 (UTC)

Are you sure python-brotlipy is needed? I don't see reference to it in the RestrictedPython source code or documentation anywhere.

bunburya commented on 2020-09-26 14:00 (UTC)

I needed python-brotlipy installed to install this; I think it should be included as a check dependency.

lunchbox commented on 2019-10-18 14:47 (UTC)

So it looks like my problem was related to a past install of openmmm. It looks like this package got built back in April and when I went to install it the /usr/lib/python3.7/site-packages/patool-1.12-py3.7.egg-info/ directory and all its contents already existed. I verified that the folder had no owner with pacman so I deleted it and rebuilt this package. Everything worked as expected.

bmwinger commented on 2019-09-08 02:50 (UTC)

I don't know if this was the same as your problem @lunchbox, but I realized that pytest wasn't finding the RestrictedPython module, and the only reason the tests passed on my machine was because I also had RestrictedPython installed via pip in .local at the same time, so it was testing that version.

I've fixed this at the same time as the version bump to 5.0.

1 2 Next › Last »