pypm2 0.2.1

Python package manager for projects running Python3.6 and above.

PyPM

Pypm is a python package manager for projects using Python 3 and above. This library is similar to npm. This command line tool works just like npm and should mirror its features.

Reason

The python community has no package management tool that is closely maintained. Also, outside of requirements.txt there is no adopted approach to storing and maintaining dependencies. In an effort to change this, I've introduced the PyPM tool. It uses the same package.json structure as npm, with all the configurations setup.py offers.

UPDATED:
Its been brought to my attention (by a redditor; shock), that the above statement was in fact a lie. So, let me be clear. This project was written over 2 years ago, in 2 hours, when I was creating my PyReact library (you can find the repo on my page). It was an effort to package up the framework to mimic ReactJS, and consequently, npm. Myself nor any of my other close Python devs had heard of Flint or Poetry, so I made my own dependency manager. I was today years old (10 August 2022) when it was brought to my attention. So, for rightfully argumentative community, I've decided to make this disclaimer that PyPM is not a game-changer and is just yet another option of Python package managers.

Another note, it currently uses setup.cfg as the configuration file. This will be changed to adopt the .toml configuration file approach.

This project intends to introduce another project management tool to the Python community.

Install

requires Python 3.6 or above

PyPI

pip install pypm2

Locally

git clone https://github.com/ableinc/pypm
cd pypm
pip install --editable .

Visit PyPi: PyPi for Pyenv

How to Use

PyPM works just like npm. You are granted the same operations such as, init, install, uninstall, update, start, and run. Run:

pypm --help

Usage

1. init
   Generate a brand new package.json file from information in your requirements.txt and setup.py.

   pypm init
   

2. run
   Run a predefined scripts from the 'scripts' section of your package.json.

   pypm run tests
   

3. start
   Run the start script.

   pypm start
   

4. install ¹
   Install all or specific packages. Using 'install' as a standalone, it will install all dependencies listed in your package.json (if exists).

   pypm install
   

   or

   pypm install package1 package2
   

5. uninstall ¹
   Uninstall all or specific packages. Using 'uninstall' as a standalone, it will uninstall all dependencies listed in your package.json (if exists).

   pypm uninstall
   

   or

   pypm uninstall package1 package2
   

6. update ¹
   Update all or specific packages. Using 'update' as a standalone, it will update all dependencies listed in your package.json (if exists).

   pypm update
   

   or

   pypm update package1 package2
   

7. setup
   Instead of manually creating setup.py and setup.cfg files, you can add the same arguments under the 'setup' key in the package.json (refer to package.json), then run pypm setup to install your project locally.

   pypm setup
   

   Update setuptools, wheel, pip:

   pypm setup True
   

   Specify a version of python to use:

   pypm setup --python python3.9
   

8. getreqs
   Generate the requirments.txt file based on your (virtual) environment.

   pypm getreqs
   

Key

¹ Any arguments that pip or npm allow can be combined into these command line arguments. Initiated by adding --arguments option. Example:

pypm --arguments --no-cache install pydotenvs

The above example will install the library pydotenvs via PyPI using Pip's built in --no-cache feature.

If you have multiple arguments to append to a command you can seperate them by commas. For example:

pypm --arguments --no-cache,--verbose,--logs,~/Downloads install pydotenvs

Notes

1. Documentation is on-going, so refer to examples above for now.

2. Unfortunately someone beat me to the name pypm. Note that when you use pip install be sure to include the 2. This would normally be an issue if you imported this package, but it's a command line tool

3. When installing using npm, the package.json will not update dependencies. This is a known bug. Until fixed, use npm/npx to do your installing for node projects. All other features work.

4. When generating the setup.py & setup.cfg files for development mode installation pip, setuptools and wheel may need to be updated. Follow the instructions above to update alongside setup functionality.

Changelog

January 2023

• Fixed bug with stdlib_list library - it is limited to python version <= 3.9. Future updates to the library will remove this dependency.
• Updated micro version number. New version 0.2.1

August 2022

• Updated how the package is installed on the system
• New algorithm for automatically generating the requirements.txt file has been added
• pypm init can now generate the requirements.txt file by pypm command (pypm getreqs)
• You can now specify a version of python to use for pypm setup. By default it will use python3.

June 2021

• Enhanced the arguments feature for CLI tool.

April 2021

• Minor bug fix to CLI tool; version update.

September 2020

• Verbose is no longer default
• Setup.py functionality added to package.json
• Custom error messages
• CLI updates Setup.py feature has been introduced in version 0.1.3

August 2020

• CLI has been rebuilt; less complex.
• PyPI easy install; pip install pypm2

Up Next

1. No cache options when installing. - Done | You may add any arguments that are allowed for pip, npm or any other CLI tool arguments
2. Better automation algorithm when generating a new package.json - Done
3. Possible PyPI easy install - Done
4. Add package-lock.json - currently in development
5. Replace setup.py & setup.cfg, move functionality to package.json - Done
6. PyPI upload built in Done