diff options
author | 2022-07-15 01:31:29 +0200 | |
---|---|---|
committer | 2022-07-15 01:31:29 +0200 | |
commit | 0d86b4035fbd5ec65620e7680189828971155edb (patch) | |
tree | 76083b7348c5db448f29acf66ddec07e93842fe3 /pydis_site | |
parent | Reword new codejam rule exception clause (diff) |
Add note about approval for non-WebSocket communication
Diffstat (limited to 'pydis_site')
-rw-r--r-- | pydis_site/templates/events/pages/code-jams/9/rules.html | 2 |
1 files changed, 2 insertions, 0 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 cabdd8f4..263e84e1 100644 --- a/pydis_site/templates/events/pages/code-jams/9/rules.html +++ b/pydis_site/templates/events/pages/code-jams/9/rules.html @@ -20,6 +20,8 @@ For example, you may use PostgreSQL as a database but not its `NOTIFY` command. Working with subprocesses (through stdin/stdout or <code>multiprocessing.Pool()</code>/<code>concurrent.futures.ProcessPoolExecutor()</code>) is also allowed. </p> + + <p>If you're interested in utilizing a particular non-WebSocket method of communication, reach out to the Events Team for discussion and approval</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> <li> |