Re: [Python-Dev] licensing
Guido van Rossum writes:
Greg Stein writes:
For example, can I take the async modules and build a commercial product on them?
Yes, my intent was that they go under the normal Python 'do what thou wilt' license. If I goofed in any way, please let me know!
As far as I know, yes. Sam Rushing promised me this when he gave them to me for inclusion. (I've had a complaint that they aren't the latest -- can someone confirm this?)
Guilty as charged. I've been tweaking them a bit lately, for performance, but anyone can grab the very latest versions out of the medusa CVS repository: CVSROOT=:pserver:medusa@seattle.nightmare.com:/usr/local/cvsroot (the password is 'medusa') Or download one of the snapshots. BTW, those particular files have always had the Python copyright/license. -Sam
Sam Rushing wrote:
Greg Stein writes:
For example, can I take the async modules and build a commercial product on them?
Yes, my intent was that they go under the normal Python 'do what thou wilt' license. If I goofed in any way, please let me know!
Nope... you haven't goofed. I was thrown off when a certain person (nudge, nudge) goofed in their upcoming book, which I recently reviewed. thx! -g -- Greg Stein, http://www.lyra.org/
Nope... you haven't goofed. I was thrown off when a certain person (nudge, nudge) goofed in their upcoming book, which I recently reviewed.
I now feel for the other Mark and David, Aaron et al, etc. Our book is out of date in a number of ways before the tech reviewers even saw it. Medusa wasnt a good example - I should have known better when I wrote it. But Pythonwin is a _real_ problem. Just as I start writing the book, Neil sends me a really cool editor control and it leads me down a path of IDLE/Pythonwin integration. So almost _everything_ I have already written on "IDEs for Python" is already out of date - and printing is not scheduled for a number of months. [This may help explain to Guido and Tim my recent fervour in this area - I want to get the "new look" Pythonwin ready for the book. I just yesterday got a dockable interactive window happening. Now adding a splitter window to each window to expose a pyclbr based tree control and then it is time to stop (and re-write that chapter :-] Mark.
[Mark Hammond]
... [This may help explain to Guido and Tim my recent fervour in this area - I want to get the "new look" Pythonwin ready for the book. I just yesterday got a dockable interactive window happening. Now adding a splitter window to each window to expose a pyclbr based tree control and then it is time to stop (and re-write that chapter :-]
All right! Do get the latest CVS versions of these files: pyclbr has been sped up a lot over the past two days, and is much less likely to get baffled now. And AutoIndent.py now defaults usetabs to 1 (which, of course, means it still uses spaces in new files <wink>).
participants (4)
-
Greg Stein -
Mark Hammond -
Sam Rushing -
Tim Peters