public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "andrew.burgess at embecosm dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/27788] FAIL: gdb.python/py-startup-opt.exp: attr=dont_write_bytecode: testname: input 6: end
Date: Thu, 29 Apr 2021 09:27:25 +0000	[thread overview]
Message-ID: <bug-27788-4717-bhadcznywR@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27788-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27788

--- Comment #3 from Andrew Burgess <andrew.burgess at embecosm dot com> ---
I just posted this possible fix:
  https://sourceware.org/pipermail/gdb-patches/2021-April/178329.html

This doesn't unset the environment variable.  

Given that (until Python 3.8) we can't control where .pyc files are placed, I
didn't think it was kind to unset the environment variable when the developer
clearly does not want .pyc files written to their file system.

But I'd be interested in hearing different opinions.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-04-29  9:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28 18:30 [Bug testsuite/27788] New: " vries at gcc dot gnu.org
2021-04-28 18:32 ` [Bug testsuite/27788] " vries at gcc dot gnu.org
2021-04-29  8:14 ` vries at gcc dot gnu.org
2021-04-29  8:50 ` vries at gcc dot gnu.org
2021-04-29  9:27 ` andrew.burgess at embecosm dot com [this message]
2021-05-03 11:22 ` cvs-commit at gcc dot gnu.org
2021-05-04  6:02 ` vries at gcc dot gnu.org

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=bug-27788-4717-bhadcznywR@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).