[Draft] Issue #246: [DISCUSSION] Reconsider src/ directory requirement? #255
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤖 Auto-generated Draft PR
This draft PR was automatically created from issue #246.
Original Issue: #246
Analysis Summary:
The issue is well-defined with concrete examples from major Python projects. Relaxing src/ requirement to accept project-named directories aligns with common practice and AgentReady's goal of recognizing standard patterns.
The standard_layout detector for Python requires that all code be in a directory named
src/. However, in practice, it seems like a common practice in Python to name the source directory after the project itself; either the name of the root directory or some variation of it. For example:Of course,
src/is also seen sometimes, e.g.:So I would say that both of these patterns are relatively "standard" layouts, so I would expect models trained on common practice to be comfortable with both.
This PR was automatically created by the @agentready-dev workflow.
View activity log