title: setup.py -- configuration for private / commercial projects
body: <p>What can I put on our <code>setup.py</code> project configuration file to tell the developers that the project is a private/commercial application/library.</p>
  
  <p>Currently I set:</p>
  
  <pre><code>setup(
      name='MyProject',
      version='0.1.0',
      license='(c) My Company',
      ...
  )
  </code></pre>
  
  <p>Any best practice?</p>
  
  <p><strong>Note:</strong></p>
  
  <p>Nowadays, most of the projects are open source, and adhere to the licences model. However, when you work on the industry, software are private. My company works with off-shore companies which may not be aware of the fact that a software can be private. So, I want to bring this fact to their attention by specifying this in the <code>setup.py</code> file. This is why I'm looking for best practices about that.</p>
  
  <p><strong>Conclusion/Solution</strong></p>
  
  <p>For private/proprietary applications, I will follow <a href="https://stackoverflow.com/a/44098491/1513933">rth's recommendation</a>:</p>
  
  <ul>
  <li>set the license attribute to “Proprietary”,</li>
  <li>add the classifier “License :: Other/Proprietary License”,</li>
  <li>and maybe add a <code>LICENSE</code> file.</li>
  </ul>
  
  <p>The template will be something like that:</p>
  
  <pre><code>setup(
      name='MyProject',
      version='0.1.0',
      license="Proprietary",
      classifiers=[
          'License :: Other/Proprietary License',
          ...
      ],
      ...
  )
  </code></pre>
  
  <p>An alternative could be to set “Not open source”, like defined in the <a href="https://github.com/audreyr/cookiecutter-pypackage/blob/master/cookiecutter.json" rel="noreferrer">cookiecutter-pypackage</a> template.</p>