Arch Linux User Repository

@petronny sounds good, I just removed py-spy from ray's install_requires in the setup.py but am still keeping it as a depends in the PKGBUILD.

Is there a way to show py-spy though pip list?

@acxz I totally agree with eschwartz's comment. It's not a python package at all.
I think we should inform python-ray to change its way to detect py-spy.

Also the author of py-spy insist to distribute it via pypi.

Well, quite a mess.

python-ray requires py-spy but even if it is installed it doesn't detect it as it is searching for it through the python package registry. Is there a way to show py-spy though pip list?

Looks like it was an error on my end, build works fine now.

Hello! Thx for maintaining this package.

I am getting the following error when trying to install it:

==> Making package: py-spy 0.3.3-1 (Thu 05 Mar 2020 10:20:32 PM EST)
==> Retrieving sources...
  -> Found py-spy-0.3.3.tar.gz
==> Validating source files with sha512sums...
    py-spy-0.3.3.tar.gz ... Passed
==> Making package: py-spy 0.3.3-1 (Thu 05 Mar 2020 10:20:32 PM EST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found py-spy-0.3.3.tar.gz
==> Validating source files with sha512sums...
    py-spy-0.3.3.tar.gz ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting py-spy-0.3.3.tar.gz with bsdtar
==> Sources are ready.
==> Making package: py-spy 0.3.3-1 (Thu 05 Mar 2020 10:20:34 PM EST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Removing existing $pkgdir/ directory...
==> Starting build()...
  Downloaded ctrlc v3.1.4
warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of `inferno v0.9.4` failed to transfer more than 10 bytes in 30s)
warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for `indicatif v0.14.0` within 30s)
warning: spurious network error (1 tries remaining): [28] Timeout was reached (failed to download any data for `indicatif v0.14.0` within 30s)
warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of `term_size v0.3.1` failed to transfer more than 10 bytes in 30s)
warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for `bitflags v1.2.1` within 30s)
warning: spurious network error (1 tries remaining): [28] Timeout was reached (download of `bitflags v1.2.1` failed to transfer more than 10 bytes in 30s)
warning: spurious network error (1 tries remaining): [28] Timeout was reached (failed to download any data for `term_size v0.3.1` within 30s)
warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of `cpp_demangle v0.2.14` failed to transfer more than 10 bytes in 30s)
warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for `console v0.9.2` within 30s)
warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of `tempfile v3.1.0` failed to transfer more than 10 bytes in 30s)
warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for `serde_json v1.0.48` within 30s)
warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of `rand_distr v0.2.2` failed to transfer more than 10 bytes in 30s)
warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for `rand v0.7.3` within 30s)
warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of `failure v0.1.6` failed to transfer more than 10 bytes in 30s)
warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for `env_logger v0.7.1` within 30s)
warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of `libc v0.2.67` failed to transfer more than 10 bytes in 30s)
warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for `goblin v0.1.3` within 30s)
warning: spurious network error (1 tries remaining): [28] Timeout was reached (download of `rand v0.7.3` failed to transfer more than 10 bytes in 30s)
warning: spurious network error (1 tries remaining): [28] Timeout was reached (failed to download any data for `rand_distr v0.2.2` within 30s)
warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of `memmap v0.7.0` failed to transfer more than 10 bytes in 30s)
warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for `lru v0.4.3` within 30s)
jkwarning: spurious network error (1 tries remaining): [28] Timeout was reached (download of `env_logger v0.7.1` failed to transfer more than 10 bytes in 30s)
warning: spurious network error (1 tries remaining): [28] Timeout was reached (failed to download any data for `failure v0.1.6` within 30s)
error: failed to download from `https://crates.io/api/v1/crates/term_size/0.3.1/download`

Caused by:
  [28] Timeout was reached (download of `term_size v0.3.1` failed to transfer more than 10 bytes in 30s)
==> ERROR: A failure occurred in build().
    Aborting...
Error making: py-spy
yay -Syu py-spy  233.61s user 159.84s system 97% cpu 6:45.39 total

It seems that libunwind should be added to depends.

Merged instead, thanks for the fast response.

BTW, no need to provide/conflict itself, also you forgot to quote the newly added ${srcdir} references.

This is not a python package and is therefore misnamed and should not contain the prefix "python-".

It's a 100% rust project, which uses weird and IMO disgusting hacks to pretend to be a python program for no other reason than to make it easy for people to misuse and abuse the PyPI index for hosting statically compiled rust binaries. What's next, pip install firefox as a distribution method for your favorite browser?

Please re-upload this as a package called "py-spy", using cargo build --release to build the software during build(), using install(1) to install the resulting binary during package(), and most importantly, setting arch=('x86_64') as this is most definitely not an any-arch package.