HELP needed: Tricks for licensing Python software

[Pekka Niiranen]

Thanks for all who bothered to answer.
I shall consider clisp instead (cmucl).

Some notes:

- Autocad has allways used lockpiece here in Europe.
   Recently (Acad 2002) they too have started using license tied
   to MAC -address.

- Open Source: the smaller the idea, the bigger the protection ;).
   I have invented a perfect in-house tool but the dataformat we
   are using is open, widely used and not ours. I can only protect
   my idea by protecting the source :(.

-pekka-


Martin Maney wrote:
> Max Khesin <max at cnovsisiponatecmh.com> wrote:
> 
>>I appreciate the sentiment, but it is meaningless without numbers. It is
> 
> 
> It annoys or offends your honest customers; if they don't outnumber
> your dishonest ones then you are probably doomed anyway, because
> there's really no such thing as copy protection for software, only copy
> discouragement.
> 
> 
>>true that copy-protection offends some honest people, but the numbers I
>>heard seem to indicate (unless you have data to prove the opposite) that
>>copy protection is economically advantageous in many instances. Honest
> 
> 
> I notice you don't say "all instances", so I don't really need to show
> you that it isn't always a win, do I?  :-)
> 
> 
>>people will just have to get over it :).
> 
> 
> The risk is, of course, that too many honest would-be customers will
> "get over it", though not in the way you hope.  But it's your call. 
> Hope you don't regret it, whichever way you decide to go.