Skip to content

Conversation

@rlskoeser
Copy link
Member

@rlskoeser rlskoeser commented May 22, 2025

  • add installation instructions (somehow just noticed they were missing! 😅)
  • fix the dates for century so the numbers match the text (noticed while working on notebook submission to US-RSE'25)
  • update the develop version from 0.4 to 0.5.0.dev0 (must have forgotten to do this when I made the 0.4 release)

Summary by CodeRabbit

  • Documentation
    • Added an "Installation" section with detailed installation instructions.
    • Simplified example import statements.
    • Corrected example date intervals for the 19th and 20th centuries with updated durations and representations.
  • Chores
    • Updated the version number to 0.5.0.dev0.

@rlskoeser rlskoeser requested a review from jdamerow May 22, 2025 20:15
@coderabbitai
Copy link
Contributor

coderabbitai bot commented May 22, 2025

## Walkthrough

The changes updated the README.md file to add a new "Installation" section with pip and GitHub instructions, and corrected example date ranges for centuries. Additionally, the version string in the package's __init__.py was incremented from "0.4.0" to "0.5.0.dev0".

## Changes

| File(s)                | Change Summary                                                                                         |
|------------------------|-------------------------------------------------------------------------------------------------------|
| README.md              | Added "Installation" section with pip and GitHub instructions; corrected example usage for centuries; improved formatting and line wrapping.  |
| src/undate/__init__.py | Updated `__version__` from "0.4.0" to "0.5.0.dev0".                                                   |

## Poem

> A hop and a skip, the version jumps high,  
> README now tells you the how and the why.  
> Centuries corrected, instructions anew,  
> Pip or from GitHub—install what you do!  
> 🐇✨

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (2)
README.md (2)

28-41: Installation instructions look comprehensive.

The new Installation section clearly describes how to install from PyPI or GitHub, which addresses the previous omission. Consider adding a note on pinning to the exact dev version (e.g., pip install undate==0.5.0.dev0) if users want the latest published development release.


145-146: Enhance example consistency.

Currently, the 20th century example shows only the interval object but omits its duration. For consistency with the 19th century example, consider adding a .duration().days line and expected output immediately afterward.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e664a81 and 473da51.

📒 Files selected for processing (2)
  • README.md (2 hunks)
  • src/undate/__init__.py (1 hunks)
🔇 Additional comments (1)
src/undate/__init__.py (1)

1-1: Version bump is appropriate.

The __version__ has been updated to "0.5.0.dev0" in line with the README changes. Please verify that any other version references (e.g., in setup.py, pyproject.toml, CI/CD workflows, or documentation) are also updated to avoid mismatches.

>>> UndateInterval(Undate(1900), Undate(2000), label="20th century")
<UndateInterval '20th century' (1900/2000)>
>>> UndateInterval(Undate(1801), Undate(1900), label="19th century")
>>> UndateInterval(Undate(1801), Undate(1900), label="19th century").duration().days
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking at these examples, my first question is are beginning and end values inclusive or exclusive? Looking up the date range for 19th century (which apparently I didn't know 😅), I realize it's inclusive but maybe worth pointing out?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point. Done!

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

♻️ Duplicate comments (1)
README.md (1)

162-166: 19th and 20th century intervals corrected
The string representations and duration calculations for the 19th (1801/1900, 36524 days) and 20th (1901/2000) centuries now accurately reflect the intended ranges.

🧹 Nitpick comments (3)
README.md (3)

28-41: Installation instructions added—consider adding minimum Python version and venv usage
The new Installation section clearly outlines pip and GitHub install options. For completeness, you might mention the supported Python versions (e.g., 3.7+) and recommend using a virtual environment to isolate dependencies.


45-45: Add comma after introductory adverb
For readability, add a comma after “Often”:

- Often humanities and cultural data include imprecise or uncertain
+ Often, humanities and cultural data include imprecise or uncertain

232-233: Replace bare URL with markdown link
Avoid bare URLs to satisfy markdownlint and improve readability; use link syntax:

-* For more examples, refer to the code notebooks included in the[examples] (https://github.com/dh-tech/undate-python/tree/main/examples/) in this repository.
+* For more examples, refer to the code notebooks included in the [examples](https://github.com/dh-tech/undate-python/tree/main/examples/) in this repository.
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

233-233: Bare URL used
null

(MD034, no-bare-urls)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 47a6c57 and e01c065.

📒 Files selected for processing (1)
  • README.md (9 hunks)
🧰 Additional context used
🪛 LanguageTool
README.md

[uncategorized] ~44-~44: Possible missing comma found.
Context: ...velop#egg=undate ``` ## Example Usage Often humanities and cultural data include im...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~180-~180: A comma may be missing after the conjunctive/linking adverb ‘Currently’.
Context: ...ut an Undate object in those formats. Currently available converters are "ISO8601" and ...

(SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)

🪛 markdownlint-cli2 (0.17.2)
README.md

233-233: Bare URL used
null

(MD034, no-bare-urls)

🔇 Additional comments (1)
README.md (1)

58-58: Simplify import path for users
Switching from from undate.undate import ... to from undate import ... is a nice UX improvement and aligns with common package structures.

@rlskoeser rlskoeser merged commit 2a7bcc1 into develop May 23, 2025
9 checks passed
@rlskoeser rlskoeser deleted the feature/improve-readme branch May 23, 2025 14:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants