An old Python 2 script that nobody will touch
A business-critical script written against Python 2, running on a server that is years overdue for an upgrade, with no tests and no original author.
Running on Python 3, with tests
Working with Python?
Most Python we inherit started as one script for one job, grew for a few years, and then the person who understood it moved on. We read what is actually there, get it running on a current version, and leave it in a state the next person can pick up.
What it is
Python, created by Guido van Rossum in 1991, is a general-purpose high-level language. It is read like plain English by people who have never seen it before, which is one reason it ended up running so much of the world's glue code, reports, and overnight jobs.
It dominates data science, machine learning, web back ends built on Django, Flask or FastAPI, automation, scientific computing, and DevOps scripting. Python 2 reached end of life January 1, 2020, so Python 3 is the only supported line. The language is looked after by the Python Software Foundation and a large contributor community.
The honest version
No technology is all upside. This is where Python earns its place and where it tends to cause trouble.
Sound familiar?
The Python problems that bring people to us, and what you have once each one is fixed.
A business-critical script written against Python 2, running on a server that is years overdue for an upgrade, with no tests and no original author.
Running on Python 3, with tests
A folder of scripts with no README, no requirements file, and a vague memory that one of them emails the invoices on the first of the month.
Documented, owned, repeatable
A new OS release removed the old Python binary or moved it, and overnight jobs have been silently failing for weeks before anyone noticed.
Jobs running, with alerts if they don't
Pinned versions that no longer build on a current OS, or private packages that depend on libraries that have since been renamed or removed.
Reproducible environment, pinned properly
A Pandas or pure-Python job that grew past the size it was designed for and now overlaps with the next day's run.
Finishes in minutes, same answers
A script that loads a whole file into memory at once, fine for last year's data, fatal for this year's.
Streams the data, finishes cleanly
What we do
Call us for one broken script, or hand us the whole folder.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Yes. We read the code, capture what it currently produces so we have something to compare against, move it to Python 3 piece by piece, and run the old and new side by side until the outputs match. Scripts with no tests get tests as part of the job.
That is most of what we do with Python. We read what is actually there, write down how it is meant to work, get it running cleanly on a current Python with a pinned environment, and leave it documented enough that the next person has a chance.
Usually the OS has moved or removed the Python binary the cron line was pointing at, or a library the script depended on no longer builds, or a feature the script used was deprecated in the newer Python. Pinning the environment and using a virtual env fixes this for good.
Rarely the right first step. Python slowness is almost always a loop doing too much work, a Pandas call fighting itself, or a database query that needs an index. We measure first, and a rewrite only comes up if the measurements justify it.
Most often an old requirements file pins versions that no longer build on a current OS, or depends on a package that has since been renamed. We rebuild the environment against versions that actually install, keep the behaviour the same, and lock it so it keeps working.
Estimates are free. Send us the script or describe the job and you get a price before any work starts.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: