From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: 29944@debbugs.gnu.org
Subject: [bug#29944] [PATCH 1/2] gnu: Add python2-pyro.
Date: Tue, 2 Jan 2018 16:52:14 +0100 [thread overview]
Message-ID: <m1wp10tfkw.fsf@ordinateur-de-catherine--konrad.home> (raw)
* gnu/packages/python.scm (python2-pyro): New public variable.
---
gnu/packages/python.scm | 29 +++++++++++++++++++++++++++++
1 file changed, 29 insertions(+)
diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm
index 07302c729..0dff54a1b 100644
--- a/gnu/packages/python.scm
+++ b/gnu/packages/python.scm
@@ -12180,3 +12180,32 @@ such as figshare or Zenodo.")
(define-public python2-semver
(package-with-python2 python-semver))
+
+(define-public python2-pyro
+ (package
+ (name "python2-pyro")
+ (version "3.16")
+ (source
+ (origin
+ (method url-fetch)
+ (uri (pypi-uri "Pyro" version))
+ (file-name (string-append "Pyro-" version ".tar.gz"))
+ (sha256
+ (base32
+ "0y75wzdqbjy565rpxaxscav4j8xg060sa90lnmb7aypgaf251v8v"))))
+ (build-system python-build-system)
+ (arguments
+ ;; Pyro is not compatible with Python 3
+ `(#:python ,python-2
+ ;; Pyro has no test cases for automatic execution
+ #:tests? #f))
+ (home-page "http://pythonhosted.org/Pyro/")
+ (synopsis "Distributed object manager for Python")
+ (description "Pyro is a Distributed Object Technology system
+written in Python that is designed to be easy to use. It resembles
+Java's Remote Method Invocation (RMI). It has less similarity to CORBA,
+which is a system and language independent Distributed Object Technology
+and has much more to offer than Pyro or RMI. Pyro 3.x is no
+longer maintained. New projects should use Pyro4 instead, which
+is the new Pyro version that is actively developed.")
+ (license license:expat)))
--
2.14.3 (Apple Git-98)
next reply other threads:[~2018-01-02 16:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 15:52 Konrad Hinsen [this message]
2018-01-04 17:46 ` bug#29944: [PATCH 1/2] gnu: Add python2-pyro Leo Famulari
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=m1wp10tfkw.fsf@ordinateur-de-catherine--konrad.home \
--to=konrad.hinsen@fastmail.net \
--cc=29944@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).