Dave wrote:
> With the open source licenses that allow redistribution of modified
> code, how do you keep someone unaffiliated with the Python community
> from creating his or her own version of python, and declaring it to be
> Python 2.6, or maybe Python 2.7 without any approval of anyone at the
>
Matimus wrote:
> Others have made some pretty
> sound arguments around trademarks and such, but I'm going to simply
> argue that Python as a community has its own inertia, and it simply
> isn't a practical to be concerned about a dubious fork. It simply
> wouldn't take off.
I think this is indeed
On Oct 8, 8:43 am, Dave <[EMAIL PROTECTED]> wrote:
> With the open source licenses that allow redistribution of modified
> code, how do you keep someone unaffiliated with the Python community
> from creating his or her own version of python, and declaring it to be
> Python 2.6, or maybe Python 2.7
I think it's pretty self-evident that it's not a huge problem, don't
you? Do you see lots of low quality python forks cluttering up the
internet?
hardly any...the best python fork I found:
http://www.woopit.com/albums/Australian-snakes/GreenPythonSnake.jpg
though they look more like tweezers t
Dave wrote:
With the open source licenses that allow redistribution of modified
code, how do you keep someone unaffiliated with the Python community
from creating his or her own version of python, and declaring it to be
Python 2.6, or maybe Python 2.7 without any approval of anyone at the
PSF? Ma
On Oct 8, 8:43 am, Dave <[EMAIL PROTECTED]> wrote:
> With the open source licenses that allow redistribution of modified
> code, how do you keep someone unaffiliated with the Python community
> from creating his or her own version of python, and declaring it to be
> Python 2.6, or maybe Python 2.7
Dave wrote:
If licensees can
redisribute as they like, isn't this a huge problem? Is this dealt
with be restricting use of the Python trademarks? Just curious..
From http://www.python.org/psf/summary/
---
The PSF also holds and protects the trademarks behind the Python
programming language. T
Dave wrote:
> With the open source licenses that allow redistribution of modified
> code, how do you keep someone unaffiliated with the Python community
> from creating his or her own version of python, and declaring it to be
> Python 2.6, or maybe Python 2.7 without any approval of anyone at the
On Wed, Oct 8, 2008 at 10:43 AM, Dave <[EMAIL PROTECTED]> wrote:
> With the open source licenses that allow redistribution of modified
> code, how do you keep someone unaffiliated with the Python community
> from creating his or her own version of python, and declaring it to be
> Python 2.6, or may
