New package: PYTHIA8 v0.1.0

[JuliaRegistrator]

• Registering package: PYTHIA8
• Repository: https://github.com/JuliaHEP/PYTHIA8.jl
• Created by: @peremato
• Version: v0.1.0
• Commit: 9b576775e56d11536594fe4fef97bea1f717e9d7
• Reviewed by: @peremato
• Reference: JuliaHEP/PYTHIA8.jl@9b57677#commitcomment-147197461
• Description: Pythia8 Julia interface
• Release notes:

## Initial release

[github-actions]

Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. New package registration

Please make sure that you have read the package naming guidelines.

2. AutoMerge Guidelines which are not met ❌

• Name does not meet all of the following: starts with an upper-case letter, ASCII alphanumerics only, not all letters are upper-case.

3. Needs action: here's what to do next

1. Please try to update your package to conform to these guidelines. The General registry's README has an FAQ that can help figure out how to do so.
2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless the AutoMerge issue is that you skipped a version number).

If you need help fixing the AutoMerge issues, or want your pull request to be manually merged instead, please post a comment explaining what you need help with or why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the public Julia Slack for better visibility.

4. To pause or stop registration

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.

[peremato]

[noblock] @goerz Can you please unblock the request with this new name. Thanks!

[goerz]

[noblock] So yeah, unfortunately, this still caught the "not all letters are upper-case" check, which I can't override. But it should be fine. You just have to go back on Slack in three days and ask for a maintainer to merge it manually. I don't see this PR as particularly controversial, so it's just a matter of getting someone's attention

[peremato]

Thanks!

[carstenbauer]

[noblock] Why is this called PYTHIA8.jl, that is, why is the version number included in the package name? If a version 9 of the upstream package is released, should we expect a PYTHIA9.jl? That doesn't seem ideal. Otherwise I think this can be merged.

[Moelf]

[noblock] very good question, for some reason HEP has settled to this pattern:

• https://launchpad.net/mg5amcnlo
• https://github.com/scikit-hep/uproot5
• https://gitlab.cern.ch/hepmc/HepMC3
• https://en.wikipedia.org/wiki/Geant4

[peremato]

[noblock] PYTHIA6 was written in FORTRAN, PYTHIA8 is in C++. If ever there is a PYTHIA9 will be written on a different language, perhaps in Julia 😄, so we do not expect a PYTHIA9 in the immediate future.

[carstenbauer]

Alright, I take it that these different "versions" are more like entire rewrites, in which case this makes sense. I'll go ahead and merge this.