From: kokamoto@hera.eonet.ne.jp
To: 9fans@9fans.net
Subject: Re: [9fans] python2.7.6 and pip
Date: Fri, 19 Jun 2020 15:45:05 +0900 [thread overview]
Message-ID: <C14DCD0BF2594B592A009E0436CE4C1D@hera.eonet.ne.jp> (raw)
In-Reply-To: <15925339340.b02b.69278@composer.9fans.topicbox.com>
[-- Attachment #1: Type: text/plain, Size: 41 bytes --]
Ok, thanks
I'll write to you.
Kenji
[-- Attachment #2: Type: message/rfc822, Size: 9787 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 1087 bytes --]
Not sure why this text/plain message is marked invalid given it is, well, a plain text message. Here are the details:
Kenji,
TCP_NODELAY should be enabled in the 2.7.6 build.
Make sure you have all the APE patches from 9legacy or check the sources:
https://9p.io/sources/contrib/jas/cpython-src.arch.bz2
https://9p.io/sources/contrib/jas/src/cmd/cpython-src.arch.bz2
https://9p.io/sources/contrib/jas/src/ape-source.arch
Python 2.7.6 is the last viable release on Plan 9 until a rewrite of the _p9ssl.c version of the ssl module is completed. After 2.7.6 the Python group back ported the openssl module from Python 3 to the 2.7 branch and it broke the underlying ssl module hooks used in the Plan 9 Python 2.7.6 port that leveraged libsec instead of openssl.
Feel free to contact me off list if you need additional help.
Jeff
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Ta10c6b46f1dfa71e-M597edfb83f7d30f60951427f
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2.1.2: Type: text/html, Size: 4606 bytes --]
next prev parent reply other threads:[~2020-06-19 6:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 9:06 kokamoto
2020-06-19 2:19 ` [9fans] " Jeff Sickel
2020-06-19 2:32 ` jas
2020-06-19 6:45 ` kokamoto [this message]
2020-06-19 7:17 ` Jens Staal
2020-06-29 23:05 ` kokamoto
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=C14DCD0BF2594B592A009E0436CE4C1D@hera.eonet.ne.jp \
--to=kokamoto@hera.eonet.ne.jp \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).