reala10n / cptk Goto Github PK

Checking if the tests exceeded the time limit is easy. However, checking for memory usage is a bit more difficult

Users may want to commit and push their solutions. This is why we want to integrate git with cptk and provide the following options:

• Automatically commit after submitting code to a single problem
• Automatically push after submitting code to a single problem
• Automatically commit before the end of a session (multiple problems)
• Automatically push before the end of a session
• Edit and customize commit messages

Examples of formats for commit messages:

Solved {number} problems
{'\n'.join(f''{p.name} - {p.url}" for p in problems)}

Solved {numberSolved}, Resubmitted {numberResubmitted}

etc.

We can analyze the websites that the user visits, what problems he spends most of his time on, and what language he prefers!
This information can be interesting and in my opinion, gives cptk some extra points when compared to other competitive programming toolkits.
Although it sounds good, this feature may be too much for the simpler users, and we might want to consider adding it as an extra and optional dependency.

Clone a problem into a new temporary directory. In this directory, run the preprocessor and other third-party plugin hooks, and only then copy the directory into the final destination (and raise warnings if some files are overwritten).

cool

This issue proposes a new plugin to cptk that will interact with the code CLI and will extend the built-in feature-set of cptk.

Key features

• Option to automatically open a file after cloning a problem (with pre-defined cursor location using code -g
• Show test expected vs output using code -d

http://www.usaco.org

https://acm.timus.ru/

Currently, tests with large input and outputs will get loaded into memory and will take a very long time to compare.
We should use the output stream to compare the output of the execution to the expected output file online

Allow website plugins to make requests using a requests session managed and provided by the cptk core.
For login information, add support for a keys.cptk.yaml file that will contain information that is managed by website plugins.
The website plugin will define the model of their section in the keys.cptk.yaml file.
The session used by cptk will be stored locally (probably as a pickle, perhaps an encrypted pickle).

If the user renames the folder structure of already existing problems, cptk should be smart and create new problems with the same relative path in the new, renamed subdirectory.
For example, if there is a problem from cses.fi located inside introductory-problems/trailing-zeros and the user decides to rename the directory to something like intro/trailing-zeros, other problems from the "Introductory Problems" section in the problem set should be cloned into the new intro subdirectory instead of the old introductory-problems one.

www.codechef.com

The extension will communicate with the cptk command line and will provide a nice GUI for longer commands.

The project configuration file, project.cptk.yaml, should allow a specification of a list of template paths.
If multiple templates are provided, the first template in the list will be the default one, but the user will be able to overwrite the default choice with other choice names when cloning or creating a new problem using the clone and create subcommands, using a click option.

When using the clone subcommand the resulting path is printed with inconsistent slashes, for example:

PS> cptk clone https://cses.fi/problemset/task/1068
D:\Projects\tomer-cptk\cses-fi/cses-problem-set/weird-algorithm/

https://open.kattis.com/

Currently, the traceback for unexpected errors lacks information and in my option, the default python one is better.
I would like to print out the default traceback (or something that is very similar to it) with an additional bold line that states that an unexpected error has occurred.

This solution is great for Python developers and users that aren't familiar with Python:

• Python developers that are using cptk will be familiar with the default Python traceback and will be able to figure out what is the problem if they want to.
• Other users will see the bold statement which states that an unexpected error has occurred, and then they will be able to report the issue if they want to.

The error message should also print some information about the current Python version, and information about the version of cptk.

Logging into the websites again and again every time can be quite annoying. To avoid it, we can:

• Save the browser session, and load the same one every time cptk lanches.
• Use the default session of the user, stored in
• Store login credentials manually and automatically login for the user