Computer Engineering != CS. Computer engineering is a part of EE. Here's a single example of the price difference you can see on your first job: A friend of mine and I interviewed at the same company for similar positions. He was finishing his BS in EE and I was finishing my MS in EE. My offer was 18k more than his and was for a higher-level engineering classification. Given that the company average for raises was 3.5%, he would have been making around 4.5k more than when he started in 2 years with the company and wouldn't have been bumped up to engineer 2. Or he could have spent two years to get his MS, made 18k more, and started at the "engineer 2" level. He chose to get his MS.

Most places I looked treated a MS like a BS + 3 years experience. They stated this on the job postings. But my market/industry may be different than others.

Here are some reasons to do your MS now instead of later:
1.) I would have a hard time going back to school after a long break. When you get a job, sure you're at your office for 40 hours a week but you don't have homework, class projects, or finals. Your free time is your time. Some days I like coming home, shutting down my EE side, and playing with my son. And you don't know what will happen during your break - will you get married, buy a house, or have a kid? Each one of those things is a major drain on time, energy, and money.
2.) You like your field and want to learn. There's nothing wrong with expanding your skills.
3.) You don't want to completely enter adulthood yet. Grad school is a nice way to postpone real responsibilities.

But, DO NOT DO A CLASSWORK ONLY MS. If you don't have a research project that ends in a thesis, I will put your resume on the same stack as those who only have a BS. That's the biggest thing. If you can't handle the research, just get a job. Non-thesis MS degrees are for people who are working while getting their degree. If you're young and just going to school, there's no excuse for not doing research. Getting on a funded project can be hard, though.

From what I've seen, Python 3.0 is not supported by a good number of Python packages whereas Python 2.6 is which would make the "no Python 3.0 support" a minor issue for me. Python 3.0 is also not shipping as the default interpreter for Fedora, Ubunutu, or openSuSE yet so it won't really affect basic users for a while. I have also seen benchmarks (but I don't have references, so I welcome contradictions and corrections) that show that 3.0 is considerably slower than 2.6 so if the speed of Python is an issue to people they shouldn't be using 3.0 (I take issue with people who grumble about Python's execution speed anyway - if speed is that important stick to C/C++). If you have a good amount of existing Python apps that work under 2.5 getting them to work in 2.6 isn't hard. Moving to 3.0 is a much bigger step, especially if you relied on built-in modules that are either different now or removed.

I see the "no windows support" as a much bigger negative - if one of the biggest strengths of Python is cross-platform support and you need your programs to work on both Windows and Linux (as I do) that's going to be a problem and I'm only half interested (because half of my apps never leave Linux).