Op 2005-04-14, Robert Kern schreef <[EMAIL PROTECTED]>: > Antoon Pardon wrote: >> Op 2005-04-13, Robert Kern schreef <[EMAIL PROTECTED]>: >> >> I would do that if I were just writing code I thought others could >> find usefull. I then would feel no problem "burdening" those users >> with the same kind of license I found in the product I took some >> code from. But I also think that readers of documentation should >> be free to use any code included in any way they see fit. > > If they have issues with distributing code derived from Python, why are > they reading a Python tutorial?
Try and look it from a students viewpoint. He is learing languages, algorithms and so on. Now he is ready to write his own program. Chances are high that he will rely on examples from the courses/documentation he read. It is just not practical for someone like that to figure out all the possible different licenses under which he can use the examples from the various documenation sources. Now if this documentation refers to code from yet another source with its own license, using it becomes an utter nightmare for the student, because now he has to figure out which piece of the code is original from the author of the documentation and which was copied from the other source. Consideration like this, let me come to the conclusion that code included with documentation should come with no strings attached for the students to reuse. -- Antoon Pardon -- http://mail.python.org/mailman/listinfo/python-list