|Don't ask to ask, just ask|
Because you can.....
The implementation of "really useful things in a few lines of code using a 'baby' subset of the language" is left as an exercise for the demonstrator. ;)
Seriously, the best way to get someone into Perl isn't to tout its undeniable superiority to other alternatives. Doing that will raise the defenses of those who already feel their preference is the "one true language." The best way is to take some task you do every day, and solve it with Perl code while leveraging Perl's strengths and avoiding its more advanced capabilities. If you can do that using core modules, fantastic. If you need a CPAN module, your discussion will need to start by showing the simplicity with which CPAN modules can be installed.
Here's an outline:
As questions come up, use them as an opportunity to segue into topics like the CPAN smoke testers, Perl's committment to backward compatibility, Perl's leading role in advancing pattern matching techniques, concise syntax capable of rich expression, and so forth. Let those topics "come up" rather than forcing them upon Pythonistas. ;)
Throughout the discussion, suggest that you actually enjoy other languages too; that you might have done this using XYZ language, but that the module your using already did most of the work for you; that a shell script might have been adequate, but that Perl provides testing tools that helped you to gain a confidence that your code was correct, etc. When people raise opinions that they might have done this using Ruby, Python, C, etc., "Yes, that might be a nice approach also. I'm just demonstrating how simple it is with Perl. I suspect your implementation take a similar course regardless of the language."
This type of approach worked fairly well when I had to address a Unix user's group once, where we seemed to start off on the wrong foot as one trouble-maker wanted to just scoff at Perl. By the end, his disdain seemed to be more under control, and everyone else seemed to be genuinely interested.