I'm trying to install devpi-server on Amazon Linux 2015.09 but when I start
it, I'm receiving the following error:
$ cat /etc/system-release
Amazon Linux AMI release 2015.09
$ devpi-server --version
3.0.2
$ devpi-server --start
2016-03-22 21:53:12,909 INFO NOCTX Loading node info from
/opt/devpi/.devpi/server/.nodeinfo
2016-03-22 21:53:12,910 INFO NOCTX generated uuid:
89e20f8f78fc4f2f8d8b96e121115993
fatal: The backend 'sqlite' can't be found, is the plugin not installed?
I am able to import sqlite3 from Python.
$ python
Python 2.7.10 (default, Dec 8 2015, 18:25:23)
[GCC 4.8.3 20140911 (Red Hat 4.8.3-9)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sqlite3
>>>
What am I missing?
Hi!
I just released devpi-client 2.6.0, devpi-server 3.1.0 and devpi-web
3.1.0.
For devpi-client authentication infos are retained when switching
servers with ``devpi use``, no need to login each time anymore.
See https://pypi.python.org/pypi/devpi-client for the full changelog.
For devpi-server uncached releases are streamed while downloading from
PyPI (or any other mirror) to clients like pip. This prevents timeouts
on first installation of bigger packages.
Additionally there are some import/export improvements.
See https://pypi.python.org/pypi/devpi-server for the full changelog.
Like PyPI, devpi-web now uses ``readme-renderer`` to convert the long
description of packages to HTML. If there are any errors doing that, the
error messages are appended to the description now.
There were some project name normalization issues that are now fixed.
Those caused some documentation to not be linked and search results
involving those projects caused server errors resulting in a plain error
message.
See https://pypi.python.org/pypi/devpi-web for the full changelog.
If you need support, training, adjustments wrt packaging and
professional testing you may contact us through http://merlinux.eu.
Regards,
Florian Schulze
Hi,
I'm playing around with devpi themes.
My goal is to create a nice theme for my company.
I'd like to add extra information to some pages, like the index page or the
main page.
I added a snippet of code which produces an "index inheritance diagram" on
each index page display.
Because the company I work for is not that small, these diagrams can get
strange.
A sample diagram: index inheritance diagram
<https://lh3.googleusercontent.com/--9yr5WSohOc/VZ0BL6xN3YI/AAAAAAAAAAs/8wZq…>.
Each box is an index, I intentionally removed all user and index names,
except for root/pypi.
It's not my indices, please don't judge me for the design :)
I'm concerned about performance here. First of all, currently I generate
those on display action, which doesn't seem the way to go.
Could devpi provide a hook so that I'm able to regenerate a diagram on an
index update event?
Additionally, I'd like to add more information to an index page and the
root pages. So the question is: Could functions in devpi_web.views expose
more data in get_index() and root()? Potentially other functions?
I know I can always get the data with python snippets in the templates, but
it all takes precious time.
For instance, in my company, some indices are regular user indices, some of
them are project indices.
I'd like to sort the list of indices on the root page: display the project
ones first, and user indices below.
The way I would see this is the custom_data property of an index.
The bottom line: I think people could easily create fancier themes if the
devpi web views functions exposed more data to the templates, even if that
data is not used in the default theme.
It would be great to get the full indexconfig json structure for each index
in both get_index() and root() functions from devpi_web.views module.
Now I'm not sure how much more data others might want to get there.
I hope these things make sense.
Any thoughts?
