Skip to content

Fix: Remove uvloop (unsupported on Windows), add pytest, and configure .gitignore #44

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

TulsiBasetti
Copy link

Summary of Changes

  • Removed uvloop from requirements.txt as it is not supported on Windows and is not used in the codebase.
  • Added missing pytest dependency to requirements.txt since it was imported in app.py.
  • Created a .gitignore file to exclude virtual environments, compiled Python files, IDE settings, logs, and system files.

Why These Changes Matter

These updates enhance cross-platform compatibility (especially for Windows users), ensure a proper environment setup, and adhere to best practices for Python development.

Verification

  • Verified that uvloop was not imported or used in any .py file.
  • Ensured that pytest is required by inspecting the imports.
  • .gitignore follows standard Python, VS Code, and OS ignore rules.

Note: Code execution was not performed, but all changes were carefully verified through file inspection and setup steps.

@TulsiBasetti TulsiBasetti force-pushed the tulsi-basetti-flask-mongo branch from c82cce7 to 20d4d1a Compare June 18, 2025 07:50
…oject

Signed-off-by: Tulsi Basetti <basetti.tulsi@gmail.com>
Signed-off-by: 22051814 <basetti.tulsi@gmail.com>
@TulsiBasetti TulsiBasetti force-pushed the tulsi-basetti-flask-mongo branch from 20d4d1a to c892b37 Compare June 18, 2025 07:54
Copy link

@pratik-mahalle pratik-mahalle left a comment

Choose a reason for hiding this comment

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

Hi @TulsiBasetti, Thanks for raising this pr.
Unfortunately, this PR doesn’t include any meaningful changes, typos and breaking links are supposed or just content changes are to be reported not fixed. You can do so on the specific two repositories that we provided. In the future, please ensure that a PR in this repo is raised only if you’ve made substantial updates or solved a particular issue. This helps keep the process efficient and organized.
This being a part of an assignment in api fellowship would be counted since you were supposed to create a pr but wont be merged since this is not that relevant of a change. I’m sure you understand, and I appreciate your cooperation on this. We will be closing this PR for now.

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.

2 participants