Github messages for voidlinux
 help / color / mirror / Atom feed
From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: memray-1.7.0
Date: Wed, 12 Apr 2023 21:55:35 +0200	[thread overview]
Message-ID: <20230412195535.KleXz2YnmvvqdaMC8yj3ciIhUWUM1axvGwbZwjlcQE0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43411@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 976 bytes --]

There is an updated pull request by icp1994 against master on the void-packages repository

https://github.com/icp1994/void-packages memray
https://github.com/void-linux/void-packages/pull/43411

New package: memray-1.7.0
#### Description
[Memray](https://bloomberg.github.io/memray/) is a memory profiler for Python. It can track memory allocations in Python code, in native extension modules, and in the Python interpreter itself. It can generate several different types of reports to help you analyze the captured memory usage data.

#### Testing the changes
- I tested the changes in this PR: **YES**

#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**

#### Local build testing
- I built this PR locally for my native architecture: **x86_64**

A patch file from https://github.com/void-linux/void-packages/pull/43411.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-memray-43411.patch --]
[-- Type: text/x-diff, Size: 1432 bytes --]

From 6262d8c67d37a12af0941be2edd3bd5e375c793a Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Fri, 7 Apr 2023 22:32:18 +0530
Subject: [PATCH] New package: memray-1.7.0

---
 srcpkgs/memray/template | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)
 create mode 100644 srcpkgs/memray/template

diff --git a/srcpkgs/memray/template b/srcpkgs/memray/template
new file mode 100644
index 000000000000..12cae28f47b1
--- /dev/null
+++ b/srcpkgs/memray/template
@@ -0,0 +1,26 @@
+# Template file for 'memray'
+pkgname=memray
+version=1.7.0
+revision=1
+build_style=python3-pep517
+make_check_target="tests/unit"
+hostmakedepends="python3-setuptools python3-wheel python3-Cython"
+makedepends="python3-devel libunwind-devel liblz4-devel"
+depends="python3-Jinja2 python3-rich"
+checkdepends="${depends} python3-pytest"
+short_desc="Reports memory allocations in python code & compiled extensions"
+maintainer="icp <pangolin@vivaldi.net>"
+license="Apache-2.0"
+homepage="https://bloomberg.github.io/memray/"
+changelog="https://bloomberg.github.io/memray/changelog.html"
+distfiles="https://github.com/bloomberg/memray/archive/refs/tags/v${version}.tar.gz"
+checksum=0c735753d6d8a9050c9313c55ee41bfca271c3dec7cc37d2ed01eba5d358a7d6
+make_check_pre="env PYTHONPATH=src"
+
+pre_build() {
+	export MEMRAY_LIBBACKTRACE_TARGET="${XBPS_TARGET_MACHINE}"
+}
+
+pre_check() {
+	python3 setup.py build_ext --inplace
+}

  reply	other threads:[~2023-04-12 19:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 19:24 [PR PATCH] " icp1994
2023-04-12 19:55 ` icp1994 [this message]
2023-04-12 20:07 ` [PR PATCH] [Updated] " icp1994
2023-06-25 17:53 ` [PR PATCH] [Merged]: " Duncaen

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=20230412195535.KleXz2YnmvvqdaMC8yj3ciIhUWUM1axvGwbZwjlcQE0@z \
    --to=icp1994@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).