New package: PyCaesar v0.1.0

[JuliaRegistrator]

• Registering package: PyCaesar
• Repository: https://github.com/JuliaRobotics/PyCaesar.jl
• Created by: @dehann
• Version: v0.1.0
• Commit: 0d4bc802226eff1eab70344eda8c54003fc2c978
• Reviewed by: @dehann
• Reference: tag v0.1 releases JuliaRobotics/PyCaesar.jl#21
• Description: Python extensions relating to Caesar.jl

[github-actions]

Your new package pull request does not meet the guidelines for auto-merging. Please make sure that you have read the General registry README and the AutoMerge guidelines. The following guidelines were not met:

• Package name similar to 1 existing package.
  1. Similar to Caesar. Damerau-Levenshtein distance 2 is at or below cutoff of 2.

Note that the guidelines are only required for the pull request to be merged automatically. However, it is strongly recommended to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human.

After you have fixed the AutoMerge issues, simple retrigger Registrator, which will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number).

If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the Julia Slack to ask for help. Include a link to this pull request.

Since you are registering a new package, please make sure that you have also read the package naming guidelines: https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1

---

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. You can edit blocking comments, adding [noblock] to them in order to unblock auto-merging.

[dehann]

Good day, I would like this package to registered with the current name PyCaesar please. I am an author of both Caesar and this new PyCaesar. The point of PyCaesar is to expose all the functionality of Caesar plus PyCall related features.

We have strong use-cases both with and without PyCall and therefore found it sensible to separate out to PyCaesar the related functionality. In addition, this approach allows better use of weakdeps, since "double weakdeps" with both PyCall and other packages does not seem like the right design.