pandaspro

pandas with friendlier dataframe methods and Excel export / formatting helpers.

pip install pandaspro

See CHANGELOG.md for what changed in each version, and df.cpdhelp() for the dataframe shortcuts.

Data assembly: cpdBaseFrame and cpdDatabaseC

The two halves of assembling a project's data:

• cpdBaseFrame — dated system extracts. One folder of files named by date (SOB_20261001.csv); decorate a class and load a version with X(version="latest"). The data is produced elsewhere and only read here.
• cpdDatabaseC — hand-maintained lists. One folder of JSON files named by list (modules/clients.json) plus a browser editor; decorate a store class and one class per list. The data is maintained by people in the published page.

cpdDatabaseC

from mylists import MyLists, Clients

MyLists.publish()          # creates <folder>/mylists.html and modules/*.json (data is never overwritten)
MyLists.open()             # opens the editor in Edge / Chrome; "Open folder" -> pick <folder>

Clients.frame()            # rows as a DataFrame
MyLists.list()             # every module: id, title, group, live, rows, revision, saved_at
MyLists.check()            # one line per module: filled? live? same as its old source?

CountryGroups.import_source()   # rows from the old Excel into the module (not live yet)
CountryGroups.compare()         # empty frame = module and Excel agree
CountryGroups.set_live()        # from now on read_live() returns the module

mylists is the example shipped in pandaspro/cpddatabasec/example/: copy mylists/ into your project, rename the store, keep or replace the three example lists, add your own. Declaring a store and a list:

from pandaspro import cpdDatabaseC, cpdField as field

@cpdDatabaseC(name="MyLists", package="myproject", editor="mylists.html")
class MyLists:
    @classmethod
    def get_path(cls):                       # or path="..." in the decorator
        return os.environ["MYLISTS_DIR"]     # per machine, never a hard-coded path in the repo

@MyLists.module("clients", title="Clients", group="Reference", key=["code"])
class Clients:
    code = field(required=True, help="Short code, unique")
    name = field(required=True)
    tier = field(type="select", options=["A", "B", "C"])

Add a list = add a decorated class. Add a field = add a line (publish() refreshes the definition, rows stay). Change the page = pass editor_source="your.html" (start from a copy of pandaspro/cpddatabasec/editor.html).

Versions and releases

All work happens on master. A version is a tag on master (v1.3.1); there are no version branches. The version number lives in one place, pyproject.toml.

• While you work: add a line under Unreleased in CHANGELOG.md for anything a user can notice.
• To release: python release.py 1.3.2 (add --dry-run to rehearse). It checks the tree, runs the tests, sets the version, dates the changelog section, commits, tags and pushes.
• A machine that produces reports should sit on a tag, not on every push: git fetch --tags then git checkout v1.3.2.
• Version numbers: last digit for fixes and small additions, middle digit for new features, first digit when existing calls stop working.