public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Emilio Rojas <eorojas@gmail.com>
To: marco atzeri <marco.atzeri@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: ipython failing after last python code update.
Date: Fri, 2 Feb 2024 10:14:43 -0800	[thread overview]
Message-ID: <CACyyGH+5wKGW49mxA3xraedQ1uEevvzYDsEAUadSGnz4AYkF-g@mail.gmail.com> (raw)
In-Reply-To: <CAB8Xom9WVGrvzJa6NXvCTBCXQuS-xnNYgkZ6aPa-tgGpFJ58=Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]

Thanks, it worked.  On the downside, it motivated me to get Windows python
working from the bash cmd line, so I'll likely be doing that.  I already
needed to run my scripts with the Windows python and it is two versions
ahead.
----------------
Emilio (eo) Rojas
---





On Fri, Feb 2, 2024 at 2:49 AM marco atzeri <marco.atzeri@gmail.com> wrote:

> On Fri, Feb 2, 2024 at 11:34 AM Emilio Rojas via Cygwin  wrote:
> >
> > I've attached the cygcheckout.out file.
> >
> > python3.9.18 seems to work fine, but when I run ipython8.18.1 it hangs
> > after tying any command.
> >
>
> Hi Emilio,
> you are in the right place.
>
> Others have reported similar problems on other python packages
>
> https://cygwin.com/pipermail/cygwin/2024-January/255273.html
> https://cygwin.com/pipermail/cygwin/2024-January/255267.html
>
> and going back to 3.9,16-1 solved their issue.
>
> Can you confirm that using previous version python 3.9.16-1 you have
> no problem ?
>
> The easy way to replace python39 version 3.9.18-1 with version
> 3.9.16-1 is to select "Sync" at the Package selection window
>
> Regards
> Marco
>

      reply	other threads:[~2024-02-02 18:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01 17:42 Emilio Rojas
2024-02-02 10:49 ` marco atzeri
2024-02-02 18:14   ` Emilio Rojas [this message]

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=CACyyGH+5wKGW49mxA3xraedQ1uEevvzYDsEAUadSGnz4AYkF-g@mail.gmail.com \
    --to=eorojas@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=marco.atzeri@gmail.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).