1.0.0

[qcoumes]

• Le tgz de base est trop grand #2 Seems to have fix this one as a side effect

• Sandbox is slow #3 Not really slow anymore

• Exception when launching sandbox #18 Fixed by removing name from container

• Installation de Java sur la sandbox  #19 Both pl-java and pl-javac has been installed

• Network Breakout #20 Container cannot access internet anymore

• Environment created by graders should be kept and used #21 Grader now use most recent env

• --reload is now enforced in manage.py

• EnvView.get() now return every environments with the given ID

• Added EnvView.head() to check if an environment exists on the sandbox

Every test of PL - master is working on it, but has to be tested on pl-preprod before being merge on master, especially if it survive a night.

[qcoumes]

This version has now been on PL-preprod for a week and (afaik) without any bug.

If 2 people could review (correctly) the code so we can merge it on master on deploy it as soon as possible on PL.

@Pavell94000 @mciissee @nimdanor

[qcoumes]

#24 should be merge on this branch before merging it.

[nimdanor]

Why did you change:
with lock:
to
lock.aquire() lock.release()
??

Another question where is the documentation for the capabilities of the sandbox containers ?

why is the language of the sandbox en_US ?

[qcoumes]

We actually had to merge #24 to 1.0.0, as i said above, before merging this branch on master.
So we are now going to merge #24 on 1.0.0 and then merge 1.0.0 to master once more.

Why did you change:
with lock:
to
lock.aquire() lock.release()
??

To avoid over-indentation of the code on big block (I kept with statement for 1/2 lignes statements)

Another question where is the documentation for the capabilities of the sandbox containers ?

The container limitations are set at production (in config.py) and can vary between servers.

why is the language of the sandbox en_US ?

I never bother changing it, should I set it to fr_FR ?