Question 1

How do I run a Python script with pier?

Accepted Answer

Add a script with a shebang like #!/usr/bin/env python3 in the command field of your TOML config, as shown in the shebang example. Pier will create a temp file and execute it using the specified interpreter.

Question 2

pier vs using bash aliases for script management?

Accepted Answer

Pier adds metadata tagging and a centralized catalog, making scripts searchable and organizable with descriptions, whereas bash aliases are limited to simple command shortcuts without categorization. However, aliases are built-in and faster for very basic needs.

Question 3

How to migrate my pier config after a breaking change?

Accepted Answer

For upgrades like to v0.1.4, manually update the TOML file by changing syntax, such as replacing `default_interpreter` with `[default] interpreter`, as documented in the recent breaking changes section.

Question 4

Can pier handle scripts with external dependencies?

Accepted Answer

Pier itself doesn't manage dependencies; it relies on the system's installed interpreters and tools. For scripts with complex dependencies, you need to ensure the environment is set up separately, which can be a limitation.

Question 5

Is pier good for sharing scripts with a team?

Accepted Answer

It can be used for shared repositories via TOML config files, but lacks built-in collaboration features like access control or real-time sync. Teams might need to pair it with version control systems like Git.

Question 6

What happens if my pier script has a shebang error?

Accepted Answer

Pier will attempt to execute the script as-is, but if the shebang points to a missing interpreter, it may fail. You can set a default interpreter in the config or ensure the interpreter is available in the PATH.

pier

What is pier?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions