public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Richard S. Gordon" <rigordo@comcast.net>
To: cygwin@cygwin.com
Cc: Richard Sanders Gordon <rigordo@comcast.net>
Subject: Python 3.6.1 fails to generate 256 colors, with xterm-256color, on Cygwin based 64-bit Windows 10.
Date: Sun, 11 Jun 2017 14:18:00 -0000	[thread overview]
Message-ID: <86DAFF59-6EA8-4288-9D7D-E3262988BD7C@comcast.net> (raw)

NOTES:

1. Python 3.6.1 generates 8 colors (64-color pairs), with xterm, on Cygwin
   based 32-bit Windows 10

2. Python 3.6.1 generates 16 colors (256-color pairs), with xterm-16color,
   on Cygwin based 32-bit Windows 10

3. Python 3.6.1 generates 256 colors (65536-color pairs), with xterm-256color,
   on Cygwin based 64-bit Windows 10. However, the generated colors appear to
   be corrupted by overloading text attribute with specified foreground and
   background colors.

   Fixing this Python 3.6.1 issue will probably require modification to the
   Python curses stdlib. Here is the ncurses 6.0 author's description of the
   notable changes that he made to ncurses 5.x in order to produce ncurses
   6.0 (excerpted from: http://invisible-island.net/ncurses/announce.html):

   a. Extend the cchar_t structure to allow more than 16 colors to be encoded.

   b. Modify the encoding of mouse state to make room for a 5th mouse button.
      That allows one to use ncurses with a wheel mouse with xterm or similar
      X terminal emulators.

4. Cygwin problem reporter's test platform is a 27" iMAC (with 3.5 GHz Intel
   Core i7, 16 GB 1600 MHz DDR3) running Mac OS 10.12.5 (Sierra). It includes
   support for Python 3.6.0. It uses the Parallels Desktop 12 for Mac (a
   hypervisor) to run the following guest operating system:

   a. Android 4,

   b. Linux (CentOS 7.2 & 7.3, Debian 8.7 & 8.8, Fedora 24 &25, OpenSUSE
      13.2, Scientific 7.2 & 7.3, Ubuntu 16.04 & 17.04)

   c. Solaris (OpenIndians Hipster 1610)

   d. Unix (PCDBSD 10.3 & TrueOS 12.0)

   e. Windows (10 32-bit, 10 64-bit) (NOTE: previously ran 32-bit XP, 7
      and 8.1). Only Windows 10, with Cygwin, includes support for
      Python 3.6.1 and support for xterm, xterm-16color and xterm-256olor.
      The other Guest Operating Systems typically support Python 3.4.x or
      Python 3.5.x with only xterm (8-color).

5. Cygwin problem reporter's suggest fixes:

   a. The fix to the Python 3.6.1 curses stdlib should only be applied to
      those 64-bit platform versions used with 64-bit ncurses 6.0.

   b. The fix should NOT apply to the Python 3.6.1 curses stdlib applied
      to those 32-bit platforms used with 32-bit ncurses 6.0, because the
      32-bit ncurses 6.0 API is backwards compatible to the 32-bit ncurses
      5.x API.

6. Cygwin Problem Reporter's Test Case:

   This Cygwin problem can be demonstrated by running the Problem Reporter's
   test_tsWxColorPalette.py in Python 3x (developer-sandbox) which can be
   found in https://github.com/rigordo959/tsWxGTUI_PyVx_Repository. 

Richard S. Gordon


--
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

             reply	other threads:[~2017-06-11 14:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-11 14:18 Richard S. Gordon [this message]
2017-06-11 15:44 ` Brian Inglis
2017-06-12  7:21 Richard S. Gordon

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=86DAFF59-6EA8-4288-9D7D-E3262988BD7C@comcast.net \
    --to=rigordo@comcast.net \
    --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).