On 16. 05. 23 13:15, Sandro wrote:
On 05-05-2023 15:10, Sandro wrote:
> On 27-04-2023 14:26, Sandro wrote:
>> Well, I submitted the package for review [2] and have been told that
>> vkbasalt not being published on PyPI is an issue wrt naming parity.
>> So, I filed a bug requesting publication on PyPI [3], but I haven't
>> heard back from upstream, yet. If upstream remains unresponsive, I would
>> need to either publish it myself or get the name reserved as described
>> in PyPI parity [4].
>
> It has been almost two weeks and I haven't heard back from upstream
> regarding my request for publication on PyPI.
Still no news from upstream. But I'd like to move on with packaging
vkbasalt-cli. Meanwhile bug reports regarding Bottles keep pouring [1]
in. Well, at least is shows that there's a user base for that package.
> What are the next steps I should take in line with PyPI parity? I'm
> leaning towards "Ask Python SIG to block the name on PyPI for you" and
> will consider publishing it myself at a later stage should upstream
> remain unresponsive.
Did I misunderstand/misinterpret the guidelines? The review is currently
stalled due to the PyPI parity issue.
Should I approach PyPI folks myself and ask them to block vkbasalt-cli
for me? Any kind of guidance is much appreciated.
Hi! Sorry for the silence.
It seems weird to ask PyPI admins to block a project that has working
code, so what I would do is upload the project on PyPI, and tell the
author that I'm happy to hand it over to him.
Do you want me to do it?