From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Python extraneous dependencies
Date: Tue, 26 Feb 2019 05:31:00 -0000 [thread overview]
Message-ID: <0966bd837e33ca9ff07b13271211b2f5d2939793.camel@cygwin.com> (raw)
In-Reply-To: <5c73e2de.1c69fb81.51805.32cd@mx.google.com>
On Mon, 2019-02-25 at 04:43 -0800, Steven Penny wrote:
> On Sun, 24 Feb 2019 17:42:36, Yaakov Selkowitz wrote:
> > On Sat, 2019-02-23 at 16:29 -0800, Steven Penny wrote:
> > > I noticed that "python36" requires "binutils".
> >
> > This is needed for ctypes.util.find_library(). FWIW, on Linux, not
> > only binutils is used, but also gcc.
> >
> > > Further, I noticed this dependency chain:
> > >
> > > python36 > libuuid-devel > pkg-config > libglib2.0_0
> >
> > Until 3.7, the uuid stdlib module loads libuuid via ctypes, hence the
> > dependency. In 3.7, there is a compiled binding, and so the -devel
> > dependency was dropped. Also, pkgconf will soon be providing and
> > replacing pkg-config, which will cause the glib2.0 dependency to be
> > dropped.
>
> thanks. i was interested further in comparison so i took this file:
>
> https://python.org/ftp/python/3.6.8/python-3.6.8-embed-amd64.zip
>
> then use tar for fair comparison:
>
> tar -a -c -f python-3.6.8-embed-amd64.tar.xz python-3.6.8-embed-amd64
Did you look at the contents of that zip file? It's quite minimal, and
therefore not a fair comparison at all.
> and that doesnt include the other packages i previously discussed. so it almost
> makes more sense to not even use the cygwin version?
Hardly, but discussing how/why *not* to use Cygwin is OT IMO.
--
Yaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-02-26 4:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-24 1:45 Steven Penny
2019-02-24 3:08 ` LRN
2019-02-25 2:24 ` Yaakov Selkowitz
2019-02-25 13:54 ` Steven Penny
2019-02-26 5:31 ` Yaakov Selkowitz [this message]
2019-02-26 9:48 ` Ray Donnelly
2019-03-26 2:39 ` Steven Penny
2019-03-26 14:08 ` Yaakov Selkowitz
2019-03-26 18:25 ` Steven Penny
2019-03-26 18:58 ` Yaakov Selkowitz
2019-03-26 23:09 ` Steven Penny
2019-04-21 15:46 ` Steven Penny
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=0966bd837e33ca9ff07b13271211b2f5d2939793.camel@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin@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).