From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Hamzeh Nasajpour" <h.nasajpour@pantherx.org>
Cc: 44090-done@debbugs.gnu.org
Subject: bug#44090: Packaging a python library that is implemented with rust
Date: Mon, 01 Feb 2021 14:02:27 -0500 [thread overview]
Message-ID: <87zh0nr4qk.fsf@gmail.com> (raw)
In-Reply-To: <ccc953ad-6bc9-4ccf-8bc0-6c8d6d977105@www.fastmail.com> (Hamzeh Nasajpour's message of "Tue, 20 Oct 2020 08:40:19 +0330")
Hello Hamzeh,
"Hamzeh Nasajpour" <h.nasajpour@pantherx.org> writes:
> Hi,
>
> I'm not expert in rust and python but I need to package a python library, and this python library is a wrapper over the rust library. This library is using the `setuptools_rust` for build/install.
> * python library: https://github.com/etesync/etebase-py
> * rust library: https://github.com/etesync/etebase-rs
> * `setup.py`: https://github.com/etesync/etebase-py/blob/master/setup.py
>
> Anyway I need to package this python library. Since guix has two different build system for `python` and `rust` I don't know how can I package it. It's a python library but it should install some rust library inside the python system build.
[...]
> Sorry for duplication, I sent this email here too: https://lists.gnu.org/archive/html/help-guix/2020-10/msg00092.html
> then I thought this mailing list is better for asking this type questions.
The original list was better suited for this kind of question. This
list is about actual *bugs*, rather than general question. I see you've
had a reply from Leo; hopefully that answered your question.
Closing.
Maxim
prev parent reply other threads:[~2021-02-01 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 5:10 bug#44090: Packaging a python library that is implemented with rust Hamzeh Nasajpour
2020-10-20 10:23 ` Leo Prikler
2021-02-01 19:02 ` Maxim Cournoyer [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zh0nr4qk.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=44090-done@debbugs.gnu.org \
--cc=h.nasajpour@pantherx.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).