GPL v3 - Do I need to show passwords and secure keys in source
<p>I'm developing in Python using Qt5 (PyQt5), which uses GPL v3 (<a href="http://www.gnu.org/licenses/gpl-3.0.txt" rel="noreferrer">http://www.gnu.org/licenses/gpl-3.0.txt</a>).</p>

<p>I understand I need to make the source available, but if I create a separate file <code>secret.py</code> which contains only one line - the secret <code>API key</code> I use to communicate with my server (it's like a password), and that file or the API has nothing to do with the PyQt, Qt - do I need to show it in source?</p>

<p>Can I compile the software to executable file and attach source without the <code>secret.py</code>, or that is against the license?</p>

<p>This seems to fall under &quot;Installation Information&quot; according to the GPL v3 license. &quot;Installation information&quot; doesn't need to be provided as source code, but it must be provided in such a way that others can take the source code, modify it, and make it work with the &quot;Installation Information&quot; that is provided.</p>
<p>(Technical: At the place where the passwords and secure keys are entered in the source code, I would modify the code so that it doesn't build, followed by instructions how to create your own passwords and secure keys. So you try to build the program, it fails, it points you to instructions, you follow the instructions and change the source files, you try to build again, and it works).</p>

software gpl