Fredrik Lundh wrote:
> Mathias Panzenboeck wrote:
>
>> But the question is: *IS* this derived work? I mean, it's not copied code.
>> It's the same hashing-logic, which I learned by watching pythons code.
>
> given that it's only a few lines of code, and there's hardly any other
> way to write th
Fredrik Lundh wrote:
> Mathias Panzenboeck wrote:
>
>> But the question is: *IS* this derived work? I mean, it's not copied
>> code.
>> It's the same hashing-logic, which I learned by watching pythons code.
>
> given that it's only a few lines of code, and there's hardly any other
> way to writ
Mathias Panzenboeck wrote:
> But the question is: *IS* this derived work? I mean, it's not copied code.
> It's the same hashing-logic, which I learned by watching pythons code.
given that it's only a few lines of code, and there's hardly any other
way to write those lines if you want to implemen
Paul Rubin wrote:
> Mathias Panzenboeck <[EMAIL PROTECTED]> writes:
>> So, can this code be considered as derived and do I have to put my
>> code under the GPL? I'd like to publish it under something less
>> restrictive, like a BSD style license. But if GPL is the only way,
>> then GPL it is. :)
>
Mathias Panzenboeck <[EMAIL PROTECTED]> writes:
> So, can this code be considered as derived and do I have to put my
> code under the GPL? I'd like to publish it under something less
> restrictive, like a BSD style license. But if GPL is the only way,
> then GPL it is. :)
Python is not GPL'd but h
Hi.
I wrote a small hashlib for C. Because I'm new to hashes I looked at pythons
implementation and
reused *some* of the code... or more the mathematical "hash-function", not
really the code.
In particular I looked at pythons hash and lookup functions, so I came up with
this (see the code
un
