Skip to content

[FEATURE] Clean install from pip #138

Description

@e-lo

User Story

As a MetCouncil user, I'd like to be able to install lasso cleanly from PIP and Conda

Issue Checklist

  • Issue defined
  • Resolution decided on
  • User story satisfied
  • Tests?
  • Documentation updated

Priority

High

Level of Effort

Low-Medium

Resolution Ideas/Discussion

Naming: Need to have a clean name which wont conflict with anything else on PyPi

  • Suggestions: @RachelWikenMC?
    • msp-lasso ?
    • lasso-msp?
    • lasso-MetCouncil?
    • gopher-lasso?
    • vikings-lasso?
    • loon-lasso?
    • minne-lasso?

Rename package:

  • setup.py
  • pypi
  • repo folders
  • github

Deploying to PyPi and Conda Forge:

  • Add a deploy github action to publish to PyPi upon release tagging (need: which name?)

Project

MetCouncil

Who should be involved?

Users: @RachelWikenMC
Reviewers: @i-am-sijia

Risk

Will this potentially break anything?
Low

Metadata

Metadata

Assignees

Labels

MetCouncilThings for MetCouncilchoreOther changes that don't modify src or test files

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions