From: Steven Stallion <sstallion@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Python3 for Plan9
Date: Fri, 16 Aug 2013 15:23:23 -0700 [thread overview]
Message-ID: <CAGGHmKFcj6=o7ByvRTjq2AJCXbU6szDopNavPrrf7kQ7SmH=aw@mail.gmail.com> (raw)
In-Reply-To: <D5B13650-6575-4A4B-A55C-5F50FAA69B4D@corpus-callosum.com>
Interesting. Your factotum change broke global authentication. The
purpose of the * realm (look at the comments at the top of
factotum.py) was intended to act as a default. Please fix this.
On Fri, Aug 16, 2013 at 2:52 PM, Jeff Sickel <jas@corpus-callosum.com> wrote:
> Just remember that there is a small mercurial dependency that's currently not
> fully tracked. Our patches to Selenic have started to be rolled in, but it may
> still take a few more days before a Mercurial 2.7.1 release that has all of our
> changes in place.
>
> Feel free to track the cpython bitbucket fork for our most recent changes.
> The mercurial pieces will be updated in short order. And, as time allows, I'll
> try my best to remember to push changes up to my contrib area on sources.
>
> -jas
>
>
>
> On Aug 13, 2013, at 11:40 PM, michaelian ennis <michaelian.ennis@gmail.com> wrote:
>
>> I think you will find most things sought after from python 3 are available in 2.7. In addition there is a plan9 module included giving you the building blocks to build plan9-centric tools. https://bitbucket.org/jas/cpython
>>
>> Ian
>>
>>
>> On Tue, Aug 13, 2013 at 4:58 AM, Devyn Collier Johnson <devyncjohnson@gmail.com> wrote:
>>
>> On 08/12/2013 10:12 PM, Matthew Veety wrote:
>> No it is. Just use the compilers for the other arch.
>>
>> On Aug 12, 2013, at 21:35, Devyn Collier Johnson <devyncjohnson@gmail.com> wrote:
>>
>> On 08/12/2013 07:23 PM, erik quanstrom wrote:
>> On Mon Aug 12 19:15:36 EDT 2013, devyncjohnson@gmail.com wrote:
>> Aloha Plan9 fans!
>>
>> I am new to Plan9 and I plan to use it for robotics. However, I am
>> unable to find a Python3 interpreter that would run on a Plan9 system on
>> an ARM system. Does such a package exist?
>> not out o the box, but jas' python port on bitbucket is close. we haven't
>> tried out python 3 yet, and we've been ignoring arm but we are following
>> the tip, so python 3 might just work on 386/amd64.
>>
>> i- erik
>> Thanks anyway. I am new to cross compiling, so I assume it is not as easy as downloading the source code and compiling?
>>
>> Mahalo,
>>
>> DevynCJohnson@Gmail.com
>>
>>
>> Thanks! I will try that sometime.
>>
>> Mahalo,
>>
>> DCJ
>>
>>
>
>
next prev parent reply other threads:[~2013-08-16 22:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 23:13 Devyn Collier Johnson
2013-08-12 23:16 ` Jacob Todd
2013-08-12 23:23 ` erik quanstrom
2013-08-13 1:35 ` Devyn Collier Johnson
2013-08-13 2:12 ` Matthew Veety
2013-08-13 11:58 ` Devyn Collier Johnson
2013-08-14 4:40 ` michaelian ennis
2013-08-16 21:52 ` Jeff Sickel
2013-08-16 22:23 ` Steven Stallion [this message]
2013-08-17 0:21 ` Devyn Collier Johnson
2013-08-17 6:20 ` Alex Jordan
2013-08-17 11:03 ` Devyn Collier Johnson
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='CAGGHmKFcj6=o7ByvRTjq2AJCXbU6szDopNavPrrf7kQ7SmH=aw@mail.gmail.com' \
--to=sstallion@gmail.com \
--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).