fix rose deployment

[andre-merzky]

This PR fixes #66.

[gemini-code-assist]

Summary of Changes

Hello @andre-merzky, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves a deployment problem by modifying the pyproject.toml configuration. The change specifically adds a [tool.setuptools.packages.find] section, directing the build system to locate packages within the 'rose' directory. This ensures that the 'rose' package is properly discovered and included when the project is packaged and deployed, thereby fixing the reported issue.

Highlights

• Deployment Fix: This pull request addresses and fixes a deployment issue related to the 'rose' package, as indicated by the title and description.
• Build Configuration: The pyproject.toml file has been updated to explicitly tell setuptools where to find the 'rose' package, ensuring it is correctly included during the build process.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[Copilot]

Pull Request Overview

This PR fixes rose deployment issues by adding setuptools package discovery configuration to ensure the rose package is properly found and packaged during installation.

• Adds [tool.setuptools.packages.find] section to specify package location

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The where parameter should point to the directory containing the package, not the package itself. If 'rose' is the package name, where should be ["."] (the project root) or omitted entirely. If the package is inside a src/ directory, use where = ["src"]. The current configuration will look for packages inside the rose directory, which is likely incorrect.

Suggested change

	where = ["rose"]
	where = ["."]

[gemini-code-assist]

Code Review

This pull request fixes the package deployment by configuring setuptools to correctly find the rose package. The change is functional and addresses the issue. I have added one comment regarding project structure conventions that could improve long-term maintainability by making the project layout more intuitive for developers.

[gemini-code-assist]

Using where = ["rose"] suggests an unconventional project layout where the source directory is named the same as the package (rose). This can be confusing for developers. A more common convention in Python projects is to use a src layout, where all source code resides in a src directory. Adopting this convention would mean restructuring the project to have src/rose/... and changing this configuration to where = ["src"]. While this is a larger change outside the scope of this PR, it's a good practice to consider for improving project clarity and long-term maintainability.