Leading Low Cost Python 2 Developers Sydney, Melbourne, Brisbane, Perth, Adelaide
Capture what the code does today. Then move it and prove nothing changed.
For businesses with scripts, services and scheduled jobs still running on Python 2. We record what the code produces, contain the risk while it stays put, move it to a current Python 3, and prove the output is the same.
More about this service
We are an Australian team working with businesses in the United States, the United Kingdom, New Zealand and Australia. Every engagement starts with a scoped technical assessment, so the estimate that follows is based on your code and your data.
- Assessment A scoped technical review before any estimate
- 18+ yrs Building business software
- Independent No licence commission, no reseller agenda
- US UK NZ AU Australian team, no account managers
Built here. Your data stays here.
- No offshore development. Everything is written by our own team in Australia. Nothing is subcontracted overseas.
- Your data stays onshore. Hosted in Australia, on infrastructure you own, under Australian law.
- Every state, not just ours. Perth, Melbourne, Sydney, Brisbane, Adelaide and everywhere between.
Scripts nobody looks at, with no security fixes
Python 2 code tends to be scripts and services that do something important and unglamorous: processing files, moving data between systems, producing reports, running on a schedule. Nobody looks at them, because they work.
Read more
The exposure is in what they depend on. Every library pinned to a Python 2 version stopped receiving security fixes, and the server is often held on an old operating system to keep them running. The change that makes the move awkward, how text and raw bytes are told apart, is also what makes automatic conversion unreliable.
Our Python 2 developer service is for businesses in Sydney, Melbourne, Brisbane, Perth and Adelaide. It covers three kinds of work: code fixes and updates, migration to a modern technology stack, and ongoing maintenance and support.
Three ways forward for Python 2 code
The first is worth doing whatever comes next.
-
Contain it and record it
What each script takes in and produces is captured as tests. The server is isolated as far as the job allows. Nothing changes for the business, and the code is finally understood.
-
Port it to Python 3
The code is converted with tools, then reviewed by hand where text and bytes meet. Libraries are replaced with maintained ones. The tests prove the output has not changed.
-
Replace or retire it
Some scripts are easier to write again than to port, and some turn out to do nothing anybody needs. Both are found during the first step.
What we do with Python 2 code
Six kinds of work. Most engagements are three or four of them.
-
Inventory
Every script, service and scheduled job found, with what starts it and what it touches.
-
Behaviour tests
Real inputs and outputs captured and turned into tests, so the move can be proven.
-
Porting
Code converted to a current Python 3, with the handling of text, bytes, division and file encodings reviewed by hand.
-
Library replacement
Dependencies with no Python 3 version replaced by maintained ones, or the small part in use written again.
-
Server moves
The jobs moved off the old operating system onto a current one, with schedules and credentials carried across.
-
Ongoing maintenance
The code kept on a supported Python as versions retire, so this does not happen again.
Containing it, porting it and rewriting it are different projects
Most codebases need a mix of the three.
-
Leave it on Python 2, contained
Acceptable for an internal script on an isolated machine, for a while. Not acceptable for anything that handles outside input or can be reached from the internet.
-
Port to Python 3
The code keeps its shape and its author would still recognise it. Right for most scripts and services that do their job well.
-
Write it again
Right for code that is tangled, or that leans on a library with no successor. With behaviour tests in hand, a rewrite can be proven the same way as a port.
What a Python 2 assessment looks at
The dates are from the Python project. The rest is about what the code touches.
-
Support status
The Python project retired Python 2 on 1 January 2020 and made its last release, 2.7.18, in April 2020. Python 3 versions retire on a schedule too, about five years after release, so the target is a version with years left.
-
What there is
Scripts, long running services, scheduled jobs and anything started by another system. The list is usually longer than anyone expects.
-
Dependencies
Every library the code imports, the version it is pinned to, and whether a Python 3 version exists.
-
Text and bytes
Wherever the code reads files, talks to a network or a database, or handles names with accents. This is where behaviour changes without an error.
-
Tests
Whether any exist. Usually none do, and capturing current behaviour is the first real work.
-
The server
The operating system the code is held on, and what else lives there.
-
Exposure
Whether the code handles input from outside the business or can be reached from the internet. This sets the urgency.
-
Who wrote it
Whether the author is still available to explain what it is for.
Python 2 scripts still doing important work in the background?
What the assessment needs from you
A fixed-scope piece of work with a written result: the options, the risks of each, and a staged estimate. No production data is sent by email. We agree a secure way to share it first.
-
The code
Access to the scripts and services, and whether they are in source control.
-
What they do
What each is for, as far as anybody knows.
-
Schedules
What runs on a timer, and when.
-
The server
The operating system and who manages it.
-
Connections
Databases, file shares and other systems the code reads from or writes to.
-
Sample data
Real inputs and outputs that can be used to prove the move, shared securely.
-
What is hurting
The two or three problems that started the conversation.
-
The way back
How long the business can run on the old system if a cutover has to be reversed.
From assessment to code on a supported Python
By video call and screen share, at meeting times agreed to suit you.
-
Inventory and assessment
We find every script and job, list what each depends on and how exposed it is. You get that list in writing, with options and a staged estimate.
-
Capture behaviour
Current inputs and outputs are recorded and turned into tests.
-
Proof of concept
One representative script, including an awkward one, is ported and shown to produce the same output.
-
Staged work
The work is done in stages agreed from the assessment, each with its own scope and estimate, starting with whatever is hurting the business most.
-
Side by side running
Old and new run on the same inputs, and the outputs are compared until they match.
-
Cutover and support
Each switch is planned with a way back. We watch the first days of live use, then maintain the system for as long as it stays in service.
What people ask us about Python 2
Can an automatic tool convert Python 2 to 3 for us?
It gets part of the way, and it will not tell you about the part that matters. The handling of text and bytes changes behaviour without raising an error, so converted code needs a deliberate review and tests to prove it.
Our code works. Why change it?
The code is not the exposure. The libraries are. Packages pinned to Python 2 stopped receiving security fixes, and the server is usually being held on an old operating system to keep them running.
We have no tests. Is that a problem?
It is the first thing to fix. We capture what the current code produces and turn that into tests, so the move can be proven and not hoped for. The tests stay useful long after the project ends.
What if a library we depend on has no Python 3 version?
Either a maintained equivalent exists, or the small part you use is written again. In practice most code uses a fraction of the libraries it imports.
Which Python 3 version should we move to?
A recent one with several years of support left, that all your libraries already work with. Python 3 versions are retired on a schedule, so the choice is checked against the Python project release calendar at the time.
Is this urgent?
It depends on exposure. An internal script on an isolated server can wait a while. Anything that processes outside input or can be reached from the internet should be dealt with now.
Do you provide Python 2 developers in Sydney, Melbourne, Brisbane, Perth and Adelaide?
Yes. We are an Australian team and we take on Python 2 work for businesses in Sydney, Melbourne, Brisbane, Perth and Adelaide, and elsewhere in Australia. The work runs by video call and screen share, with secure access to a copy of your system. The service is the same in every city: code fixes and updates, migration to a modern technology stack, and ongoing maintenance and support.
How does this work from the United States, the United Kingdom or New Zealand?
By video call and screen share, at meeting times agreed to suit you, from discovery to handover. Confidentiality, who can reach your systems and where your data is held are agreed in writing before work starts.
What does it cost?
The assessment is a fixed-scope piece of work with an agreed fee. The estimate for anything after it comes from what the assessment finds, in stages, so you are not asked to commit to a whole project on a guess.
Sending your details…
You can stay on this page while we send it.
Tell us about your Python 2 code
What the code does, where it runs, whether it handles outside input, and what is forcing the question. Include your country so we can suggest meeting times. Please do not send production data.
Prefer a quick chat? Call 0425 531 127. We answer it ourselves, in Australia.
Kasun Wijayamanna, founderYou deal with Kasun from scope to delivery. No account managers and no offshore handoff.