New package: iCSV v1.0.0-DEV

[JuliaRegistrator]

• Registering package: iCSV
• Repository: https://gitlab.com/leibersp/PYiCSV.jl
• Created by: https://gitlab.com/leibersp
• Version: v1.0.0-DEV
• Commit: bf96db5739007cdb63a14a81c6080adb3d4d9b6b
• Git reference: HEAD

[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.

• Name is not at least 5 characters long

• Repo URL does not end with /name.jl.git, where name is the package name

• Version number is not allowed to contain prerelease data

• The following dependencies do not have a [compat] entry that is upper-bounded and only includes a finite number of breaking releases: Conda, PyCall

  Extended explanation

  Your package has a Project.toml file which might look something like the following:

  name = "YourPackage"
  uuid = "random id"
  authors = ["Author Names"]
  version = "major.minor"
  
  [deps]
  # Package dependencies
  # ...
  
  [compat]
  # ...

  Every package listed in [deps], along with julia itself, must also be listed under [compat] (if you don't have a [compat] section, make one!). See the Pkg docs for the syntax for compatibility bounds, and this documentation for more on the kinds of compat bounds required for AutoMerge.

• I was not able to load the package (i.e. import iCSV failed). See the AutoMerge logs for details.

• Package name similar to 4 existing packages.

  1. Similar to uCSV. Damerau-Levenshtein distance 1 is at or below cutoff of 2. Damerau-Levenshtein distance 1 between lowercased names is at or below cutoff of 1.
  2. Similar to CSV. Damerau-Levenshtein distance 1 is at or below cutoff of 2. Damerau-Levenshtein distance 1 between lowercased names is at or below cutoff of 1.
  3. Similar to SCS. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  4. Similar to WCS. Damerau-Levenshtein distance 2 is at or below cutoff of 2.

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.

[goerz]

You have to make sure to also change the project name and the version number in the Project.toml file.

On the topic of version numbers: I’d recommend starting with v0.1.0 even if you’re fairly sure the API is stable. Treat it as the v1.0.0-dev. Once it’s seen some use and you know there are no major issues and design flaws, and once the stable API is fully documented as such, you can just make a v1.0.0 release then.