Might I suggest the best of both worlds given your situation. Use the Python as "pseudocode" to write the algorithms in Perl. You keep your expertise in the language domain while benefiting from the work in another (and benefiting the Perl community in general with the new tools).
Perl really can make this kind of thing easy and having sample code before to redraft/translate can sometimes even lead to better code as you won't be boxed in or painted into a corner the way so many code bases end up, you'll just be guided.
Compare your project to the Perl effort to port Python's WSGI. And don't stop there! There is more to be learned from others. Why not mix in Ruby's Rack? We arrive at Plack. And it was a pretty short trip.
Caveat: if your team was reticent to hit up the CPAN for help in the past, trying to keep this kind of thing together on your own might not be a good match for your culture. "Modern" has more to do with approach than the language and if you're rooted in old-school Perl it might be harder to change that than to change languages.