Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It's strange that there isn't built-in support for setting a default, but here are two options which may help you work around it.</p> <p><strong>Option 1:</strong> Probably the simplest solution would be to leave your <strong>~/.pypirc</strong> script intact and create shell aliases for your internal and public uploads. This may give you more control over customizing things for your workflow.</p> <p>Given this <strong>.pypirc</strong> file: </p> <pre><code>[distutils] index-servers = pypi internal [pypi] repository: http://pypi.python.org/pypi username: brad password: &lt;pass&gt; [internal] repository: http://localhost:8080 username: brad password: &lt;pass&gt; </code></pre> <p>Create some shell aliases (place these definitions in your shell's rcfile, e.g. <strong>~/.bashrc</strong>):</p> <pre><code>alias ppup_internal='python setup.py bdist_egg sdist upload -r internal' alias ppup_public='python setup.py bdist_egg sdist upload' </code></pre> <p>Usage:</p> <pre><code>% ppup_internal ... running upload Submitting dist/foo-0.0.0.tar.gz to http://localhost:8080 Server response (200): OK </code></pre> <hr> <p><strong>Option 2:</strong> A hack: you can work around the default by patching the default repository name at the top of your setup.py scripts. </p> <pre><code>from distutils import config config.PyPIRCCommand.DEFAULT_REPOSITORY = 'internal' from setuptools import setup setup( name='foo', ... </code></pre> <p>Output:</p> <pre><code>% python setup.py sdist upload ... running upload Submitting dist/foo-0.0.0.tar.gz to http://localhost:8080 Server response (200): OK % python setup.py sdist upload -r pypi ... running upload Submitting dist/foo-0.0.0.tar.gz to http://pypi.python.org/pypi Server response (200): OK </code></pre> <hr> <p><strong>Background:</strong> If you define the <strong>[distutils]</strong> key in <strong>.pypirc</strong>, the upload command defaults to the <strong>pypi url</strong> when the <strong>-r [repo]</strong> argument is omitted. The relevant code is in <strong>distutils.config.PyPIRCCommand</strong>:</p> <pre><code>class PyPIRCCommand(Command): DEFAULT_REPOSITORY = 'http://pypi.python.org/pypi' def _read_pypirc(self): if os.path.exists(rc): self.announce('Using PyPI login from %s' % rc) repository = self.repository or self.DEFAULT_REPOSITORY realm = self.realm or self.DEFAULT_REALM </code></pre> <p>The old format of <strong>.pypirc</strong> expected a <strong>[server-login]</strong> section, which was far less flexible since it only defines a single target repository. This isn't a workable option since the <strong>[pypi]</strong> section below will be unusable:</p> <pre><code>[server-login] repository: http://localhost:8080 username: brad password: &lt;pass&gt; [pypi] repository: http://pypi.python.org/pypi username: brad password: &lt;pass&gt; </code></pre> <p>Now by default distutils will use this target:</p> <pre><code>% python setup.py sdist upload ... running upload Submitting dist/foo-0.0.0.tar.gz to http://localhost:8080 Server response (200): OK </code></pre> <p>But you can't access the any other repos: it silently defaults to the <strong>[server-login]</strong> properties:</p> <pre><code>% python setup.py sdist upload -r pypi ... running upload Submitting dist/foo-0.0.0.tar.gz to http://localhost:8080 Server response (200): OK </code></pre>
    singulars
    1. This table or related slice is empty.
    1. PODefault server in multiple server configuration of distutils in ~/.pypirc
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USsamplebias
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODefault server in multiple server configuration of distutils in ~/.pypirc
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTBountyClose
    1. COThanks for going the extra mile on this one. It's very disappointing that it's not supported. `config.PyPIRCCommand.DEFAULT_REPOSITORY = 'internal'` is a bit confusing, does it refer to a section in `.pypirc`, or is it a URL to the server?
      singulars
      1. PO
      1. USbradley.ayers
    2. COYep, I thought it best to lay out all options I could find. The string `internal` is the name of the section in the .pypirc which you want to be your default. So in your .pypirc you named your local repository `[internal]` so that line in setup.py will monkey-patch the default to be `internal`.
      singulars
      1. PO
      1. USsamplebias
    3. COoops, I didn't realise I had to award the bounty separately, there you go.
      singulars
      1. PO
      1. USbradley.ayers
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload