The only correct answer to this is to spend some time to go (all the way) through the getting started guides for both.
Now, if you are sincerely planning to shape your career on this decision (and because you didn't clarify how you narrowed your decision down to Django and Rails), I'd recommend taking advantage of your current flexibility to get your hands dirty with a wider array of the options out there before investing copious amounts of time specializing on a single language/framework.
In your position, I'd take this time to actually go through the getting started guides for at least a couple of additional languages/frameworks (e.g., Symfony, Zend Framework, etc for PHP and Meteor, Express, etc for Node.js). This will allow you to find the stack that's a genuinely good fit based on your current skill level, opinions, experience, etc. This should not only give you confidence in your decision, but more importantly, it's sure to make the entire learning process much more enjoyable. Additionally, this approach would give you exposure to the documentation quality of the various projects in the process.
All tech arguments and language hate aside, specializing in any of the languages/frameworks mentioned will absolutely make you employable by a wide variety of companies in the current market, so personally I wouldn't stress over that aspect of it very much. That is, unless you're only planning to entertain local opportunities and live in a region which lacks tech diversity. In that case, your local job market should probably be a more important factor in your decision.
Now, if you are sincerely planning to shape your career on this decision (and because you didn't clarify how you narrowed your decision down to Django and Rails), I'd recommend taking advantage of your current flexibility to get your hands dirty with a wider array of the options out there before investing copious amounts of time specializing on a single language/framework.
In your position, I'd take this time to actually go through the getting started guides for at least a couple of additional languages/frameworks (e.g., Symfony, Zend Framework, etc for PHP and Meteor, Express, etc for Node.js). This will allow you to find the stack that's a genuinely good fit based on your current skill level, opinions, experience, etc. This should not only give you confidence in your decision, but more importantly, it's sure to make the entire learning process much more enjoyable. Additionally, this approach would give you exposure to the documentation quality of the various projects in the process.
All tech arguments and language hate aside, specializing in any of the languages/frameworks mentioned will absolutely make you employable by a wide variety of companies in the current market, so personally I wouldn't stress over that aspect of it very much. That is, unless you're only planning to entertain local opportunities and live in a region which lacks tech diversity. In that case, your local job market should probably be a more important factor in your decision.