From: Alex Brandt <alunduil@gentoo.org>
To: gentoo-python@lists.gentoo.org
Subject: [gentoo-python] Testing Python Packages
Date: Wed, 03 Sep 2014 17:46:54 -0500 [thread overview]
Message-ID: <2411859.5RSSJtBeRX@elijah> (raw)
[-- Attachment #1: Type: text/plain, Size: 790 bytes --]
Hey Everyone,
I've been tinkering with an ebuild testing framework but want to
know if I'm actually solving a problem or just creating a
nuisance.
I thought I'd start with the Python group before asking in
general but I've been wondering what keeps people from running
test suites on ebuilds before they commit ebuilds to the tree?
I'm only asking out of curiosity and don't want to start any
discussion about what should or should not be done. I want to
know about what things actually block work on tasks like tests
that might be forgotten.
Any feedback about why people in particular do or do not run
test suites would be greatly appreciated.
Thanks,
--
Alex Brandt
Cloud Evangelist for Rackspace and Developer for Gentoo
http://blog.alunduil.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 213 bytes --]
reply other threads:[~2014-09-03 22:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2411859.5RSSJtBeRX@elijah \
--to=alunduil@gentoo.org \
--cc=gentoo-python@lists.gentoo.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