Skip to main content

Python script to export your LeetCode solutions

Project description

LeetCode Export

Python script and Docker image to export your LeetCode submissions.

If you find LeetCode Export helpful, please consider giving it a star ⭐️. Your support helps me gauge its usage and motivates further development.

📝 Table of Contents

⚠️ DISCLAIMER

The problems hosted on leetcode.com are intellectual propriety of LeetCode LLC unless specified otherwise. DO NOT UPLOAD THE DESCRIPTION OF LEETCODE PROBLEMS ON GITHUB OR ON ANY OTHER WEBSITE or you might receive ad DMCA Takedown notice.

Before using this script read the LeetCode Terms of Service.

⚙️ About

This script uses LeetCode REST and GraphQL APIs to download all your LeetCode submitted solutions.

Before running the script, make sure that python3 is installed in your system.

If you prefer, you can use the Docker image to download LeetCode submissions. For more information read the section Docker Image.

🏁 Getting started

Download leetcode-export

To use leetcode-export download it from pypi.org, pull the docker image, or clone this repository.

Download from pypi.org

Run pip install leetcode-export to install leetcode-export, you might have to use pip3 of your system. Then execute run the script leetcode-export, optionally supply the script arguments. For more information read the section script arguments.

Docker Image

Download the docker image from DockerHub:

docker pull nevermendel/leetcode-export

Download all your LeetCode submission in the current folder:

docker run -it -v $(pwd):/usr/app/out --rm nevermendel/leetcode-export

Clone the repository

Clone this repository:

git clone https://github.com/NeverMendel/leetcode-export

Install all the needed dependencies:

pip install -r requirements.txt

Install leetcode-export in your system or just execute it:

  • To install the script:

    pip install .
    
  • To execute the script without installing it:

    python -m leetcode_export --folder submissions
    

Login

leetcode-export requires a valid LeetCode account to download its submissions. Login to your LeetCode account by providing the cookies. To log in using cookies, get them from an existing session.

Steps required:

  • Login in to LeetCode in the web browser
  • Open the browser's Dev Tool
  • Click on the Network tab
  • Copy the cookie header that can be found under Request Headers in any leetcode.com request.

You can insert the cookie string that you have just copied in the interactive menu (recommended) or you can pass it as a program argument when lunching the script, like in the following example:

python leetcode-export --cookies {COOKIES}

Using the interactive menu is preferred because it will avoid storing cookies in the command history.

Script arguments

The script accepts the following arguments:

usage: leetcode-export [-h] [--cookies COOKIES] [--folder FOLDER]
                       [--problem-folder-name PROBLEM_FOLDER_NAME]
                       [--no-problem-statement]
                       [--problem-statement-filename PROBLEM_STATEMENT_FILENAME]
                       [--problem-statement-content PROBLEM_STATEMENT_CONTENT]
                       [--submission-filename SUBMISSION_FILENAME]
                       [--only-accepted] [--only-last-submission]
                       [--language LANGUAGE_UNPROCESSED] [-v] [-vv] [-V]

Export LeetCode submissions

options:
  -h, --help            show this help message and exit
  --cookies COOKIES     set LeetCode cookies
  --folder FOLDER       set output folder
  --problem-folder-name PROBLEM_FOLDER_NAME
                        problem folder name format
  --no-problem-statement
                        do not save problem statement
  --problem-statement-filename PROBLEM_STATEMENT_FILENAME
                        problem statement filename format
  --problem-statement-content PROBLEM_STATEMENT_CONTENT
                        problem statement content format
  --submission-filename SUBMISSION_FILENAME
                        submission filename format
  --only-accepted       save accepted submissions only
  --only-last-submission
                        only save the last submission for each programming language
  --language LANGUAGE_UNPROCESSED
                        save submissions for specified programming languages.
                        syntax: --language=<lang1>,<lang2>,...
                        languages: python, python3, c, cpp, csharp, java,
                                   kotlin, mysql, mssql, oraclesql, javascript,
                                   html, php, golang, scala, pythonml,
                                   rust, ruby, bash, swift
                        example: --language=python,cpp,java
  -v, --verbose         enable verbose logging details
  -vv, --extra-verbose  enable more verbose logging details
  -V, --version         show program's version number and exit

Problem template arguments

Problem statement filename template

To change the format of the problem statement filename provide a template as a string when executing the script.

python leetcode-export --problem-statement-filename PROBLEM_STATEMENT_FILENAME

The template can contain parameters that will later be replaced based on the LeetCode problem information. The available parameters are the following:

question_id: int
difficulty: str
stats: str
title: str
title_slug: str

Default problem statement filename template: ${question_id} - ${title_slug}.html

Problem statement content template

To change the format of the problem statement content provide a template as a string when executing the script.

python leetcode-export --problem-statement-content PROBLEM_STATEMENT_CONTENT

The template can contain parameters that will later be replaced based on the LeetCode problem information. The available parameters are the ones contained in problem statement filename template plus:

content: str

Default problem statement content template: <h1>${question_id} - ${title}</h1><h2>Difficulty: ${difficulty} - <a href="https://leetcode.com/problems/${title_slug}/">${title_slug}</a></h2>${content}

Submission filename template

To change the format of the submission filename, you can provide a template as a string when lunching the script.

python leetcode-export --submission-filename SUBMISSION_FILENAME

The template can contain parameters that will later be replaced based on the submission information. The available parameters are the following:

id: int
lang: str
time: str
timestamp: int
status_display: str
runtime: str
url: str
is_pending: str
title: str
memory: str
code: str
compare_result: str
title_slug: str
date_formatted: str
extension: str

Default submission filename template: ${date_formatted} - ${status_display} - runtime ${runtime} - memory ${memory}.${extension}

Special mentions

Thanks to skygragon for developing leetcode-cli, which I used as documentation for LeetCode APIs. The license of leetcode-cli is available here.

License

MIT License

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

leetcode-export-2.4.0.tar.gz (12.7 kB view details)

Uploaded Source

Built Distribution

leetcode_export-2.4.0-py3-none-any.whl (12.4 kB view details)

Uploaded Python 3

File details

Details for the file leetcode-export-2.4.0.tar.gz.

File metadata

  • Download URL: leetcode-export-2.4.0.tar.gz
  • Upload date:
  • Size: 12.7 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/5.0.0 CPython/3.10.12

File hashes

Hashes for leetcode-export-2.4.0.tar.gz
Algorithm Hash digest
SHA256 4facad7642ee4a64c12a8651e7538b8b242810491f115d823fbde26056b8d702
MD5 70369c31fe009ba1a94c4d4c77e43a99
BLAKE2b-256 4a845a9e1fff932bd89c8ed1dd47061f9b89e7eaca6ea39df5867ef5252f19c1

See more details on using hashes here.

File details

Details for the file leetcode_export-2.4.0-py3-none-any.whl.

File metadata

File hashes

Hashes for leetcode_export-2.4.0-py3-none-any.whl
Algorithm Hash digest
SHA256 d6cb7364eaf08d3cde14e290e311f0d95a3d4971f5508a60a12018ce9f29b3b5
MD5 c3dc6c48997f2ad585f03da81c8950e4
BLAKE2b-256 d528abb28bca5909779c56a8dc50e1908515c07f58341c26bc76b015058929c2

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page