Skip to content
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

28 current method for loading the bot api key is archaic #29

Merged
merged 6 commits into from
Apr 19, 2022
Merged

28 current method for loading the bot api key is archaic #29

merged 6 commits into from
Apr 19, 2022

Conversation

elroykanye
Copy link
Collaborator

@elroykanye elroykanye commented Apr 13, 2022

fixes #28

Changes coming into this repo from this branch include:

  • added the python-decouple package, using decouple.config to load the env var for the API key
  • deleted the utils.py file

requirements.txt Outdated
@@ -1,3 +1,4 @@
python-telegram-bot
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this file automatically generated by python -m pip freeze > requirements.txt ?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh its not

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you generate that file with that commend, and try to use fixed libraries

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will :) thanks for this

@elroykanye
Copy link
Collaborator Author

@elhmn , I have done the updates 💯

@elroykanye elroykanye merged commit 3a2a775 into osscameroon:master Apr 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

current method for loading the bot api key is archaic
3 participants