The PyPI trove classifier "Framework :: BEAT" does not work

The deployment of beat packages in PyPI is broken because they all contain Framework :: BEAT. I think we should remove this globally so that the deployment works.

Example: https://gitlab.idiap.ch/beat/beat.backend.python/pipelines/24051

The question is: do we really want these package to appear on PyPi at all since they are mostly targeted to conda ?

And if yes, then it would likely make sense to add that classifier if it is possible. It is likely the case since you do that with bob.

Good question - I tried asking that on SO (https://stackoverflow.com/questions/18338178/how-to-propose-a-new-trove-classifier-on-pypi)

I found the place to ask for it: https://github.com/pypa/warehouse/issues/5156

Let's see if that is accepted.

mentioned in commit 02ab4e1b

mentioned in merge request !35 (merged)

mentioned in commit beat.core@b7ed11ba

mentioned in merge request beat.core!50 (merged)

mentioned in commit beat.cmdline@2dc46701

mentioned in merge request beat.cmdline!56 (merged)

mentioned in commit beat.editor@af2c62d8

mentioned in merge request beat.editor!33 (merged)

@beat: May I please ask each of you to:

1. Go to github and login with your account
2. Go to this URL: https://github.com/pypa/warehouse/issues/5156
3. Add a message like I'm a developer of a BEAT framework component and confirm I'll be using the new trove classifier as soon as it is available in there?

We need as many supporters as we can get.

made the issue confidential

made the issue visible to everyone

@beat: kind reminder - if you haven't yet add your pitch, please do so ASAP.

Closing as trove has been added as per:

https://github.com/pypa/warehouse/issues/5156#issuecomment-481639307

closed

@samuel.gaist: thx for closing this - as a follow up, could I please ask you to open issues or MRs on all python packages so we actually make use of the requested classifier? Thx in advance!

mentioned in issue #21 (closed)

mentioned in issue beat.core#75 (closed)