Excerpts from Kevin L. Mitchell's message of 2015-04-27 17:38:25 -0500:
On Mon, 2015-04-27 at 21:42 +, Jeremy Stanley wrote:
I consider it an unfortunate oversight that those files weren't
deleted a very, very long time ago.
Unfortunately, there's one problem with that: you can't tell
On 04/27/2015 06:38 PM, Kevin L. Mitchell wrote:
On Mon, 2015-04-27 at 21:42 +, Jeremy Stanley wrote:
I consider it an unfortunate oversight that those files weren't
deleted a very, very long time ago.
Unfortunately, there's one problem with that: you can't tell tox to use
a virtualenv
On Tue, Apr 28, 2015 at 2:56 PM, Jeremy Stanley fu...@yuggoth.org wrote:
On 2015-04-28 16:08:03 -0400 (-0400), Jay Pipes wrote:
Honestly, I see no problem with some helper bash scripts that
simplify life for new contributors.
[...]
[...]
I remember it happening regularly before we started
On Mon, 2015-04-27 at 15:54 -0700, Clint Byrum wrote:
Excerpts from Kevin L. Mitchell's message of 2015-04-27 15:38:25 -0700:
On Mon, 2015-04-27 at 21:42 +, Jeremy Stanley wrote:
I consider it an unfortunate oversight that those files weren't
deleted a very, very long time ago.
Thanks again for the clarification. Your initial --notests was an option I
was unaware of and I didn't take the time to try variations. I was familiar
with invoking test names by regex I just thought it was more a convention.
Regards
Ronald
On Tue, Apr 28, 2015 at 2:48 PM, Doug Hellmann
On Tue, 2015-04-28 at 16:08 -0400, Jay Pipes wrote:
Honestly, I see no problem with some helper bash scripts that simplify
life for new contributors. The bash scripts do wonders for developers
new to OpenStack or Python coding by having a pretty easy and readable
way of determining what CLI
On 2015-04-28 16:08:03 -0400 (-0400), Jay Pipes wrote:
Honestly, I see no problem with some helper bash scripts that
simplify life for new contributors.
[...]
Well, the main downside to them is that rather than serving as
documentation of how to run the tests, they serve as a temptation to
Excerpts from Kevin L. Mitchell's message of 2015-04-28 08:15:51 -0700:
On Mon, 2015-04-27 at 15:54 -0700, Clint Byrum wrote:
Excerpts from Kevin L. Mitchell's message of 2015-04-27 15:38:25 -0700:
On Mon, 2015-04-27 at 21:42 +, Jeremy Stanley wrote:
I consider it an unfortunate
Thanks Doug. For others following this thread. The following creates and
activates the tox virtual environment.
# Note: its --spacenotests not --notests
$ tox -epy27 -- notests
$ source .tox/py27/bin/activate
(py27)$ openstack help
--
Excerpts from Ronald Bradford's message of 2015-04-28 14:24:37 -0400:
Thanks Doug. For others following this thread. The following creates and
activates the tox virtual environment.
# Note: its --spacenotests not --notests
Sorry, that was a typo on my part. The option name is actually
On 29 April 2015 at 06:24, Ronald Bradford m...@ronaldbradford.com wrote:
Thanks Doug. For others following this thread. The following creates and
activates the tox virtual environment.
# Note: its --spacenotests not --notests
$ tox -epy27 -- notests
$ source .tox/py27/bin/activate
(py27)$
On Tue, 2015-04-28 at 10:40 -0700, Clint Byrum wrote:
No dice. I don't want to have to parse the tox.ini directly. We're
talking about automated tests here, by the way.
Why not? It's an ini file, with a stable interface.
Yes, but it's tox's perview. Also, it's not just the command; I
Excerpts from Jeremy Stanley's message of 2015-04-27 21:42:15 +:
On 2015-04-27 17:07:56 -0400 (-0400), Ronald Bradford wrote:
[...]
Specifically, the following two code snippets have become SOP (Standard
Operating Procedure) jumping around VMs and projects and I suspect if you
are a
On 2015-04-27 17:07:56 -0400 (-0400), Ronald Bradford wrote:
[...]
Specifically, the following two code snippets have become SOP (Standard
Operating Procedure) jumping around VMs and projects and I suspect if you
are a developer of this project, something you are very familiar with.
[...]
Hi All,
I have recently become involved in OpenStack development. After installing
a few devstacks (and buying some H/W for my own physical cloud) I settled
into learning, reviewing and debugging the Python OpenStack Client (seemed
an easy access point). I even published a blog post just 7 days
Excerpts from Kevin L. Mitchell's message of 2015-04-27 15:38:25 -0700:
On Mon, 2015-04-27 at 21:42 +, Jeremy Stanley wrote:
I consider it an unfortunate oversight that those files weren't
deleted a very, very long time ago.
Unfortunately, there's one problem with that: you can't tell
On Mon, 2015-04-27 at 21:42 +, Jeremy Stanley wrote:
I consider it an unfortunate oversight that those files weren't
deleted a very, very long time ago.
Unfortunately, there's one problem with that: you can't tell tox to use
a virtualenv that you've built. We need this capability at
On 2015-04-27 17:38:25 -0500 (-0500), Kevin L. Mitchell wrote:
Unfortunately, there's one problem with that: you can't tell tox to use
a virtualenv that you've built. We need this capability at present, so
we have to run tests using run_tests.sh instead of tox :( I have an
issue open on tox
18 matches
Mail list logo
