Hi,
I'm -1. "Other frameworks..." is not an argument for me, and I don't
believe that `.gitignore` in the project template makes it more beginner
friendly as I wouldn't call a beginner someone who use VCS.
Adding `.gitignore` assumes that folks always use Git, that's not true.
Moreover, `.giti
Hey,
Thanks, I appreciate the response. It sounds like your main concern is the
overhead of maintaining the .gitignore file, is that right? Could that
potentially be mitigated by a clear writeup of what's included, why, and
then an easy way to close all other tickets? E.g. we could easily just use
Just want to say that I agree with Cory. Being a non-core feature/issue, I
don't see a reason of why not to re-evaluate the "denied" decisions.
On Friday, March 10, 2023 at 9:11:03 AM UTC+2 Cory Zue wrote:
> Is there a more nuanced discussion of this issue anywhere? The reasons
> stated in the
I don't really like the idea of this for a number of reasons.
A lot of people create the project in a subdirectory. For them, the
gitignore is in the wrong place.
Enough people are using GitHub that they create the repo first with one of
GH's provided gitignores, or copy it in after.
As Python c
I'm also against the idea, unless done in a very minimal fashion.
Many tools in the ecosystem put "ignore everything here" .gitignore files
into their not-normally-committed directories: at least Coverage.py, Mypy,
pytest, and virtualenv. So the trend is that less and less .gitignore
patterns are
I strongly agree with Adam and Tom, the extra and unnecessary burden of
maintaining the .gitignore file outweighs its advantages.
Cheers,
Tega.
On Fri, Mar 10, 2023 at 5:12 PM 'Adam Johnson' via Django developers
(Contributions to Django itself) wrote:
> I'm also against the idea, unless done i
What exactly would be considered the burden in maintaining a .gitignore?
Arthur
On Fri, Mar 10, 2023 at 11:37 AM Tega Ukavwe wrote:
> I strongly agree with Adam and Tom, the extra and unnecessary burden of
> maintaining the .gitignore file outweighs its advantages.
>
> Cheers,
> Tega.
>
> On Fr
Also -1 from my side.
Imho django should deal with django things, and not with other stuff
that may come handy on top. There are many more VCS than git, and even
with git in particular there are several ways to structure your repo. To
me this should stay a matter of VCS/repo tooling, not being
Here I quote Tom's reply to this thread: "As Python changes, as new tools
come out, the gitignore needs to be constantly updated. There will be a lot
of bikeshedding about what should and shouldn't go in. For example, the
.vscode directory sometimes has project specific code that should be
included
