All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: autotest@test.kernel.org
Cc: kvm@vger.kernel.org, jadmanski@google.com,
	Lucas Meneghel Rodrigues <lmr@redhat.com>
Subject: [PATCH] Fixing undefined variable reference error in setup_modules.py
Date: Mon,  5 Oct 2009 15:25:38 -0300	[thread overview]
Message-ID: <1254767138-11669-1-git-send-email-lmr@redhat.com> (raw)

Fix an undefined variable reference error inside
client/setup_modules.py - just remove code that wasn't
supposed to be there.

3rd try: After IRC chat and investigation, this is a
best fix than my previous patch that tried to accomplish
the same fix.

Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
---
 client/setup_modules.py |    8 --------
 1 files changed, 0 insertions(+), 8 deletions(-)

diff --git a/client/setup_modules.py b/client/setup_modules.py
index dc255c4..6f2ea30 100644
--- a/client/setup_modules.py
+++ b/client/setup_modules.py
@@ -86,14 +86,6 @@ def _autotest_logging_handle_error(self, record):
         traceback.print_stack()
         sys.stderr.write('Future logging formatting exceptions disabled.\n')
 
-    if root_module_name == 'autotest_lib':
-        # Allow locally installed third party packages to be found
-        # before any that are installed on the system itself when not.
-        # running as a client.
-        # This is primarily for the benefit of frontend and tko so that they
-        # may use libraries other than those available as system packages.
-        sys.path.insert(0, os.path.join(base_path, "site-packages"))
-
 
 def _monkeypatch_logging_handle_error():
     # Hack out logging.py*
-- 
1.6.2.5


                 reply	other threads:[~2009-10-05 18:26 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=1254767138-11669-1-git-send-email-lmr@redhat.com \
    --to=lmr@redhat.com \
    --cc=autotest@test.kernel.org \
    --cc=jadmanski@google.com \
    --cc=kvm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.