I just found out that version "0.6.0.incubating" doesn't conform to PEP440,
the only supported versions are like:
0.1.0
0.1.0a1 for alpha release
0.1.0b1 for beta release
0.1.0rc1 for rc release
We cannot have a name like x.y.z.incubating for publishing. So for Python
release we cannot add "incubating" into the package name. I also checked
various incubating projects, all of them don't have "incubating" in their
package version or name. Do we have any better solution?
Besides, we don't ship Python distribution using ASF mirror system, we
should use Pypi. So we don't have to upload Python package to the SVN, I
will delete them from SVN.
Best,
Jerry
Justin Mclean <jus...@classsoftware.com> 于2024年9月1日周日 22:55写道：
> Hi,
>
> > This Python package name is generated from Python configuration file and
> > its version number, we cannot simply rename the package name using mv,
> > otherwise, it will be failed to upload to Pypi and install.
>
> Yes we can there isn’t anything preventing us from have two slightly
> different names in different places. Remember the only official
> distribution is the ASF mirror system.
>
> > The only thing we can do is change the version number to
> "0.6.0.incubating"
> > ("-" is not allowed for Python version numbers) and re-package them. Is
> the
> > version number "0.6.0.incubating" ok for you?
>
> That would also work.
>
> > Yeah, the readme is more about how to build from scratch. This Python
> > package is a release package that can be used directly, no need to
> compile.
> > The README can be improved, but it's not a blocking thing here.
>
> As I said it was a minor issue, not a blocking one. I mentioned it as it
> may be an issue that the IPMC brings up as they woudl probably not be able
> to compile that package without some guidance that’s not in the README.
>
> Kind Regards,
> Justin
