This might be something for you:

https://www.railstutorial.org/book

Sounds like click-bait at first but it's written by a guy with years of SaaS and VC experience.

  the chassis of the servers was opened and an unknown USB device was plugged in only 30-60 seconds before the connection was broken.

In which country did this happen?

As an European I expected the US/EU governments would keep their hands of Tor because dissidents use it in countries where US/EU want regime change.

The USG is not a monolithic entity. The State Department loves TOR, for the reasons you list, while Justice hates it. The Justice Department does not need State approval to get warrants and take down servers, nor do they need State approval to work with their foreign partners to do the same.

One of my favorite examples of this: http://articles.latimes.com/1989-06-07/news/mn-1711_1_rocky-...

The US/EU governments run their own nodes. Why WOULDN'T they take down third parties that aren't willing to give them the access they need to sniff traffic? Their support of dissidents in other countries doesn't require private nodes to exist.

Which nodes are gov run?

Nederlands

$ whois 77.95.229.11

It's not less possible, you're just more ignorant of it than America is.

I'm sure even the Netherlands has some kind of mechanism in place to allow this if a sufficiently powerful court order is in place.

Feel free to drop the 'even' in that sentence. Just say the magic words 'child pornography' and the judge will go and install that bug himself. Tor has a very bad reputation in The Netherlands, I think just saying it's a Tor node might be enough reason for a judge to sign off on an eaves-dropping warrant.

Hold off on the conclusion-jumping = 'possibly consistent with X' is a long way from 'proof of X'.

OT:

I know that Django 1.6+ can be used with Python 3.4 but is Django 1.7.1 written in Python 2.7 or 3.4?

Both.

It is possible, and not too difficult in fact, to write a single codebase that runs under both Python 2 and Python 3. Which is what Django has done. The same code runs the same under 2.7 or 3.3 or 3.4.

Thanks for the reply.

Are there any guidelines or "best practices" for writing code for both 2.7 and 3.4?

http://python-future.org/compatible_idioms.html

This is a pretty comprehensive guide. It does rely on the future lib, which is a wrapper around six and a few others to make it easier, but you can also just write your own minimal lib for things that need to have:

    if py2:
         pass # Py2 specific line here
    else:
         pass # Py3 stuff here

I think Django has chosen the approach of having their own minimal compatibility layer, iirc.

Here is Django's documentation, including notes on the compatibility stuff we ship:

https://docs.djangoproject.com/en/1.7/topics/python3/