Building on our experience with pkglite for R, +we identified several limitations and unmet needs:
+We made a few key design changes from pkglite for R to implement the above goals:
+.pkgliteignore configuration file to control packing scope,
+ following the gitignore standard.Let’s walk through a typical pkglite for Python workflow.
+Single directory:
+from pkglite import use_pkglite, pack, unpack
+
+dirs = ["path/to/pkg"]
+txt = "path/to/pkg.txt"
+use_pkglite(dirs)
+pack(dirs, output_file=txt)
+unpack(txt, output_dir="path/to/output")
+Multiple directories:
+from pkglite import use_pkglite, pack, unpack
+
+dirs = ["path/to/pkg1", "path/to/pkg2"]
+txt = "path/to/pkgs.txt"
+use_pkglite(dirs)
+pack(dirs, output_file=txt)
+unpack(txt, output_dir="path/to/output")
+Single directory:
+# Create a .pkgliteignore file to exclude files from packing
+pkglite use path/to/pkg
+
+# Pack a single directory into a text file
+pkglite pack path/to/pkg -o path/to/pkg.txt
+
+# Unpack the text file into a directory
+pkglite unpack path/to/pkg.txt -o path/to/output
+Multiple directories:
+# Create a .pkgliteignore file to exclude files from packing
+pkglite use path/to/pkg1 path/to/pkg2
+
+# Pack multiple directories into a text file
+pkglite pack path/to/pkg1 path/to/pkg2 -o path/to/pkgs.txt
+
+# Unpack the text file into multiple directories under `output/`
+pkglite unpack path/to/pkgs.txt -o path/to/output
+Run pkglite --help, pkglite use --help, pkglite pack --help, or
+pkglite unpack --help for more information about the available
+subcommands and options.
U|KcPD}1}75g2?D|d0xIox
zJw!~aA?Fe#2}ubOA~8Xd6d55|9G2)zl!Se~97tb=0TqohFnp00Uo}BEU`PH&M3bNt
zH3KI}2t~mC;}96`|DM$^ER4SxmKUSq6~ggg;dn_rr`