aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGravatar Bluenix <[email protected]>2022-07-15 01:26:07 +0200
committerGravatar GitHub <[email protected]>2022-07-15 01:26:07 +0200
commit974c554da608c0e6c98fbee4beb153b305819c00 (patch)
treef0bce0d0023b75aadd75e1775b79c7ab889e386c
parentRemove accidental stray parenthesis in new codejam rule (diff)
Reword new codejam rule exception clause
Co-authored-by: wookie184 <[email protected]>
-rw-r--r--pydis_site/templates/events/pages/code-jams/9/rules.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/pydis_site/templates/events/pages/code-jams/9/rules.html b/pydis_site/templates/events/pages/code-jams/9/rules.html
index e7a85c70..cabdd8f4 100644
--- a/pydis_site/templates/events/pages/code-jams/9/rules.html
+++ b/pydis_site/templates/events/pages/code-jams/9/rules.html
@@ -16,9 +16,9 @@
<p><strong>Your solution must only communicate through WebSockets</strong>. Any communication between the client and server (or any two server workers), must utilize WebSockets.</p>
<p>
- Exceptions to this rule are made for resources such as databases and files, albeit excluding usage other than for storage.
+ An exception to this rule is that communication with databases and files is allowed for accessing resources or for storage purposes.
For example, you may use PostgreSQL as a database but not its `NOTIFY` command.
- Lastly, working with subprocesses (through stdin/stdout or <code>multiprocessing.Pool()</code>/<code>concurrent.futures.ProcessPoolExecutor()</code>) is also exempted from this rule.
+ Working with subprocesses (through stdin/stdout or <code>multiprocessing.Pool()</code>/<code>concurrent.futures.ProcessPoolExecutor()</code>) is also allowed.
</p>
</li>
<li><p>Your solution should be platform agnostic. For example, if you use filepaths in your submission, use <code>pathlib</code> to create platform agnostic Path objects instead of hardcoding the paths.</p></li>