Package Details: python-playwright 1.42.0-1

Git Clone URL: https://aur.archlinux.org/python-playwright.git (read-only, click to copy)
Package Base: python-playwright
Description: a Python library to automate Chromium, Firefox and WebKit browsers with a single API
Upstream URL: https://github.com/microsoft/playwright-python
Licenses: Apache-2.0
Submitter: aloxaf
Maintainer: alhirzel
Last Packager: alhirzel
Votes: 3
Popularity: 0.003255
First Submitted: 2021-03-13 05:25 (UTC)
Last Updated: 2024-03-16 16:06 (UTC)

Latest Comments

alhirzel commented on 2024-03-15 18:40 (UTC)

@AlphaJack - I can definitely do this, but can you help me understand the intent? If you are making an alternative package, is there sufficient reason to do this? Or could you simply help me maintain this package or let me know what change would help you.

@lahwaacz - please feel welcome to comment as well.

lahwaacz commented on 2024-02-21 11:29 (UTC)

@AlphaJack It does not make much sense, this package does not provide the nodejs library...

AlphaJack commented on 2024-02-21 08:25 (UTC)

Hi, can you add

provides=("playwright")
conflics=("playwright")

to the PKGBUILD?

lahwaacz commented on 2024-02-10 20:39 (UTC)

@ViToni debugedit is required by base-devel, which is implicitly assumed to be installed when building Arch packages. Note that it is a meta package rather than a group since a year ago: https://archlinux.org/news/switch-to-the-base-devel-meta-package-requires-manual-intervention/

ViToni commented on 2024-02-10 18:10 (UTC)

While installing python-playwright 1.41.1-1 I see the message:

/usr/share/makepkg/tidy/strip.sh: line 48: debugedit: command not found

Maybe this needs to be a dependency.

alhirzel commented on 2023-12-25 02:36 (UTC)

Gotcha :) Well good eyes nonetheless! Status update, I have submitted a question about the driver here: https://github.com/microsoft/playwright/issues/8100

lahwaacz commented on 2023-12-24 11:50 (UTC)

@alhirzel Thanks, but actually I don't know anything about playwright, I only noticed the problems by building in a clean chroot and checking the build log :-)

alhirzel commented on 2023-12-22 13:35 (UTC) (edited on 2023-12-22 14:15 (UTC) by alhirzel)

@lahwaacz good eyes - I will look into this over the next few days. If you have time, I am happy to add you as co-maintainer or maintainer as well? It appears you know a little more than me about packaging playwright.

At first glance, I see this "driver" build step was added a few years ago: https://github.com/microsoft/playwright-python/commit/c606344e9a321abcb4c932b2bc80066b6158fdf8

I have updated the dependencies you mentioned (thank you!) but simply removing the driver step breaks the package. I have bumped pkgrel with the updated dependencies and commented-out the breaking change removing the driver wheel download. It is mysterious indeed; perhaps a separate package is needed for python-playwright-driver.

lahwaacz commented on 2023-12-19 08:26 (UTC) (edited on 2023-12-19 08:58 (UTC) by lahwaacz)

makedepends should be updated: git, python-build and python-installer are missing and python-pip and python-setuptools are not used anymore.

Still, I noticed this in the build log:

removing build/bdist.linux-x86_64/wheel
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 35.1M  100 35.1M    0     0  4352k      0  0:00:08  0:00:08 --:--:-- 4844k
Fetching https://playwright.azureedge.net/builds/driver/next/playwright-1.40.0-beta-1700587209000-linux.zip
Updating RECORD file of /build/python-playwright/src/playwright-python/dist/.tmp-eil86rkr/playwright-1.40.0-py3-none-manylinux1_x86_64.whl
Copying new wheels
Successfully built playwright-1.40.0-py3-none-manylinux1_x86_64.whl

What's going on? It still does not seem to be a pure from-source build...

MarsSeed commented on 2023-11-02 23:37 (UTC)

Installing with python-pip is not allowed by Arch Python package guidelines, and even pip itself complains that it should not be done.

Instead, please implement the recommended Standards based (PEP 517) installation.

Also, this should be built from source, not packaged from an x86_64 binary wheel.