RFC: Use src/ directory
See original GitHub issuePut the package in src/marshmallow
, as recommended in these articles:
- https://blog.ionelmc.ro/2014/05/25/python-packaging/#the-structure
- https://hynek.me/articles/testing-packaging/
The benefits makes sense, but I haven’t yet run into the pitfalls talked about in those articles…
Strong opinions welcome!
Issue Analytics
- State:
- Created 5 years ago
- Reactions:4
- Comments:6 (6 by maintainers)
Top Results From Across the Web
[RFC] src directory #8451 - vercel/next.js - GitHub
Yep, I came here looking for any gotchas about putting /pages and other directories I use to organize my project (e.g. /components ,...
Read more >RFC 3944: H.350 Directory Services
The goal of the architecture is to 'directory enable' multimedia ... The use of a common, authoritative data source for call server, endpoint,...
Read more >RFC 1781 - Using the OSI Directory to Achieve User Friendly ...
Using the OSI Directory to Achieve User Friendly Naming RFC 1781 · This document specifies an Internet standards track protocol for the Internet...
Read more >Appendix A. Directory Server RFC Support
This chapter lists notable supported LDAP-related RFCs. It is not a complete list of RFCs Directory Server supports. A.1. LDAPv3 Features.
Read more >File-to-RFC | SAP Community
Hi, Explain me File-to-RFC and it parameters. ... Source directory in Communication channel shud b correctly mentioned.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@lafrech If we go forward with this, we should do it on both
2.x-line
anddev
to avoid complicated merges.I’m not sure but it might complicate the merges from 2.x. Not really a blocker as hopefully three won’t be many (how long are we maintaining 2.x when 3.0 is out ?) and since a lot of code has changed already, a lot of merges can’t be automatic and the changes must be ported manually (I suppose, I can’t tell since you’re the one performing those tasks).