-
Notifications
You must be signed in to change notification settings - Fork 968
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Find better name for "non-src" layout (picked: flat) #618
Comments
Another possibility:
One thought is that the name "src" layout communicates primarily where e.g. |
I think it should be just "src" layout and others. The src layout seems to be misused and denies the fact that |
Since this is bikesheding after all, I think it is important to decide what to focus on. I think that'll be: what these terms might communicate to first timers and to avoid names that can be mixed with other common concepts. IMO that means we can take the following off the table:
That leaves us with "flat" and "top-level". Between these two, I think I'll go with flat since it's a common enough name and conveys the meaning well enough. It'll be pretty search friendly too. |
No. "Flat" layout conflicts with its duplicate path name convention. |
Not sure if you're serious or trying to be funny/sarcastic there. Anyway, mediocre doesn't make sense (it's not a neutral term) so I'm going to ignore all of that. |
Directory name duplication happens in both layouts when the source project and the published package share a name (it just appears as So the general way of describing the two layouts would be:
|
@ncoghlan I'm gonna borrow that wording, for the discussion topic. :) |
Hello am actually an intermediate python developer but then i think "auto_src.py" will make a good layout as it will kind of notify users that its automatic and he no specific layout🙌🏼 |
The concensus here seems to be "flat". :) |
From #320 (comment):
Suggestions so far:
The text was updated successfully, but these errors were encountered: