# Equivalent of Python's Inline script metadata (PEP 723) in Julia

**URL:** <https://discourse.julialang.org/t/equivalent-of-pythons-inline-script-metadata-pep-723-in-julia/127980>\
**Category:** Package Management\
**Tags:** question\
**Created:** [April 11, 2025, 2:10pm UTC](https://discourse.julialang.org/t/equivalent-of-pythons-inline-script-metadata-pep-723-in-julia/127980 "2025-04-11T14:10:20Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![goerz](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/goerz/32/3269_2.png) [@goerz](https://discourse.julialang.org/u/goerz)\
**Post date:** [April 11, 2025, 2:23pm UTC](https://discourse.julialang.org/t/equivalent-of-pythons-inline-script-metadata-pep-723-in-julia/127980/2 "2025-04-11T14:23:00Z")

</div>

Yes, you can just add `Pkg` commands at the top of your script:

```julia
using Pkg
Pkg.activate(temp=true) # maybe point this to a more permanent project location
Pkg.add("Requests") # these are not Julia packages ...
Pkg.add("Rich") # ... but you get the point.

```

See the [documentation of `Pkg.add`](https://pkgdocs.julialang.org/v1/api/#Pkg.add) for how to pin specific versions and other details.

---

_[View the full topic](https://discourse.julialang.org/t/equivalent-of-pythons-inline-script-metadata-pep-723-in-julia/127980)._