Request for SIG Creation
"Greg Copeland" <[email protected]> Thu, 28 Oct 2004 12:55:07 -0500
| Newsgroups | gmane.comp.python.meta |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============1627741954==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C4BD17.434861F4"
This is a multi-part message in MIME format.
------_=_NextPart_001_01C4BD17.434861F4
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
I would like to create a SIG for porting and supporting Python on
VxWorks. On python.org, there are references that such a port exists,
however, it is, by far, inaccurate as it is incomplete and out of date
(python 1.5 days). According to the SIG guidelines, I'm submitting a
formal request to create a SIG.
=20
Mission: To port and maintain a recent *stable* release of Python
(2.3.4) to VxWorks for eventual inclusion.
=20
Expiration: I'm not sure here. If it does get accepted into the
standard distribution, then a 6-month expiration is fine. If it will
never be accepted as part of the standard, then it should remain
open-ended.
=20
Informal Blurb: Python on VxWorks
=20
Formal Blub: My intention is to port and maintain Python 2.3.4 to
VxWorks for eventual inclusion back to the source tree. While my target
processor is XScale, I intend for the effort to be processor agnostic.
I periodically see people making this request and accordingly, see the
need for VxPython SIG.
=20
=20
Best Regards,
=20
Greg Copeland
=20
=20
------_=_NextPart_001_01C4BD17.434861F4
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Arial;
color:windowtext;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=3DEN-US link=3Dblue vlink=3Dpurple>
<div class=3DSection1>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I would like to create a SIG for porting and =
supporting
Python on VxWorks. On python.org, there are references that such a =
port
exists, however, it is, by far, inaccurate as it is incomplete and out =
of date
(python 1.5 days). According to the SIG guidelines, I’m =
submitting a
formal request to create a SIG.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><st1:place w:st=3D"on"><font size=3D2 =
face=3DArial><span
=
style=3D'font-size:10.0pt;font-family:Arial'>Mission</span></font></st1:p=
lace><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>: To port
and maintain a recent *<b><span =
style=3D'font-weight:bold'>stable</span></b>*
release of Python (2.3.4) to VxWorks for eventual =
inclusion.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Expiration: I’m not sure here. If =
it does
get accepted into the standard distribution, then a 6-month expiration =
is
fine. If it will never be accepted as part of the standard, then =
it
should remain open-ended.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Informal Blurb: Python on =
VxWorks<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Formal Blub: My intention is to port and =
maintain Python
2.3.4 to VxWorks for eventual inclusion back to the source tree. =
While my
target processor is XScale, I intend for the effort to be processor
agnostic. I periodically see people making this request and =
accordingly, see
the need for VxPython SIG.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Best Regards,</span></font><o:p></o:p></p>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> <o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Greg Copeland</span></font><o:p></o:p></p>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span><o:p></o:p></font></p>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</body>
</html>
------_=_NextPart_001_01C4BD17.434861F4--
--===============1627741954==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Meta-sig maillist - [email protected]
http://mail.python.org/mailman/listinfo/meta-sig
--===============1627741954==--