unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Phil <phil@beadling.co.uk>, help-guix@gnu.org
Subject: Re: Avoiding PYTHONPATH - latest?
Date: Tue, 01 Dec 2020 15:54:02 +0100	[thread overview]
Message-ID: <86eek9vaph.fsf@gmail.com> (raw)
In-Reply-To: <85y2ihpsef.fsf@beadling.co.uk>

Hi,

On Tue, 01 Dec 2020 at 13:28, Phil <phil@beadling.co.uk> wrote:

> I could instead run my unit tests against my git clone, but then you're
> not testing what you will deliver, you're testing the source code that
> will be packaged, not the package itself.  The unit tests may fail if
> run on the package itself.
>
> The way around this in Guix, I imagine, is to rebuild a Guix package
> containing your own Python code each time you want to test it and then
> have the unit tests run as part of that package definition.

You might be interested by the Efraim’s talk «Just build it with Guix»
from the online Guix Day:

  <https://guix.gnu.org/en/blog/2020/online-guix-day-announce-2/>

Roughly speaking, Guix allows an undocumented file usually named
“guix.scm” or “.guix.scm“ where the point is to easily do the “build and
test what is delivered” part.


Thanks,
simon


  reply	other threads:[~2020-12-01 14:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30  0:22 Avoiding PYTHONPATH - latest? Phil
2020-11-30  9:41 ` Phil
2020-12-03 11:06   ` 宋文武
2020-11-30 13:05 ` zimoun
2020-11-30 15:04   ` Phil
2020-12-01 12:39     ` zimoun
2020-12-01 13:28       ` Phil
2020-12-01 14:54         ` zimoun [this message]
2020-12-01 18:46           ` Phil

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=86eek9vaph.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=phil@beadling.co.uk \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).