Python version upgraded from 3.6 to 3.13
Django version upgraded from 2.2 to 4.2 and other dependency upgrades can be found here

Branch changes: https://bitbucket.org/lorainelab-deepthi/appstore/branch/python-upgrade

Updated the development guide document
https://docs.google.com/document/d/1_9C03q6TD5wjLqfVLKsuDsIEQ4-qrS0JhONO5VBOwaA

Someone testing this,
Go through the steps mentioned in the document to setup the local environment, Please mention if any steps are missing in the documentation.

Moving this to review

I walked through the testing steps with Deepthi to set up a local environment for testing her changes. I ran into a blocker while testing which ended up being caused by a line in the code that sends mail to a user after submitting an app. This has since been fixed. I then ran into another issue where a NameError was being thrown with each search in the App Store. This has also been fixed. In addition to these issues being resolved, all filters appear to be working correctly within the App Store. App submissions and approvals are also working as expected.

Recommending PR!

A question for Paige Kulzer:

You mentioned in your previous comment that there was:

a blocker while testing which ended up being caused by a line in the code that sends mail to a user after submitting an app. This has since been fixed

Please describe what was done to fix the blocker.

My understanding of the development environment setup is that the tester needs to set up email capability for their local development / testing environment using a Google account. Is that what you did to fix the blocker? Please explain what was done to fix the blocker.

cc:

saideepthi jagarapu
Paige Kulzer

I'll let Deepthi explain what she did to fix the blocker. I believe the line of code I mentioned needed to be commented out in order for me to move forward with testing, but I'm not sure what changes were made beyond that. We did set up email capability for the testing environment per step 11 of the document linked in Deepthi's first comment (App Store Set-up - Development environment).

Once the setup for email is properly configured locally, the blocker for the mail is resolved. It's been tested. Please review the screenshot attached Ann Loraine

It sounds like saideepthi jagarapu is able to run the testing environment but Paige Kulzer could not. That is, developer saideepthi jagarapu was able to trouble-shoot the problem and fix it on her system, but tester / verifier Paige Kulzer could not.

Is the documentation misleading, wrong, or unclear?

Ideally, the documentation explaining how to set up the email functionality would be clear and correct enough to enable a tester (e.g., Paige Kulzer) to set up the testing environment without having to delete (comment out) code.

Could you guys work together to ensure that the documentation is correct?

I'm worried that when I try to test the App Store code on my system, or deploy it into production, this same step will fail.

Just a correction, Paige used my google email as she doesn't have one. Because of which we were facing little discrepancies in email part. Also, I want someone to check the mail part who have active google account.

Also, I was able to test end to end including mails, but sometimes I'm also not getting mails. This seems to be a local issue nothing to do with the python upgradation as this particular send_mail() django function acts similarly and is not deprecated or changed for newer django version 4.2.

For example, when i pushed my code and tested a couple of weeks back, I was able to test end to end including mails.
But when I tried to test with paige, even I faced issue with mail in my personal space.

I feel there are some gaps in development documention which needs to be reviewed.

attn: Ann Loraine

Thank you for the clarification saideepthi jagarapu.

I think we should merge these changes into the main branch, and capture tasks "review clarity of development documentation" or "review development documentation changes" in new ticket(s).

Regarding the second option:

Reviewing changes (recent edits in the Google Doc) seems easiest and best.

Next, we could do: "Set up a development / testing environment by following development documentation instructions and report any problems."

Sure Ann Loraine, I will create ticket for the same and link to this ticket.

PR for the changes : https://bitbucket.org/lorainelab/appstore/pull-requests/285

I've successfully run through the documentation again with a new gmail account. I was able to log in and submit an app with no issues. I was also able to log in as admin, accept the pending app, and use all filters present in the app store as expected. Since a new ticket has been created for finalizing the documentation, I'm going to go ahead and close this ticket now.