From: Eloitor <Eloitor@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] Fix path virtual environment message
Date: Thu, 09 Nov 2023 16:58:41 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47139@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 396 bytes --]
There is a new pull request by Eloitor against master on the void-packages repository
https://github.com/Eloitor/void-packages python-message
https://github.com/void-linux/void-packages/pull/47139
Fix path virtual environment message
#### Testing the changes
- I tested the changes in this PR: **YES**
A patch file from https://github.com/void-linux/void-packages/pull/47139.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python-message-47139.patch --]
[-- Type: text/x-diff, Size: 2997 bytes --]
From 7b6078722ed414e916ea8fc0269473e91e6f149c Mon Sep 17 00:00:00 2001
From: Eloi Torrents <eloitor@duck.com>
Date: Thu, 9 Nov 2023 16:56:40 +0100
Subject: [PATCH] Fix path virtual environment message
---
srcpkgs/python3.11/files/EXTERNALLY-MANAGED | 4 ++--
srcpkgs/python3.11/template | 2 +-
srcpkgs/python3/files/EXTERNALLY-MANAGED | 4 ++--
srcpkgs/python3/template | 2 +-
4 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/srcpkgs/python3.11/files/EXTERNALLY-MANAGED b/srcpkgs/python3.11/files/EXTERNALLY-MANAGED
index 22743f8d51db5..9fc7da0973404 100644
--- a/srcpkgs/python3.11/files/EXTERNALLY-MANAGED
+++ b/srcpkgs/python3.11/files/EXTERNALLY-MANAGED
@@ -8,7 +8,7 @@ Error=
environment, e.g.:
python3 -m venv /path/to/venv
- /path/to/venv/pip install <package>
+ /path/to/venv/bin/pip install <package>
Appending the flag --system-site-packages to the first command will give the
virtual environment access to any Python package installed via XBPS.
@@ -17,7 +17,7 @@ Error=
should automatically use the virtual environment. Alternatively, source its
activation script to add the environment to the command search path for a shell:
- . /path/to/venv/activate
+ . /path/to/venv/bin/activate
After activation, running
diff --git a/srcpkgs/python3.11/template b/srcpkgs/python3.11/template
index b384398c17520..cb6eec8a0c774 100644
--- a/srcpkgs/python3.11/template
+++ b/srcpkgs/python3.11/template
@@ -1,7 +1,7 @@
# Template file for 'python3.11'
pkgname=python3.11
version=3.11.6
-revision=1
+revision=2
build_style="gnu-configure"
configure_args="--enable-shared --enable-ipv6 --enable-optimizations
--enable-loadable-sqlite-extensions --with-computed-gotos
diff --git a/srcpkgs/python3/files/EXTERNALLY-MANAGED b/srcpkgs/python3/files/EXTERNALLY-MANAGED
index 22743f8d51db5..9fc7da0973404 100644
--- a/srcpkgs/python3/files/EXTERNALLY-MANAGED
+++ b/srcpkgs/python3/files/EXTERNALLY-MANAGED
@@ -8,7 +8,7 @@ Error=
environment, e.g.:
python3 -m venv /path/to/venv
- /path/to/venv/pip install <package>
+ /path/to/venv/bin/pip install <package>
Appending the flag --system-site-packages to the first command will give the
virtual environment access to any Python package installed via XBPS.
@@ -17,7 +17,7 @@ Error=
should automatically use the virtual environment. Alternatively, source its
activation script to add the environment to the command search path for a shell:
- . /path/to/venv/activate
+ . /path/to/venv/bin/activate
After activation, running
diff --git a/srcpkgs/python3/template b/srcpkgs/python3/template
index 970eb5dbf96a4..0c163dd500b55 100644
--- a/srcpkgs/python3/template
+++ b/srcpkgs/python3/template
@@ -4,7 +4,7 @@
#
pkgname=python3
version=3.12.0
-revision=1
+revision=2
build_style="gnu-configure"
configure_args="--enable-shared --enable-ipv6 --enable-optimizations
--enable-loadable-sqlite-extensions --with-computed-gotos
next reply other threads:[~2023-11-09 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 15:58 Eloitor [this message]
2023-12-30 20:01 ` [PR PATCH] [Updated] " Eloitor
2023-12-30 20:04 ` Eloitor
2024-02-15 5:42 ` [PR PATCH] [Updated] python3: fix " classabbyamp
2024-02-15 6:08 ` [PR PATCH] [Merged]: " classabbyamp
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47139@inbox.vuxu.org \
--to=eloitor@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).