From: Luther Thompson <lutheroto@gmail.com>
To: 33089@debbugs.gnu.org
Subject: [bug#33089] [PATCH] New package: python-ilinkedlist
Date: Thu, 18 Oct 2018 11:16:39 -0400 [thread overview]
Message-ID: <20181018111639.4aa7dc1c@gmail.com> (raw)
I've written a Python module. Here is my package definition for it.
Please let me know if I can make any improvements.
---BEGIN---
diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm
index 8261fefd9..59917feb7 100644
--- a/gnu/packages/python.scm
+++ b/gnu/packages/python.scm
@@ -14473,3 +14473,28 @@ extend common interfaces like NumPy, Pandas, or Python iterators to
larger-than-memory or distributed environments. These parallel collections
run on top of the dynamic task schedulers. ")
(license license:bsd-3)))
+
+(define-public python-ilinkedlist
+ (package
+ (name "python-ilinkedlist")
+ (version "0.1.0")
+ (source
+ (origin
+ (method url-fetch)
+ (uri (pypi-uri "ilinkedlist" version))
+ (sha256
+ (base32
+ "063c2gm4jkgkv0nsg7mrc8y0w82ms98l4xchmbrvr68cscglhk69"))))
+ (build-system python-build-system)
+ (native-inputs `(("python-pytest" ,python-pytest)))
+ (inputs `(("python" ,python)))
+ (home-page "https://github.com/luther9/ilinkedlist-py")
+ (synopsis "Immutable linked list library")
+ (description
+ "This is a implementation of immutable linked lists for Python. It
+contains @code{nil} (the empty linked list) and a @code{Pair} class for nodes.
+Since a linked list is treated as immutable, it is hashable, and its length can
+be retrieved in constant time. Some of the terminology is inspired by LISP. It
+is possible to create an improper list by creating a @code{Pair} with a non-list
+@code{cdr}.")
+ (license license:gpl3+)))
---END---
I sent this message last night, but I don't see it in the archives, so I'm
sending it again.
Regards,
Luther Thompson
reply other threads:[~2018-10-18 15:18 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181018111639.4aa7dc1c@gmail.com \
--to=lutheroto@gmail.com \
--cc=33089@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).