public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
Cc: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: Cygport user guide
Date: Tue, 9 Jun 2020 17:54:50 +0100	[thread overview]
Message-ID: <AM0PR05MB48983D94F5E454D6B894D1C7E7820@AM0PR05MB4898.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <CAB8Xom-__SfhWmjYHSfhGS=ErpVDUhzbowVNQioz71wgNRN=OA@mail.gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 901 bytes --]

On 09/06/2020 16:55, marco atzeri wrote:

> I suspect the user base is too small to justify the effort and I am afraid every
> major package needs a different approach.
> My octave and all other math programs know-how does not apply to the
> python effort I am working on ;-)
>
> From my side, I mainly learned by looking at Yaakov's packages as guidelines.
>
> Any specific argument are you looking for ?
>
> Regards
> Marco

Ah I see, that is fair enough.

That's how I'm learning too - glad I'm not the only one who gets a bit
confused at times :)

I was looking for information on PYTHON3_SITELIB but I have since worked
out that it always just points to Python 3.6's sitelib folder. Still
raises the question of how to handle building libraries/modules for
py3.7 and 3.8, but I guess most will wait until 3.7 or 3.8 becomes the
default version (?).

Thanks,

Hamish


[-- Attachment #1.1.2: 0x87B761FE07F548D6.asc --]
[-- Type: application/pgp-keys, Size: 3235 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-06-09 16:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-09 13:23 Hamish McIntyre-Bhatty
2020-06-09 15:55 ` marco atzeri
2020-06-09 16:54   ` Hamish McIntyre-Bhatty [this message]
2020-06-09 22:49   ` Doug Henderson
2020-06-12 14:44     ` Jon Turney

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=AM0PR05MB48983D94F5E454D6B894D1C7E7820@AM0PR05MB4898.eurprd05.prod.outlook.com \
    --to=hamishmb@live.co.uk \
    --cc=cygwin-apps@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).