public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Sharuzzaman Ahmat Raslan <sharuzzaman@gmail.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: python37-requests package does depends on charset_normalizer or chardet
Date: Wed, 23 Feb 2022 18:56:46 +0800	[thread overview]
Message-ID: <CAK+zucm_abE4yU2CVJ4uPe6xwOyFnRrPF17ach9cPcif-wvGEQ@mail.gmail.com> (raw)
In-Reply-To: <CAK+zucn77L9Pw+P-osKSp2SoreyJ-g64EHamdL4iQFgzqAqaWg@mail.gmail.com>

On Wed, Feb 23, 2022 at 6:37 PM Sharuzzaman Ahmat Raslan
<sharuzzaman@gmail.com> wrote:
>
> Hi Cygwin package manager.
>
> I'm on my new laptop, and installing packages as necessary.
>
> After installing python37-requests, my program raised an exception like this:
>
> Traceback (most recent call last):
>   File "get_header.py", line 1, in <module>
>     import requests
>   File "/usr/lib/python3.7/site-packages/requests/__init__.py", line
> 100, in <module>
>     check_compatibility(urllib3.__version__, chardet_version,
> charset_normalizer_version)
>   File "/usr/lib/python3.7/site-packages/requests/__init__.py", line
> 85, in check_compatibility
>     raise Exception("You need either charset_normalizer or chardet installed")
> Exception: You need either charset_normalizer or chardet installed
>
> I did not see python37-requests depends or pulling in
> charset_normalizer or chardet during installation. Is that
> intentional?
>
> Thank you.


Installing python37-chardet manually clears the exception, but not
solving the initial issue.

Thank you.

-- 
Sharuzzaman Ahmat Raslan

  reply	other threads:[~2022-02-23 10:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23 10:37 Sharuzzaman Ahmat Raslan
2022-02-23 10:56 ` Sharuzzaman Ahmat Raslan [this message]
2022-02-23 14:57   ` Adam Dinwoodie
2022-02-25  8:40     ` Sharuzzaman Ahmat Raslan
2022-02-25  9:11       ` Adam Dinwoodie
2022-02-25  9:37         ` Marco Atzeri

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=CAK+zucm_abE4yU2CVJ4uPe6xwOyFnRrPF17ach9cPcif-wvGEQ@mail.gmail.com \
    --to=sharuzzaman@gmail.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).