npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

@sjcrh/proteinpaint-python

v2.164.1

Published

Python-based utilities for proteinpaint

Readme

Installation

Docker

This is already included in the deps image and other images that use it as a base image.

Mac

  1. To run python/src/dzi.py on mac, you need to install the following packages:
brew install python
  1. Homebrew's python formula now points to Python 3 by default. Verify that python3 is installed by running:
python3 --version
  1. Install vips for managing large images:
brew install vips
  1. Now in order to install pyvips check if you have a python virtual env by running python3 -V, if not you can create one by running
python3 -m venv ~/pppython
source ~/pppython/bin/activate

# check the installed path
which python3
# Gives the absolute path to the python installattion in the virtual environment
  1. Now you should by able to install all the relevant python modules by installing all modules in the requirement.txt file
pip3 install -r requirements.txt

#To test it you can run
python3 src/dzi.py /path/to/file.svs /path/to/images
  1. In order for the nodejs server code to use python virtual environment that has been set up, you can do one of the following:
  • a. set a serverconfig.python option that equals the absolute path to your .venv/bin/python3 installation
  • b. call source path/to/.venv/bin/activate in the same shell or terminal tab/window before running a package script like npm run dev , npm run test:integration, etc.
  1. Once Python development and testing are finished, execute the following command from the proteinpaint/python directory to deactivate the currently active virtual environment:
source .venv/bin/deactivate

This is important to keep the GitHub hook working.