tinypy Google Group

Re: [tinypy] Re: Using TinyPy as a sandbox

2010-01-06T16:36:02Z

Neat :) It took me a while to figure out what you are referring to, I haven't used safepy in ages ..
svn://[link]
Is a project I made a few years ago to run arbitrary python code 'safely' ..
Cheers!-Phil
To: "tinypy" <tinypy@googlegroups.com>
Apologies for the shameless plug. The Seattle project (

Re: Using TinyPy as a sandbox

2010-01-06T05:56:34Z

Apologies for the shameless plug. The Seattle project (
[link] ) has tried to extend Phil's
excellent safety mechanisms in his safe module and add some more
formal guarantees. We're quite a bit different from TinyPy so
Seattle may not meet your needs.
If you'd like more information, just let me know or email seattle-

Re: [tinypy] Re: Using TinyPy as a sandbox

2010-01-05T19:09:08Z

I know we've added some sandboxing to tinypy, but I don't believe anyone has done any kind of formal audit of the code. But, yeah, since there isn't a ton of code, it would certainly take less effort than with say Cpython.
If someone does audit the code, adding more tests would be swell.
Cheers!-Phil

Re: Using TinyPy as a sandbox

2010-01-05T18:11:49Z

Hi,
I think it would be easier to audit. There were also changes made to
it based on problems with cpythons sandbox code. However, I don't
think as many people have gone over it.
However, I still think you need to layer sandboxing. So also do
sandboxing at the OS level for better protection. All it takes is one

Using TinyPy as a sandbox

2010-01-05T07:32:11Z

Hi,
Can anyone tell me what state the sandbox is in?
Has it been given a thorough going over, looking for problems like
those present in CPython, when the various restricted execution
approaches are taken?
Cheers,
Richard.

Issue 46 in tinypy: tinypy and wicd to install on puppy linux

2010-01-04T00:06:49Z

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 46 by jwednesday: tinypy and wicd to install on puppy linux
[link]
What steps will reproduce the problem?
1. downloaded wicd went to install was missing python
2. downloaded python would not install downloaded tinypy

Re: [tinypy] input output

2009-12-31T21:44:29Z

Sorry I took a while getting this to you. It was apparently only on an
old machine I don't use much any more. If I get a chance to work on it
over break, I'll send you patch files. You can feel free to do the
same or if you think you get it in full working order, just submit a
big patch to the list and we can add it to the repositories.

Re: [tinypy] OpenGL wrapper for py2cpp

2009-12-30T00:58:59Z

Those files are included by modules/pygame.py
The examples/pygame.py is a SDL pixel mini version of pygame.
The modules/pygame.py is an OpenGL based mini version of pygame.
The example one is self contained and probably easier to follow since it doesn't do anything too fancy. The modules one includes different files depending on various command-line defines.

Re: [tinypy] Re: Tinypy to C++ compiler

2009-12-30T00:55:41Z

It is pretty much separate code altogether, actually. Once I'm satisfied with what I'm doing I might merge it in as a separate folder off of the trunk.
It uses the parser and tokenizer. And I could merge the tests together (which would give even better test coverage to normal tinypy).
-Phil

OpenGL wrapper for py2cpp

2009-12-29T23:19:15Z

Has an OpenGL "wrapper" been made for py2cpp? If not I think I'll make
one.
I couldn't figure out where or if the "drivers" in the modules/
directory are used. Are they? If I were to make an OpenGL wrapper
would I go about it like examples/pygame.py or modules/driver-
sdl.cpp ?
Thanks!
Joey

Re: Tinypy to C++ compiler

2009-12-29T23:36:08Z

Is tinypy modified at all for the py2cpp script? Or is it primarily a
collection of separate code that uses tinypy?
One option would be to maintain py2cpp as a branch of the tinypy
repository. That way you could have the pros while avoiding the cons
that would be due to merging it in.
I don't know how difficult it is to maintain a branch in subversion. I

Tinypy to C++ compiler

2009-12-01T22:22:30Z

Hey,
[link]
Spent the last week working on that. Going to try using it to do some rapid dev of iPhone games.
I did it in my own repository so I wouldn't clutter up tinypy with a million "commit -m 'blah'" type of messages. I'm not sure if I should add this into tinypy or leave it as a separate project. (Pros: we'd get a few more tests added into tinypy, and type annotation would get parsed, Cons: we'd have this other encoding script for compiling to C++, and maybe that's outside the scope of this project?) I'd vote for merging it in, since it would leave tinypy pretty much as-is. But I'm open for leaving it out if it seems like it'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.

Re: [tinypy] input output

2009-11-25T08:26:13Z

sure,
thanks... i can try.

2009/11/25 Seth Lemons <ulf...@gmail.com>

--
Vittoria Cozza
[link]
[link]

Re: [tinypy] input output

2009-11-24T23:37:32Z

I worked on a sys module a while back. I had a bit of the IO stuff
implemented, but I don't have the code at hand right now. If I can
find it, would you like to work on finishing it up? I likely won't get
time to work on it again until late December or January.

Seth

On Tue, Nov 24, 2009 at 9:03 AM, Donny Viszneki

Re: [tinypy] input output

2009-11-24T14:03:56Z

If tinypy is primarily intended for embedding in other applications,
there's probably no great reason to incorporate all the standard I/O
functions just to have the embedder have to reimplement them anyhow.

--
[link]