| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Based on the rubygems one.
|
|\
| |
| |
| |
| | |
Reviewed-By: Javier Jardón <javier.jardon@codethink.co.uk>
Reviewed-By: Sam Thursfield <sam.thursfield@codethink.co.uk>
|
| | |
|
| |
| |
| |
| |
| |
| | |
Most svn repos use a standard layout, we assume svn repos we want to lorry
are using a standard layout, so make str_repo_lorry add 'layout': 'standard'
for svn repos
|
| |
| |
| |
| |
| |
| | |
This fixes the tool so that it can find refs such as foobar-1.4.0 when
the version has been passed as 1.4 and refs such as foobar-1.4 when the version
has been passed 1.4.0
|
|\ \
| |/
|/|
| |
| | |
Reviewed by:
Sam Thursfield <sam.thursfield@codethink.co.uk>
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
We also call package_releases with True, so that we also get versions
of releases that have been hidden. pip is willing to install from hidden
releases so we should too, the concept of hidden releases will eventually
disappear from pypi as well.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
It's sometime useful to see the output of the vcs, but having this enabled
all the time clutters the log
|
| |
| |
| |
| | |
The two extensions have diverged so this generic class is no longer useful.
|
| | |
|
| |
| |
| |
| | |
This is redundant.
|
| |
| |
| |
| |
| |
| |
| | |
As well as being case insensitive project names on python treat '-' and '_'
as equivalent characters [1]
[1]: http://legacy.python.org/dev/peps/pep-0426/#name
|
| |
| |
| |
| |
| |
| | |
This lets the importer specify how package names will be compared,
to do this the importer optionally supplies a callback, if no callback
is supplied then the tool will default to == for string comparison.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This adds PythonLorryExtension class to python.to_lorry to run the extension
in a more conventional way. Previously the PythonExtension class
was used to execute any of the extensions (it would call the extensions main()
function). We move away from this so the
extension can access useful methods, such as local_data_path(), that are
provided by the ImportExtension class.
This also removes use of pkg_resources.parse_requirement which is redundant.
This also removes the unused import of select.
|
|/
|
|
| |
This adds a config file for the python extensions
|
|\
| |
| |
| |
| | |
Reviewed-By: Jim MacArthur <jim.macarthur@codethink.co.uk>
Reviewed-By: Sam Thursfield <sam.thursfield@codethink.co.uk>
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| |/
| |
| |
| | |
Reviewed-By: Richard Ipsum <richard.ipsum@codethink.co.uk>
Reviewed-By: Sam Thursfield <sam.thursfield@codethink.co.uk>
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There isn't yet an official spec for distribution names in python,
however there is a draft at http://legacy.python.org/dev/peps/pep-0426/#name
In particular,
"All comparisons of distribution names MUST be case insensitive,
and MUST consider hyphens and underscores to be equivalent."
pkg_resource.parse_requirements will replace any underscores in the
package name as hyphens, so when we search pypi we need to look for
the package name with underscores as well as with hyphens.
|
|\
| |
| |
| |
| | |
There is work still to be done on this importer, but it is usable for
some Python projects and may as well be merged to 'master' now.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Morph doesn't need a chunk morph to build/install setuptools packages,
but the import tool needs to grow the ability to have 'to_chunk' as an
optional stage before we can remove this part of the python extension.
|
| |
| |
| |
| |
| | |
python.find_deps does some pretty basic validation of the requirement specs,
this commit adds the tests for this validation.
|
| |
| |
| |
| |
| | |
This takes source_dir, name, version and returns the dependencies for the
package as json on stdout.
|
| | |
|
| |
| |
| |
| | |
This takes source, name, version and produces a lorry
|
| | |
|
| |
| |
| |
| |
| |
| | |
This is helpful for discovering when messages are being put on stderr,
we're collecting messages on stderr, but these could come from different
subprocesses leading to a confusing mixture of error messages.
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
|
| |
Content overlaps with that of the README a bit, I'm not sure what to do
about this. Putting 'man' pages online as part of our continuous
delivery infrastructure should ultimately be the goal.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
The multi_json Gem wasn't being detected as signed, because the
'signing_key' field is an expression that can evaluate to 'nil' in some
cases. In this Gem the 'cert_chain' field was still a standard string.
Hopefully checking for the presence of either will catch all cases
(and false positives should be harmless anyway).
|