release capa as pypi project `capa`

[williballenthin]

we got control of the pypi package capa so should we publish to that package instead? we currently use flare-capa. if we're going to do it, v2.0 is the time.

alternatively, we could publish to both names?

[mr-tz]

not sure what the best practice is here... if we move to capa can flare-capa "redirect" there?

[Ana06]

Ideally I would keep both for some time as people using flare-capa can then still update. However I don't know if this is easy to do, would we need two setup.py? Maybe it is not worth the effort and it is ok to just keep capa and deprecate flare-capa. I think it would be nice to update old capa versions to capa as well., in case someone wants to use an old version (for example to move to use the new name without updating to the last version as it includes breaking changes).

[williballenthin]

lets not migrate to the capa name in v2.0 - its just two days away and would be a pretty big change for our users.

maybe we plan to do this for v3.0?

still, we can update the capa name between now and v3.0 to do things like:

• point users to the correct package: flare-capa, and/or maybe
• have it be a trivial package that simply lists flare-capa as a dependency so it mostly works like users expect.

[Ana06]

why don't we do it the other way around? change to the capa name in v2.0 and make flare-capa listing capa as dependency and maybe a warning. That should keep working for users that have capa already installed.

There is always confusion with the flare-capa name. So I personally wouldn't delay the change.