-
Notifications
You must be signed in to change notification settings - Fork 431
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
use gitignore for compiled python etc #29
Comments
Thanks for the tip! I'm on it... -jjg
…On Thu, May 30, 2024 at 11:35 AM scruffynerf ***@***.***> wrote:
It's a best practice to use .gitignore to remove the pycache directories,
which are both autocreated, and user specific (version, machine, etc etc)
—
Reply to this email directly, view it on GitHub
<#29>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZ6GXG6BEV6LQERCNKXZ3DZE5INRAVCNFSM6AAAAABIRIMCTCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMZDMMBZHA4TEOI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Had to meet you half way. Streamlit immediately digests GitHub updates, so a valid config.py is mandatory. Thanks again... |
@jgravelle |
Four. Got 'em. Thanks...
…-jjg
On Thu, May 30, 2024 at 3:47 PM scruffynerf ***@***.***> wrote:
You should delete the existing *pycache* folders (there are 3 I think)
—
Reply to this email directly, view it on GitHub
<#29 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZ6GXEZQQBWJLOYPVL7BFDZE6F47AVCNFSM6AAAAABIRIMCTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBQHAZTQOBSGY>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's a best practice to use .gitignore to remove the pycache directories, which are both autocreated, and user specific (version, machine, etc etc)
Also, provide a sample config file to copy before first use, and remove the actual config from the repo, otherwise any git update balks due to file changes made to that config file.
The text was updated successfully, but these errors were encountered: