You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Explain why having a .pyc file under source control isn't a good idea
What steps will you take to remove the existing files (include git commands used)
Which other files or folders would you not have under source control
The text was updated successfully, but these errors were encountered:
.pyc are files in form of bytecode that is compiled from Python source files.
Having those files onboard source control might cause trouble due to code for specific module being available in .pyc even after deleting the source file. The module may still be imported even when the source is long gone.
git -rm --cached *.pyc <-- command to use to remove .pyc files from source control tracking.
If preprocessors (Sass, Less, CoffeeScript etc.) are used then I would vouch for not including generated files due to irrelevance.
Explain why having a .pyc file under source control isn't a good idea
What steps will you take to remove the existing files (include git commands used)
Which other files or folders would you not have under source control
The text was updated successfully, but these errors were encountered: