https://dev.arvados.org/https://dev.arvados.org/favicon.ico?15576888422015-01-19T15:01:29ZArvadosArvados - Bug #4988: [SDKs] Fix incompatibility between Python packages and newer virtualenvhttps://dev.arvados.org/issues/4988?journal_id=201282015-01-19T15:01:29ZBrett Smithbrett.smith@curii.com
<ul></ul><p>I note that we try to tag our build version as <code>0.1.<git timestamp>+<git hash></code>, but the <code>+</code> is being transformed into <code>-</code> along the way. See <a href="https://pypi.python.org/pypi/arvados-python-client" class="external">our Python package page</a>. This transformation shows up in the <code>.egg-info</code> files if you run <code>python setup.py egg_info</code>, so it's apparently happening early in the process.</p>
<p>Maybe the wheezy build tools are too old to be PEP 440-aware?</p> Arvados - Bug #4988: [SDKs] Fix incompatibility between Python packages and newer virtualenvhttps://dev.arvados.org/issues/4988?journal_id=203202015-01-21T21:00:58ZTom Cleggtom@curii.com
<ul><li><strong>Target version</strong> changed from <i>Bug Triage</i> to <i>2015-02-18 sprint</i></li></ul> Arvados - Bug #4988: [SDKs] Fix incompatibility between Python packages and newer virtualenvhttps://dev.arvados.org/issues/4988?journal_id=207152015-01-29T19:48:18ZBrett Smithbrett.smith@curii.com
<ul><li><strong>Assigned To</strong> set to <i>Brett Smith</i></li></ul> Arvados - Bug #4988: [SDKs] Fix incompatibility between Python packages and newer virtualenvhttps://dev.arvados.org/issues/4988?journal_id=210582015-02-11T15:18:02ZBrett Smithbrett.smith@curii.com
<ul></ul><p>I think the real bug here was <a class="issue tracker-1 status-3 priority-4 priority-default closed parent" title="Bug: [SDKs] Fix Python package versions so they can be uploaded to pypi (Resolved)" href="https://dev.arvados.org/issues/5175">#5175</a>: we were generating version numbers that were not PEP 440-compliant, and would not be accepted by PyPI or other tools.</p>
<p>We build our own virtualenv deb, and we're using that on the ci server. (Whether or not that's intentional is a little difficult to say right now.) It is the very latest version, even newer than what's currently in jessie (12.0.7 compared to 1.11.6). Package builds are working fine and making their way to PyPI right now.</p>
<p>I think we can close this as a duplicate.</p> Arvados - Bug #4988: [SDKs] Fix incompatibility between Python packages and newer virtualenvhttps://dev.arvados.org/issues/4988?journal_id=211062015-02-12T15:17:21ZBrett Smithbrett.smith@curii.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li></ul>