Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Main recode/rework thread
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Phil Hassey  
View profile  
 More options Feb 19 2011, 12:52 am
From: Phil Hassey <philhas...@yahoo.com>
Date: Fri, 18 Feb 2011 21:52:18 -0800 (PST)
Local: Sat, Feb 19 2011 12:52 am
Subject: Re: [tinypy] Re: Main recode/rework thread

Just a couple thoughts:
- MIT license is quite important for tinypy to be useful.  Other licenses are too restrictive or too obscure to be generally useful.
- I think we'll all be quite interested to take a look at what you've got put together.
- "For example, modules are not permitted to have any static/global variables ..."
What does that mean?  Best I understand a modules contents is all global variables?
- "I just don't want to be in a situation where SoundSpectrum has to quibble with people or convince anyone of anything." 
I totally understand.  I think the people here will need to see what SS has created, and if it matches what we all want as tinypy then it could become the new edition of tinypy.  If it doesn't really match what we want, then it'll become it's own python variant.  Either way a situation where SS was at odds with anyone is to be avoided.
Cheers!
-Phil

--- On Fri, 2/18/11, Andy O'Meara <and...@gmail.com> wrote:

From: Andy O'Meara <and...@gmail.com>
Subject: Re: [tinypy] Re: Main recode/rework thread
To: tinypy@googlegroups.com
Cc: "Chris McCormick" <ch...@mccormick.cx>
Date: Friday, February 18, 2011, 2:26 PM

I don't want to make any promises yet, but I anticipate it will be the MIT license, in continuation and in the spirit of Phil's original work.  That said, there's a couple design principles that we probably won't be willing to compromise on, but those principles benefit the project than subtract from it.  For example, modules are not permitted to have any static/global variables since that would take away unrestricted multi-threaded support.  

I just don't want to be in a situation where SoundSpectrum has to quibble with people or convince anyone of anything.  I know that may sound like "our way or the highway", but I'm just trying to make the point that we unfortunately don't have the resources to do absolutely everything.  For example, I made the decision to remove the setup.py script stuff that jams all the .c files into one massive file for a list of reasons.  The Xcode/MSVS projects we now have instead are an improved and more straight-forward approach that I would prefer not to debate with people if their only basis is "that's not how we did it before" or to satisfy people who feel that it has to build from a clever script.  Not trying to be bossy with all of this, just trying to be honest and say that we don't have the resources to engage in lengthy debate unless it's with people who are putting in real contributions into this project.

On that note, if there are one or two people who really take to this project, SoundSpectrum will likely be willing to put them on payroll (depending on the kind of work planned).  

On Fri, Feb 18, 2011 at 2:27 AM, Chris McCormick <ch...@mccormick.cx> wrote:

Hi Andy,

Your work sounds awesome. What license will it be available under when you

release it?

On Thu, Feb 17, 2011 at 02:19:40PM -0600, Andy O'Meara wrote:
> Over the years I've been discouraged by folks who say they're interested in
> contributing but don't in the end, so that's why we've taken this project on
> privately and quietly thus far.  I've spent hundreds of hours going back and
> forth with certain people in the CPython dev community that frankly were
> just unwilling to listen to the needs and priorities of commercial app
> developers.  And frankly we're done with them, and they can have their
> butt-slow, lumbering, and thread-restrictive CPython.  They can also have
> their GIL while we do with Python what should have been done years ago (and
> why Lua is used over Python today by commercial developers that ship
> software that everyday people pay for--like us).

Thousands of people ship software every day that people pay for using CPython.

I am extremely grateful to the CPython devs for making such an awesome language

available as Free Software so that so many of us can benefit.

I look forward to seeing the source code and trying out your new iteration of

TinyPy, and I'm especially excited reading your comparisons to lua.

Cheers,

Chris.

-------------------

http://mccormick.cx

--

You received this message because you are subscribed to the Google Groups "tinypy" group.

To post to this group, send email to tinypy@googlegroups.com.

To unsubscribe from this group, send email to tinypy+unsubscribe@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/tinypy?hl=en.

--

You received this message because you are subscribed to the Google Groups "tinypy" group.

To post to this group, send email to tinypy@googlegroups.com.

To unsubscribe from this group, send email to tinypy+unsubscribe@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/tinypy?hl=en.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.