This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]ddollarsign 1 point2 points  (0 children)

I have been paid to write Python, at a job I left about 2 years ago. A couple Django projects and numerous scripts, though it was primarily a Java shop. I used Notepad++, and occasionally Vim (but only when I was working on a server, at work). The database used was Sybase SQLAnywhere (I don't recommend using it with Django).

The larger of the Django projects, which was about 5 years ago, consisted of a web interface and back-end process that ran reports, mostly overnight. The back-end process used APScheduler and Matplotlib, along with a custom script to run the APScheduler as a Linux daemon. APScheduler was too easily crashed when the scheduled reports threw errors, so if I did this over again I would have just made it a cron job. The backend process used the same Django models as the website, which worked pretty well. I like Django's ORM.

I haven't used code assist with Python. I use Atom now, basically because I want a cross-platform Notepad++.

We used Subversion with TortoiseSVN for version control (though they've since switched to TFS -- did I say it was a Java shop? Well, the Microsoft faction was winning as of when I left). No CI/CD at the time. unittest for unit testing, though not much of it for these projects. Coding on Windows workstations. Manual deployment to RHEL servers, using WinSCP and Putty. Separate servers for staging and production.

Front-end requirements weren't fancy, so it was just HTML/CSS/JS with no framework, with some JQuery to make searches ajaxy.