<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<rss version="2.0">
  <channel>
  <title>tinypy Google Group</title>
  <link>http://groups.google.com/group/tinypy</link>
  <description>tinypy is a minimalist implementation of python in 64k of code. This group is for both general and development discussion of tinypy, talking about your projects that use tinypy, or anything else reasonably related to tinypy.</description>
  <language>en</language>
  <item>
  <title>Re: [tinypy] Re: Using TinyPy as a sandbox</title>
  <link>http://groups.google.com/group/tinypy/browse_thread/thread/e7633cde434a5491/8557a13dfefd598e?show_docid=8557a13dfefd598e</link>
  <description>
  Neat :)  It took me a while to figure out what you are referring to, I haven&#39;t used safepy in ages .. &lt;br&gt; svn://&lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://www.imitationpickles.org/pysafe/trunk &quot;&gt;[link]&lt;/a&gt; &lt;br&gt; Is a project I made a few years ago to run arbitrary python code &#39;safely&#39; ..  &lt;br&gt; Cheers!-Phil &lt;br&gt; To: &amp;quot;tinypy&amp;quot; &amp;lt;tinypy@googlegroups.com&amp;gt; &lt;br&gt; Apologies for the shameless plug.   The Seattle project (
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/tinypy/browse_thread/thread/e7633cde434a5491/8557a13dfefd598e?show_docid=8557a13dfefd598e</guid>
  <author>
  philhas...@yahoo.com
  (Phil Hassey)
  </author>
  <pubDate>Wed, 06 Jan 2010 16:36:02 UT
</pubDate>
  </item>
  <item>
  <title>Re: Using TinyPy as a sandbox</title>
  <link>http://groups.google.com/group/tinypy/browse_thread/thread/e7633cde434a5491/9336e211ae94ca06?show_docid=9336e211ae94ca06</link>
  <description>
  Apologies for the shameless plug. The Seattle project ( &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;https://seattle.cs.washington.edu/&quot;&gt;[link]&lt;/a&gt; ) has tried to extend Phil&#39;s &lt;br&gt; excellent safety mechanisms in his safe module and add some more &lt;br&gt; formal guarantees. We&#39;re quite a bit different from TinyPy so &lt;br&gt; Seattle may not meet your needs. &lt;br&gt; If you&#39;d like more information, just let me know or email seattle-
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/tinypy/browse_thread/thread/e7633cde434a5491/9336e211ae94ca06?show_docid=9336e211ae94ca06</guid>
  <author>
  justincap...@gmail.com
  (justinc@cs.washington.edu)
  </author>
  <pubDate>Wed, 06 Jan 2010 05:56:34 UT
</pubDate>
  </item>
  <item>
  <title>Re: [tinypy] Re: Using TinyPy as a sandbox</title>
  <link>http://groups.google.com/group/tinypy/browse_thread/thread/e7633cde434a5491/0f9a49b671780064?show_docid=0f9a49b671780064</link>
  <description>
  I know we&#39;ve added some sandboxing to tinypy, but I don&#39;t believe anyone has done any kind of formal audit of the code.  But, yeah, since there isn&#39;t a ton of code, it would certainly take less effort than with say Cpython. &lt;br&gt; If someone does audit the code, adding more tests would be swell. &lt;br&gt; Cheers!-Phil
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/tinypy/browse_thread/thread/e7633cde434a5491/0f9a49b671780064?show_docid=0f9a49b671780064</guid>
  <author>
  philhas...@yahoo.com
  (Phil Hassey)
  </author>
  <pubDate>Tue, 05 Jan 2010 19:09:08 UT
</pubDate>
  </item>
  <item>
  <title>Re: Using TinyPy as a sandbox</title>
  <link>http://groups.google.com/group/tinypy/browse_thread/thread/e7633cde434a5491/f402e982fbfc2bf9?show_docid=f402e982fbfc2bf9</link>
  <description>
  Hi, &lt;br&gt; I think it would be easier to audit. There were also changes made to &lt;br&gt; it based on problems with cpythons sandbox code. However, I don&#39;t &lt;br&gt; think as many people have gone over it. &lt;br&gt; However, I still think you need to layer sandboxing. So also do &lt;br&gt; sandboxing at the OS level for better protection. All it takes is one
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/tinypy/browse_thread/thread/e7633cde434a5491/f402e982fbfc2bf9?show_docid=f402e982fbfc2bf9</guid>
  <author>
  ren...@gmail.com
  (illume)
  </author>
  <pubDate>Tue, 05 Jan 2010 18:11:49 UT
</pubDate>
  </item>
  <item>
  <title>Using TinyPy as a sandbox</title>
  <link>http://groups.google.com/group/tinypy/browse_thread/thread/e7633cde434a5491/54ab7c8bf08db9fe?show_docid=54ab7c8bf08db9fe</link>
  <description>
  Hi, &lt;br&gt; Can anyone tell me what state the sandbox is in? &lt;br&gt; Has it been given a thorough going over, looking for problems like &lt;br&gt; those present in CPython, when the various restricted execution &lt;br&gt; approaches are taken? &lt;br&gt; Cheers, &lt;br&gt; Richard.
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/tinypy/browse_thread/thread/e7633cde434a5491/54ab7c8bf08db9fe?show_docid=54ab7c8bf08db9fe</guid>
  <author>
  richard.m....@gmail.com
  (Richard Tew)
  </author>
  <pubDate>Tue, 05 Jan 2010 07:32:11 UT
</pubDate>
  </item>
  <item>
  <title>Issue 46 in tinypy: tinypy and wicd to install on puppy linux</title>
  <link>http://groups.google.com/group/tinypy/browse_thread/thread/5861bb7bf9ed5991/26d707b9dd3864ee?show_docid=26d707b9dd3864ee</link>
  <description>
  Status: New &lt;br&gt; Owner: ---- &lt;br&gt; Labels: Type-Defect Priority-Medium &lt;br&gt; New issue 46 by jwednesday: tinypy and wicd to install on puppy linux &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://code.google.com/p/tinypy/issues/detail?id=46&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; What steps will reproduce the problem? &lt;br&gt; 1. downloaded wicd went to install was missing python &lt;br&gt; 2. downloaded python would not install downloaded tinypy
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/tinypy/browse_thread/thread/5861bb7bf9ed5991/26d707b9dd3864ee?show_docid=26d707b9dd3864ee</guid>
  <author>
  codesite-nore...@google.com
  </author>
  <pubDate>Mon, 04 Jan 2010 00:06:49 UT
</pubDate>
  </item>
  <item>
  <title>Re: [tinypy] input output</title>
  <link>http://groups.google.com/group/tinypy/browse_thread/thread/c6d1d93fb0e6becd/e5ce0dceec009cd4?show_docid=e5ce0dceec009cd4</link>
  <description>
  Sorry I took a while getting this to you. It was apparently only on an &lt;br&gt; old machine I don&#39;t use much any more. If I get a chance to work on it &lt;br&gt; over break, I&#39;ll send you patch files. You can feel free to do the &lt;br&gt; same or if you think you get it in full working order, just submit a &lt;br&gt; big patch to the list and we can add it to the repositories.
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/tinypy/browse_thread/thread/c6d1d93fb0e6becd/e5ce0dceec009cd4?show_docid=e5ce0dceec009cd4</guid>
  <author>
  ulf...@gmail.com
  (Seth Lemons)
  </author>
  <pubDate>Thu, 31 Dec 2009 21:44:29 UT
</pubDate>
  </item>
  <item>
  <title>Re: [tinypy] OpenGL wrapper for py2cpp</title>
  <link>http://groups.google.com/group/tinypy/browse_thread/thread/a587636ccc5604bf/3ebe1b9da0685cdc?show_docid=3ebe1b9da0685cdc</link>
  <description>
  Those files are included by modules/pygame.py &lt;br&gt; The examples/pygame.py is a SDL pixel mini version of pygame. &lt;br&gt; The modules/pygame.py is an OpenGL based mini version of pygame. &lt;br&gt; The example one is self contained and probably easier to follow since it doesn&#39;t do anything too fancy.  The modules one includes different files depending on various command-line defines.
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/tinypy/browse_thread/thread/a587636ccc5604bf/3ebe1b9da0685cdc?show_docid=3ebe1b9da0685cdc</guid>
  <author>
  philhas...@yahoo.com
  (Phil Hassey)
  </author>
  <pubDate>Wed, 30 Dec 2009 00:58:59 UT
</pubDate>
  </item>
  <item>
  <title>Re: [tinypy] Re: Tinypy to C++ compiler</title>
  <link>http://groups.google.com/group/tinypy/browse_thread/thread/b81af24a7cd263ed/24b2d5f75dbe8794?show_docid=24b2d5f75dbe8794</link>
  <description>
  It is pretty much separate code altogether, actually.  Once I&#39;m satisfied with what I&#39;m doing I might merge it in as a separate folder off of the trunk.   &lt;br&gt; It uses the parser and tokenizer.  And I could merge the tests together (which would give even better test coverage to normal tinypy).   &lt;br&gt; -Phil
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/tinypy/browse_thread/thread/b81af24a7cd263ed/24b2d5f75dbe8794?show_docid=24b2d5f75dbe8794</guid>
  <author>
  philhas...@yahoo.com
  (Phil Hassey)
  </author>
  <pubDate>Wed, 30 Dec 2009 00:55:41 UT
</pubDate>
  </item>
  <item>
  <title>OpenGL wrapper for py2cpp</title>
  <link>http://groups.google.com/group/tinypy/browse_thread/thread/a587636ccc5604bf/41ceb61abc819f02?show_docid=41ceb61abc819f02</link>
  <description>
  Has an OpenGL &amp;quot;wrapper&amp;quot; been made for py2cpp? If not I think I&#39;ll make &lt;br&gt; one. &lt;br&gt; I couldn&#39;t figure out where or if the &amp;quot;drivers&amp;quot; in the modules/ &lt;br&gt; directory are used. Are they? If I were to make an OpenGL wrapper &lt;br&gt; would I go about it like examples/pygame.py or modules/driver- &lt;br&gt; sdl.cpp ? &lt;br&gt; Thanks! &lt;br&gt; Joey
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/tinypy/browse_thread/thread/a587636ccc5604bf/41ceb61abc819f02?show_docid=41ceb61abc819f02</guid>
  <author>
  marshallpeng...@gmail.com
  (Joey Marshall)
  </author>
  <pubDate>Tue, 29 Dec 2009 23:19:15 UT
</pubDate>
  </item>
  <item>
  <title>Re: Tinypy to C++ compiler</title>
  <link>http://groups.google.com/group/tinypy/browse_thread/thread/b81af24a7cd263ed/bc9d9f5b1d3d6757?show_docid=bc9d9f5b1d3d6757</link>
  <description>
  Is tinypy modified at all for the py2cpp script? Or is it primarily a &lt;br&gt; collection of separate code that uses tinypy? &lt;br&gt; One option would be to maintain py2cpp as a branch of the tinypy &lt;br&gt; repository. That way you could have the pros while avoiding the cons &lt;br&gt; that would be due to merging it in. &lt;br&gt; I don&#39;t know how difficult it is to maintain a branch in subversion. I
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/tinypy/browse_thread/thread/b81af24a7cd263ed/bc9d9f5b1d3d6757?show_docid=bc9d9f5b1d3d6757</guid>
  <author>
  marshallpeng...@gmail.com
  (Joey Marshall)
  </author>
  <pubDate>Tue, 29 Dec 2009 23:36:08 UT
</pubDate>
  </item>
  <item>
  <title>Tinypy to C++ compiler</title>
  <link>http://groups.google.com/group/tinypy/browse_thread/thread/b81af24a7cd263ed/39c86571434ec9c4?show_docid=39c86571434ec9c4</link>
  <description>
  Hey, &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://www.philhassey.com/blog/2009/12/01/restricted-tinypy-to-c-compiler/&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; Spent the last week working on that.  Going to try using it to do some rapid dev of iPhone games. &lt;br&gt; I did it in my own repository so I wouldn&#39;t clutter up tinypy with a million &amp;quot;commit -m &#39;blah&#39;&amp;quot; type of messages.  I&#39;m not sure if I should add this into tinypy or leave it as a separate project.  (Pros: we&#39;d get a few more tests added into tinypy, and type annotation would get parsed, Cons: we&#39;d have this other encoding script for compiling to C++, and maybe that&#39;s outside the scope of this project?)  I&#39;d vote for merging it in, since it would leave tinypy pretty much as-is.  But I&#39;m open for leaving it out if it seems like it&#39;d just be adding a few more distracting files to tinypy.  Another con is that it is all C++ code, and our tinypy codebase is very much C oriented right now.  So it really is a different project.
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/tinypy/browse_thread/thread/b81af24a7cd263ed/39c86571434ec9c4?show_docid=39c86571434ec9c4</guid>
  <author>
  philhas...@yahoo.com
  (Phil Hassey)
  </author>
  <pubDate>Tue, 01 Dec 2009 22:22:30 UT
</pubDate>
  </item>
  <item>
  <title>Re: [tinypy] input output</title>
  <link>http://groups.google.com/group/tinypy/browse_thread/thread/c6d1d93fb0e6becd/5081757af7d6de3f?show_docid=5081757af7d6de3f</link>
  <description>
  sure, &lt;br&gt; thanks... i can try. &lt;br&gt; &lt;p&gt;2009/11/25 Seth Lemons &amp;lt;ulf...@gmail.com&amp;gt; &lt;br&gt; &lt;p&gt;-- &lt;br&gt; Vittoria Cozza &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://www.di.uniba.it/~hixos/&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://covitti.googlepages.com&quot;&gt;[link]&lt;/a&gt;
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/tinypy/browse_thread/thread/c6d1d93fb0e6becd/5081757af7d6de3f?show_docid=5081757af7d6de3f</guid>
  <author>
  covi...@gmail.com
  (Vittoria Cozza)
  </author>
  <pubDate>Wed, 25 Nov 2009 08:26:13 UT
</pubDate>
  </item>
  <item>
  <title>Re: [tinypy] input output</title>
  <link>http://groups.google.com/group/tinypy/browse_thread/thread/c6d1d93fb0e6becd/6c8dc1eb6b7bc0d3?show_docid=6c8dc1eb6b7bc0d3</link>
  <description>
  I worked on a sys module a while back. I had a bit of the IO stuff &lt;br&gt; implemented, but I don&#39;t have the code at hand right now. If I can &lt;br&gt; find it, would you like to work on finishing it up? I likely won&#39;t get &lt;br&gt; time to work on it again until late December or January. &lt;br&gt; &lt;p&gt;Seth &lt;br&gt; &lt;p&gt;On Tue, Nov 24, 2009 at 9:03 AM, Donny Viszneki
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/tinypy/browse_thread/thread/c6d1d93fb0e6becd/6c8dc1eb6b7bc0d3?show_docid=6c8dc1eb6b7bc0d3</guid>
  <author>
  ulf...@gmail.com
  (Seth Lemons)
  </author>
  <pubDate>Tue, 24 Nov 2009 23:37:32 UT
</pubDate>
  </item>
  <item>
  <title>Re: [tinypy] input output</title>
  <link>http://groups.google.com/group/tinypy/browse_thread/thread/c6d1d93fb0e6becd/f658d1798b318034?show_docid=f658d1798b318034</link>
  <description>
  If tinypy is primarily intended for embedding in other applications, &lt;br&gt; there&#39;s probably no great reason to incorporate all the standard I/O &lt;br&gt; functions just to have the embedder have to reimplement them anyhow. &lt;br&gt; &lt;p&gt;-- &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://codebad.com/&quot;&gt;[link]&lt;/a&gt;
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/tinypy/browse_thread/thread/c6d1d93fb0e6becd/f658d1798b318034?show_docid=f658d1798b318034</guid>
  <author>
  donny.viszn...@gmail.com
  (Donny Viszneki)
  </author>
  <pubDate>Tue, 24 Nov 2009 14:03:56 UT
</pubDate>
  </item>
  </channel>
</rss>
