Github messages for voidlinux
 help / color / mirror / Atom feed
From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-lsp-server: update to 1.7.1
Date: Tue, 07 Feb 2023 04:09:33 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42124@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 390 bytes --]

There is a new pull request by cinerea0 against master on the void-packages repository

https://github.com/cinerea0/void-packages pylsp
https://github.com/void-linux/void-packages/pull/42124

python3-lsp-server: update to 1.7.1
#### Testing the changes
- I tested the changes in this PR: **YES**


A patch file from https://github.com/void-linux/void-packages/pull/42124.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pylsp-42124.patch --]
[-- Type: text/x-diff, Size: 1509 bytes --]

From 9735c2ba3bb5dbf45e27e08b1748217f2551aee7 Mon Sep 17 00:00:00 2001
From: cinerea0 <cinerea0@disroot.org>
Date: Mon, 6 Feb 2023 22:08:38 -0500
Subject: [PATCH] python3-lsp-server: update to 1.7.1

---
 srcpkgs/python3-lsp-server/template | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/python3-lsp-server/template b/srcpkgs/python3-lsp-server/template
index 42f8b7703a33..a1ccc1e317bf 100644
--- a/srcpkgs/python3-lsp-server/template
+++ b/srcpkgs/python3-lsp-server/template
@@ -1,6 +1,6 @@
 # Template file for 'python3-lsp-server'
 pkgname=python3-lsp-server
-version=1.6.0
+version=1.7.1
 revision=1
 build_style=python3-module
 hostmakedepends="python3-setuptools python3-setuptools_scm python3-wheel"
@@ -16,14 +16,15 @@ license="MIT"
 homepage="https://github.com/python-lsp/python-lsp-server"
 changelog="https://raw.githubusercontent.com/python-lsp/python-lsp-server/develop/CHANGELOG.md"
 distfiles="${PYPI_SITE}/p/python-lsp-server/python-lsp-server-${version}.tar.gz"
-checksum=d75cdff9027c4212e5b9e861e9a0219219c8e2c69508d9f24949951dabd0dc1b
+checksum=67473bb301f35434b5fa8b21fc5ed5fac27dc8a8446ccec8bae456af52a0aef6
 
 do_check() {
 	python3 -m pytest \
 		--ignore=test/plugins/test_completion.py \
 		--ignore=test/plugins/test_pydocstyle_lint.py \
 		--ignore=test/plugins/test_rope_rename.py \
-		--ignore=test/plugins/test_yapf_format.py
+		--ignore=test/plugins/test_yapf_format.py \
+		--ignore=test/plugins/test_autoimport.py
 }
 
 post_install() {

             reply	other threads:[~2023-02-07  3:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07  3:09 cinerea0 [this message]
2023-02-10 22:57 ` [PR PATCH] [Merged]: " paper42

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-42124@inbox.vuxu.org \
    --to=cinerea0@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).