Comments on: Python For Blender Wiki Site – BlenderPython.org http://www.blendernation.com/python-for-blender-wiki-site-blenderpythonorg/ Fresh Blender News, Every Day Sun, 22 Nov 2009 01:06:38 +0100 http://wordpress.org/?v=2.8.6 hourly 1 By: Haunt_House http://www.blendernation.com/python-for-blender-wiki-site-blenderpythonorg/comment-page-1/#comment-351449 Haunt_House Thu, 10 Jul 2008 22:24:08 +0000 http://www.blendernation.com/2006/08/29/python-for-blender-wiki-site-blenderpythonorg/#comment-351449 Seems like the site is discontinued for good. Was a useful idea Seems like the site is discontinued for good. Was a useful idea

]]> By: oli http://www.blendernation.com/python-for-blender-wiki-site-blenderpythonorg/comment-page-1/#comment-279333 oli Sat, 29 Mar 2008 10:16:11 +0000 http://www.blendernation.com/2006/08/29/python-for-blender-wiki-site-blenderpythonorg/#comment-279333 BlenderPython.org is higly commercialized wiht advertisments and does not contain anymore information about Blender, python and the like, as far I could see anything apart from Ad-links. No thanks. BlenderPython.org is higly commercialized wiht advertisments and does not contain anymore information about Blender, python and the like, as far I could see anything apart from Ad-links. No thanks.

]]> By: qedqubit http://www.blendernation.com/python-for-blender-wiki-site-blenderpythonorg/comment-page-1/#comment-9491 qedqubit Fri, 01 Sep 2006 19:58:23 +0000 http://www.blendernation.com/2006/08/29/python-for-blender-wiki-site-blenderpythonorg/#comment-9491 show show show the code gently on the screen errorly,errorly,errorly,errorly sofar it remains unseen. 'The page cannot be displayed' dammit ! i've been longing for something like such a site ! show show
show the code
gently on the screen
errorly,errorly,errorly,errorly
sofar it remains unseen.

'The page cannot be displayed'

dammit !

i've been longing for something like such a site !

]]> By: James Campanella http://www.blendernation.com/python-for-blender-wiki-site-blenderpythonorg/comment-page-1/#comment-9415 James Campanella Thu, 31 Aug 2006 20:57:26 +0000 http://www.blendernation.com/2006/08/29/python-for-blender-wiki-site-blenderpythonorg/#comment-9415 Oops, left out the web address in my last post which was http://www.python.org/download/releases/2.4.3/license/ which was left earlier but ahd a problem with the link. Oops, left out the web address in my last post which was http://www.python.org/download/releases/2.4.3/license/ which was left earlier but ahd a problem with the link.

]]> By: James Campanella http://www.blendernation.com/python-for-blender-wiki-site-blenderpythonorg/comment-page-1/#comment-9403 James Campanella Thu, 31 Aug 2006 17:15:00 +0000 http://www.blendernation.com/2006/08/29/python-for-blender-wiki-site-blenderpythonorg/#comment-9403 License agreements such as the Python Software Foundation (PSF) license are not hard to understand, if read. Granted the language used is not that of fiction and there may be some "big" words in it, but they can all be found in a dictionary if one doesn't understand them. At anyrate, here is the license simplified in laymans terms. Python License Explained (based off the 2.4 license from 1. License is between the user of Python (source, binary, and/or documentation), and the Python Software Foundation. 2. If you use Python, as in the standard system libraries, binary, or source code, embeded in another project you must include the PSF License as a part of your project. For example, Blender includes some libraries and a python interperter as part of it's distribution, If you look in the installation directory of Blender you will find the Python license there. 3. If you change any of Python, not scripts you've created, but the actual system libraries, or binaries, you must include a copy of the PSF License with your product, and a brief summary of the changes made. A brief summary would not necessarily have to reveal your source code. 4. Software is made available "As is" meaning there could be bugs that they haven't found, and probably are as no software is completely perfect and bugfree. 5. The Python Software Foundation is not responsible for damage to your computer, if you for instance, create an endless loop, and your AMD crunches away and heats itself into an explosion of silicon and metal, or if there is some bug in the software that damages any part of your computer. 6. If you break any part of this license, we revoke your license to use the software, and if you continue to use the software you are doing so illegally and could be sued. 7. This license doesn't make you in anyway related to or a part of the Python Software Foundation. 8. By copying, installing, or otherwise using Python you agree to abide by the terms in this license. Hope this helps, and note this is the license for Python as a language and the particular binaries distributed by the python website. What products you create can be under whatever license you want to make it be. But if you distribute your software and include system libraries or other files you got from Python as part of the python installation or source, you must include the PSF license and any changes you made to Python. Clear as Mud? License agreements such as the Python Software Foundation (PSF) license are not hard to understand, if read. Granted the language used is not that of fiction and there may be some "big" words in it, but they can all be found in a dictionary if one doesn't understand them. At anyrate, here is the license simplified in laymans terms.

Python License Explained (based off the 2.4 license from

1. License is between the user of Python (source, binary, and/or documentation), and the Python Software Foundation.

2. If you use Python, as in the standard system libraries, binary, or source code, embeded in another project you must include the PSF License as a part of your project. For example, Blender includes some libraries and a python interperter as part of it's distribution, If you look in the installation directory of Blender you will find the Python license there.

3. If you change any of Python, not scripts you've created, but the actual system libraries, or binaries, you must include a copy of the PSF License with your product, and a brief summary of the changes made. A brief summary would not necessarily have to reveal your source code.

4. Software is made available "As is" meaning there could be bugs that they haven't found, and probably are as no software is completely perfect and bugfree.

5. The Python Software Foundation is not responsible for damage to your computer, if you for instance, create an endless loop, and your AMD crunches away and heats itself into an explosion of silicon and metal, or if there is some bug in the software that damages any part of your computer.

6. If you break any part of this license, we revoke your license to use the software, and if you continue to use the software you are doing so illegally and could be sued.

7. This license doesn't make you in anyway related to or a part of the Python Software Foundation.

8. By copying, installing, or otherwise using Python you agree to abide by the terms in this license.

Hope this helps, and note this is the license for Python as a language and the particular binaries distributed by the python website. What products you create can be under whatever license you want to make it be. But if you distribute your software and include system libraries or other files you got from Python as part of the python installation or source, you must include the PSF license and any changes you made to Python.

Clear as Mud?

]]> By: Gunnar Stahl http://www.blendernation.com/python-for-blender-wiki-site-blenderpythonorg/comment-page-1/#comment-9376 Gunnar Stahl Thu, 31 Aug 2006 10:58:18 +0000 http://www.blendernation.com/2006/08/29/python-for-blender-wiki-site-blenderpythonorg/#comment-9376 Hi Morris, maybe I am just stupid, but I do not understand your post. Joeri asked a question and I found his question to be a valid one. So I did some looking-up on my own and found some answers. And since I took Joeri's question serious I tried to provide a usefull answer. Yt, Gunnar Hi Morris,
maybe I am just stupid, but I do not understand your post. Joeri asked a question and I found his question to be a valid one. So I did some looking-up on my own and found some answers. And since I took Joeri's question serious I tried to provide a usefull answer.

Yt,

Gunnar

]]> By: Morris http://www.blendernation.com/python-for-blender-wiki-site-blenderpythonorg/comment-page-1/#comment-9353 Morris Thu, 31 Aug 2006 05:45:46 +0000 http://www.blendernation.com/2006/08/29/python-for-blender-wiki-site-blenderpythonorg/#comment-9353 It's OK gunny, Joeri knows everything. He's just seeing if anyone will show their ignorance by being worried or something It's OK gunny, Joeri knows everything. He's just seeing if anyone will show their ignorance by being worried or something

]]> By: gunnarstahl http://www.blendernation.com/python-for-blender-wiki-site-blenderpythonorg/comment-page-1/#comment-9308 gunnarstahl Wed, 30 Aug 2006 10:55:52 +0000 http://www.blendernation.com/2006/08/29/python-for-blender-wiki-site-blenderpythonorg/#comment-9308 He Joeri, I don't think that this holds true. First: Python is not gpl. You can read the current (2.4.3) licence in "http://www.python.org/download/releases/2.4.3/license/" . My understanding as a non-lawyer is that you have to put your versions, derivative works and such of python itself under this licence. From my understanding this does not cover the products you produce using python. As I understand it you can put any of your sources under any licence you want. But again, I am no lawyer. Yt, Gunnar He Joeri,
I don't think that this holds true. First: Python is not gpl. You can read the current (2.4.3) licence in "http://www.python.org/download/releases/2.4.3/license/" . My understanding as a non-lawyer is that you have to put your versions, derivative works and such of python itself under this licence.
From my understanding this does not cover the products you produce using python. As I understand it you can put any of your sources under any licence you want.
But again, I am no lawyer.

Yt,

Gunnar

]]> By: joeri http://www.blendernation.com/python-for-blender-wiki-site-blenderpythonorg/comment-page-1/#comment-9305 joeri Wed, 30 Aug 2006 08:55:27 +0000 http://www.blendernation.com/2006/08/29/python-for-blender-wiki-site-blenderpythonorg/#comment-9305 What about the issue that the FSF is claiming all python scripting is GPL because it uses code that is GPL? I'm asking this questing because of the example image; if it's true that Def Background { groundcolor 0.1 0.0 0.2 } is no longer mine but opensource then that makes creating scripts alot less powerfull than pulling sliders in blender and saving it as .blend . Ofcourse the wiki about how to use python is really great! What about the issue that the FSF is claiming all python scripting is GPL because it uses code that is GPL?

I'm asking this questing because of the example image;
if it's true that

Def Background {
groundcolor 0.1 0.0 0.2
}

is no longer mine but opensource then that makes creating scripts alot less powerfull than pulling sliders in blender and saving it as .blend .

Ofcourse the wiki about how to use python is really great!

]]> By: soxofaan http://www.blendernation.com/python-for-blender-wiki-site-blenderpythonorg/comment-page-1/#comment-9304 soxofaan Wed, 30 Aug 2006 08:55:08 +0000 http://www.blendernation.com/2006/08/29/python-for-blender-wiki-site-blenderpythonorg/#comment-9304 umm, that accompanying image with the post (http://www.blendernation.com/wp-content/uploads/2006/08/python.png) does not look like python. At all. Curly brackets, for example, are considered evil in the pythonic way of life ;) It looks more like a scene declaration in POVRay to me. umm,
that accompanying image with the post (http://www.blendernation.com/wp-content/uploads/2006/08/python.png) does not look like python. At all. Curly brackets, for example, are considered evil in the pythonic way of life ;)
It looks more like a scene declaration in POVRay to me.

]]>