All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John B. Wyatt IV" <jwyatt@redhat.com>
To: John Kacur <jkacur@redhat.com>
Cc: Clark Williams <williams@redhat.com>,
	linux-rt-users@vger.kernel.org,
	kernel-rts-sst <kernel-rts-sst@redhat.com>,
	"John B. Wyatt IV" <sageofredondo@gmail.com>
Subject: Re: [PATCH] tuna: Add common virtual envs gitignores
Date: Mon, 22 Sep 2025 11:50:26 -0400	[thread overview]
Message-ID: <aNFwQtKJNcLAEsb0@thinkpad2024> (raw)
In-Reply-To: <3c66730b-a473-f103-bf13-cc19d312880d@redhat.com>

On Thu, Sep 18, 2025 at 02:06:06PM -0400, John Kacur wrote:
> I ran in a python virtual environment and only got an env directory which
> I deleted at the end. Are you actually using this

Yes. I was using a virtual environment to resolve issues with my
text editor's linter with GTK. I may need to do other things and
I want this support in there.

> or is this just
> theorectically something we might want to add?

Virtual environments are very common in Python projects. I would encourage
this project to support them. They have a variety of uses including
testing since you can pull in packages and easily use a different Python
version.

> I also understand you are trying to do your due dilligence by referencing
> where you copied this from, but then pulling in another license to do so.
> This is going to cause me headaches for something kind of trivial.

I understand this can pose some challenges, but, it is a snippet from a file
that has a Creative Commons public domain declaration from a well known
company. I suspect there are no license or copyright issues. I wanted to
include that linkage to provide a source for a code snippet, but we can
investigate removing the link and attribution. Being in the public
domain; I believe it should have no attribution requirements. Let me know if
any copyright or license issues arise.

--
Sincerely,
John Wyatt
Software Engineer, Core Kernel
Red Hat


      reply	other threads:[~2025-09-22 15:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-13 20:08 [PATCH] tuna: Add common virtual envs gitignores John B. Wyatt IV
2025-09-18 18:06 ` John Kacur
2025-09-22 15:50   ` John B. Wyatt IV [this message]

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=aNFwQtKJNcLAEsb0@thinkpad2024 \
    --to=jwyatt@redhat.com \
    --cc=jkacur@redhat.com \
    --cc=kernel-rts-sst@redhat.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=sageofredondo@gmail.com \
    --cc=williams@redhat.com \
    /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.