From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Vinicius Monego <monego@posteo.net>
Cc: 48614-done@debbugs.gnu.org
Subject: bug#48614: [PATCH 3/3] gnu: Add python-cartopy.
Date: Wed, 23 Jun 2021 06:53:59 +0200 [thread overview]
Message-ID: <20210623065359.450f512a@alma-ubu.fritz.box> (raw)
In-Reply-To: <5c9b02bbd244c522334ac9524eb79010e426feb2.camel@posteo.net>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
On Wed, 26 May 2021 18:00:10 +0000
Vinicius Monego <monego@posteo.net> wrote:
> Hi Björn,
>
> Sending a v2 with your suggestions.
>
> > Or is there a reason to have it in python-xyz.scm? WDYT?
>
> My personal preference is to have Python modules in python-* files,
> similar to how python-crypto and python-web are separate from crypto
> and web. But I'm not strong on this. Also, creating python-geo for
> this set would seem more controversial.
Pushed as
5ab7fbad27c652bb2a7143995970e8b5886a0cb6
Thanks.
> As a side note, there's a problem in python-shapely that it can't find
> libgeos and that will break cartopy at runtime :(
I tried out some examples from the gallery, they worked very nicely. Do
you still have problems? If so, would you fill out a bug report?
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2021-06-23 4:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-23 19:29 [bug#48614] [PATCH 0/3] gnu: Add python-cartopy Vinicius Monego
2021-05-23 19:31 ` [bug#48614] [PATCH 1/3] gnu: Add python-pyshp Vinicius Monego
2021-05-23 19:31 ` [bug#48614] [PATCH 2/3] gnu: Add python-pykdtree Vinicius Monego
2021-05-23 19:31 ` [bug#48614] [PATCH 3/3] gnu: Add python-cartopy Vinicius Monego
2021-05-24 23:11 ` Björn Höfling
2021-05-26 18:00 ` Vinicius Monego
2021-06-23 4:53 ` Björn Höfling [this message]
2021-06-23 10:06 ` Vinicius Monego
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=20210623065359.450f512a@alma-ubu.fritz.box \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=48614-done@debbugs.gnu.org \
--cc=monego@posteo.net \
/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).