Update .gitignore using gitignore.io

[altendky]

No description provided.

[coveralls-official]

Pull Request Test Coverage Report for Build 10580947399

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 83.891%

---

Totals
Change from base Build 10575607681:	0.0%
Covered Lines:	12301
Relevant Lines:	14663

---

💛 - Coveralls

[arvidn]

I believe the python wheel would be considered an "executable" in this context.

[altendky]

I see two topics here. They may be in conflict.

1. Should we include Cargo.lock file(s) in the repo?
2. Should we edit the standard output of the gitignore template?

For 1), there is presently a single Cargo.lock in the repo and it is revisioned. For that file, this entry in the configuration is irrelevant unless we remove the file from git. In that case git would not remind us to add it back. This doesn't seem like a critical backstop.

For 2), I guess we can edit it. When someone does an update to include either updated changes from the templates for the groups of ignores selected here, or to add another group such as for another editor, then they will overwrite the manual modification. Odds are the rust template won't change drastically so the manual modification will show in the diff and be noticed. If we were to make the ignore files managed like other general repo files then this exception would probably get more annoying. Especially since the comment suggests it is a conditional thing that would vary and require both additional configuration per rust repo and code to manage the modification.

Given the near zero upside of modifying this and the everpresent issues around modifying generated content, I'm obviously not in favor of it. But, if someone clicks commit below, then so it goes.

Suggested change

	Cargo.lock
	# Cargo.lock

[arvidn]

this is the file extension for native python modules on windows, right? Do we not need this?

[altendky]

It is covered by *.py[cod].