-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Kao Cardoso Felix wrote: > On Dec 10, 2007 11:24 PM, Lunpa, The <[EMAIL PROTECTED]> wrote: > >> I'm still puzzling on how you'd do a closed source software project in >> python anyway :). >> >> (other than by keeping it in-house) >> > > Distributing only the bytecode (.pyc or .pyo) > > (: >
That probably wouldn't work too well because that is dependent on the specific Python version you are running. However, there are tools that compile a self-contained .exe file out of the Python code, including the Python runtime. Furthermore, e.g. Soya consists of a lot of code that is in binary extensions compiled from Pyrex, not pure Python. You could withhold source to something like that. Another option used a lot are various code obfuscators. So there are ways how not to give out source to your Python applications if you really want. Regarding the license change, somebody mentioned that GPL3 should be used because it takes an active stand against patents. Well, again, I am not going to advocate anything here as my opinion is not really relevant - - I have very little code in Soya to be considered a copyright holder. However, adopting GPL3 on these grounds is more making a political statement (with a little practical impact, IMHO) than licensing or engineering issue. Code can be a mean of political expression, there is nothing wrong with that, but it also "boxes you in" in a certain position and it will restrict the potential user base. Is that what you want? Jan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org iD8DBQFHXqOTn11XseNj94gRAncWAJ9SGMqWStAieAvXy0PTtPe37o8iYACfYlmw mRu7uDcRWRbiFTiccr5SHQU= =QLL0 -----END PGP SIGNATURE----- _______________________________________________ Soya-user mailing list Soya-user@gna.org https://mail.gna.org/listinfo/soya-user
