Skip to content

Instantly share code, notes, and snippets.

View Jeevesh8's full-sized avatar
🚀
Breathing. Thinking. Reflecting.

Jeevesh Juneja Jeevesh8

🚀
Breathing. Thinking. Reflecting.
View GitHub Profile
@pommedeterresautee
pommedeterresautee / Makefile
Last active August 19, 2024 13:27
Divide Hugging Face Transformers training times by 2 or more with dynamic padding and uniform length batching
# required by (\ SHELL COMMANDS \)
SHELL:=/bin/bash
VIRT_ENV_FOLDER = ~/.local/share/virtualenvs/xnli
SOURCE_VIRT_ENV = source $(VIRT_ENV_FOLDER)/bin/activate
.PHONY: train
train:
( \
@tasdikrahman
tasdikrahman / python_tests_dir_structure.md
Last active February 10, 2025 22:15
Typical Directory structure for python tests

A Typical directory structure for running tests using unittest

Ref : stackoverflow

The best solution in my opinion is to use the unittest [command line interface][1] which will add the directory to the sys.path so you don't have to (done in the TestLoader class).

For example for a directory structure like this:

new_project

├── antigravity.py