Re: [Tutor] Lengthy copyright notices?
On 16/07/19 12:47 PM, Alan Gauld via Tutor wrote:
On 15/07/2019 23:34, Mats Wichmann wrote:
Rule #1: it's all opinion in the end...
Not quite. Different jurisdictions (remember, this list has an
international membership!) have different understandings of (even,
respect for) copyrights and permissions.
I live in a jurisdiction where whatever I write ("create") is mine - or
my employer's. It is not even necessary to claim or "exert" copyright!
However, under the 'different strokes...' rule, I still include a
copyright/license statement - if only to avoid misunderstandings in
places that have other requirements and to at least 'make an effort' to
communicate with those who have no such concepts - either in society, or
(un)enshrined in law.
The common practice is that licence/copyright text is included as a
comment in the code, not in a docstring.
I'd second that opinion. I don't like losing the copyright stuff
to a separate file - too easy to get lost. But I certainly don't
want it in my help() output either.
A comment solves both for the downside of some initial scrolling
when reading or editing the file
Some disagreement here.
(but nothing worth fighting-over!)
One line offers plenty of space to exert a claim (such can be very
simple and does not need to be lawyer-speak!) which should also refer to
the template's/package's external file or web-page. The latter giving as
much space for whatever you (or your legal representative(s) ) might
want to say!
There can be quite an accumulation of 'paper-work' at the top of
modules, which then has to be scrolled-through before we can get
stuck-in to function/class/__main__ code - even with an editor's
code-folding assistance.
Should it be left to the (far) end of the file? Would it lessen any
legal implication?
Aside from possibly irritating 'the good guys', does such really 'stop'
a determined rapscallion?
(...desperate student, lazy 'professional', corporate 'raider'...?)
--
Regards =dn
___
Tutor maillist - Tutor@python.org
To unsubscribe or change subscription options:
https://mail.python.org/mailman/listinfo/tutor
Re: [Tutor] Lengthy copyright notices?
On 17/07/2019 21:01, David L Neil wrote: > One line offers plenty of space to exert a claim (such can be very > simple and does not need to be lawyer-speak!) which should also refer to > the template's/package's external file or web-page. Yes, I've seen that and if the lawyer speak is very verbose its a good compromise. > Aside from possibly irritating 'the good guys', does such really 'stop' > a determined rapscallion? Nothing will stop a determined rapscallion(love that phrase! ;-) But it lets the good guys know who to contact at least if they do need to. For example, in my last book the publishers required me to get a disclaimer from the author of some open source files even though they clearly stated they could be used for any purpose. Having the copyright notice with email link made that easy. -- Alan G Author of the Learn to Program web site http://www.alan-g.me.uk/ http://www.amazon.com/author/alan_gauld Follow my photo-blog on Flickr at: http://www.flickr.com/photos/alangauldphotos ___ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: https://mail.python.org/mailman/listinfo/tutor
[Tutor] Calling a C shared library with PyObject
I am using Python3.6 Working with C/Python embedding: https://docs.python.org/3.6/extending/embedding.html#beyond-very-high-level-embedding-an-overview I have to call a shared library (.so) that I created using PyObjects. Please advise. Jesse Ibarra ___ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: https://mail.python.org/mailman/listinfo/tutor
Re: [Tutor] Lengthy copyright notices?
On 18/07/19 10:08 AM, Alan Gauld via Tutor wrote: On 17/07/2019 21:01, David L Neil wrote: One line offers plenty of space to exert a claim (such can be very simple and does not need to be lawyer-speak!) which should also refer to the template's/package's external file or web-page. Yes, I've seen that and if the lawyer speak is very verbose its a good compromise. Aside from possibly irritating 'the good guys', does such really 'stop' a determined rapscallion? Nothing will stop a determined rapscallion(love that phrase! ;-) But it lets the good guys know who to contact at least if they do need to. For example, in my last book the publishers required me to get a disclaimer from the author of some open source files even though they clearly stated they could be used for any purpose. Having the copyright notice with email link made that easy. Open source: I've had the same - even for short "shazzam" or "drum-roll-please" sound-clips (which advertisers use all the time - who can name the pieces of music without saying "The lady loves Milk Tray" or "British Airways"?). That said, internationally there are many definitions and variations of "fair use" - and some jurisdictions don't even recognise such a thing! (I think the British law is quite 'tight'). I refused such a request?instruction, suggesting that the publishers AND their lawyers should enter 'the real world' and learn to understand (?and embrace) "open" concepts. In response to the inevitable grumpy push-back, I pointed-out that I am an author/content-producer and not legally-trained (not quite true, but they don't know that) so why on earth would they take MY advice... Another one is 'images', which as a keen (amateur) photographer I readily understand from both 'sides' - which simply meant that in a fit of pique at the aforementioned KYA-bureaucrats, I made a point of copyrighting EVERY training diagram/illustration/code-snippet that I produced and then REQUIRED 'the blighters' to license them from me... (yet insisted that such be 'free' for trainees to download for their own use) Hah! Closed source: I was once contacted by someone who had hold of a small system I'd written way back in the mists-of-time. How, they ever obtained it, I can't imagine. The 'license' clearly said "no license", but he wanted to negotiate - which was great (although sadly, the client still "owned" the software, so no 'winning the lottery' for me then!) -- Regards =dn ___ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: https://mail.python.org/mailman/listinfo/tutor
Re: [Tutor] Calling a C shared library with PyObject
On 17/07/2019 18:03, Jesse Ibarra wrote: > I am using Python3.6 > > Working with C/Python embedding: > https://docs.python.org/3.6/extending/embedding.html#beyond-very-high-level-embedding-an-overview > > I have to call a shared library (.so) that I created using PyObjects. To be honest embedding is quite an advanced topic and the tutor list is generally targeted at beginners so you might find limited help here. (Although technically it does fall within our remit, it's just that it doesn't come up too often!) I'd suggest you post your queries on the main python list where there will likely be far more experts available. -- Alan G Author of the Learn to Program web site http://www.alan-g.me.uk/ http://www.amazon.com/author/alan_gauld Follow my photo-blog on Flickr at: http://www.flickr.com/photos/alangauldphotos ___ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: https://mail.python.org/mailman/listinfo/tutor
