Yayyyyy #mypackage I made myself merch and also some little presents for my friends yayyy
August 19, 2026 at 10:31 PM
Yayyyyy #mypackage I made myself merch and also some little presents for my friends yayyy
How to add a console script to your #Python package with uv 🚀
1️⃣ Init a package: uv init --lib mypackage
2️⃣ Add function to module
3️⃣ Define [project.scripts] in pyproject.toml
4️⃣ Build: uv build
5️⃣ Install + run: uv pip install -e . && uv run hello
Detailed steps 👇
1️⃣ Init a package: uv init --lib mypackage
2️⃣ Add function to module
3️⃣ Define [project.scripts] in pyproject.toml
4️⃣ Build: uv build
5️⃣ Install + run: uv pip install -e . && uv run hello
Detailed steps 👇
![1️⃣ Init a package
$ uv init --lib mypackage
$ tree mypackage
mypackage
├── README.md
├── pyproject.toml
└── src
└── mypackage
├── __init__.py
└── py.typed
3 directories, 4 files
2️⃣ Add a module + function
$ cat src/mypackage/script.py
def hello():
print("Hello, world!")
3️⃣ Add console script
# pyproject.toml
...
...
[project.scripts]
hello = "mypackage.script:hello"
4️⃣ Build it 📈
$ uv build
5️⃣ Test it out 🎉
$ uv pip install -e .
# linked here now -> .venv/bin/hello
$ uv run hello
Hello, world!](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:uay2bzai5qhnwqcqz7ivsvzg/bafkreigz2fg2sctnqok4cnjwuvg5weuce44ep2ixcsmia7p7stc3cb6te4)
February 24, 2025 at 1:12 PM
How to add a console script to your #Python package with uv 🚀
1️⃣ Init a package: uv init --lib mypackage
2️⃣ Add function to module
3️⃣ Define [project.scripts] in pyproject.toml
4️⃣ Build: uv build
5️⃣ Install + run: uv pip install -e . && uv run hello
Detailed steps 👇
1️⃣ Init a package: uv init --lib mypackage
2️⃣ Add function to module
3️⃣ Define [project.scripts] in pyproject.toml
4️⃣ Build: uv build
5️⃣ Install + run: uv pip install -e . && uv run hello
Detailed steps 👇
i open #mypackage and loose sweetart crumbs and powder fall out onto the table. all yellow
July 30, 2026 at 4:47 AM
i open #mypackage and loose sweetart crumbs and powder fall out onto the table. all yellow
I feel like a dog waiting for the mailman the way I want my package to show up #myPackage
March 12, 2025 at 4:34 PM
I feel like a dog waiting for the mailman the way I want my package to show up #myPackage
With SE-530 done (and now accepted), I turns my attention back to a long-standing annoyance with package settings. The pitch thread is a little hard to follow due to age, but I think I have now settled on something that could work.
Default Package Swift Settings
It's really common to see Package.swift files that apply the Swift language settings to all targets. Here's a common approach. // swift-tools-version: 5.9 import PackageDescription let package = Package( name: "MyPackage", products: [ .library(name: "MyPackage", targets: ["MyPackage"]), ], dependencies: [], targets: [ .target(name: "MyPackage"), ] ) let swiftSettings: [SwiftSetting] = [ .enableExperimentalFeature("StrictConcurrency"), .enableUpcomingFeature("DisableOutwardActorIn...
forums.swift.org
May 14, 2026 at 7:39 PM
With SE-530 done (and now accepted), I turns my attention back to a long-standing annoyance with package settings. The pitch thread is a little hard to follow due to age, but I think I have now settled on something that could work.
Day 1: usethis - Project Setup Automation 🎯
The usethis package is your best friend for automating repetitive package development tasks! 🤖
💡 Pro Tip: Set up your global options once with usethis::edit_r_profile() to add your name, email, and preferred license.
The usethis package is your best friend for automating repetitive package development tasks! 🤖
💡 Pro Tip: Set up your global options once with usethis::edit_r_profile() to add your name, email, and preferred license.
December 1, 2025 at 11:01 AM
Day 1: usethis - Project Setup Automation 🎯
The usethis package is your best friend for automating repetitive package development tasks! 🤖
💡 Pro Tip: Set up your global options once with usethis::edit_r_profile() to add your name, email, and preferred license.
The usethis package is your best friend for automating repetitive package development tasks! 🤖
💡 Pro Tip: Set up your global options once with usethis::edit_r_profile() to add your name, email, and preferred license.
I OPENED #MYPACKAGE FROM VAR AND HE WAS NOT FUCKEN JOKING ABOUT #THISTHREAD ,,, I AM STILL CACKLING SO HARD. an abundance of yellow sweetarts mailed across the skies!!!!! 😭💛🍬 ty @sevarix.bsky.social for blorbos and specifically lemon candy
September 2, 2026 at 12:50 AM
I OPENED #MYPACKAGE FROM VAR AND HE WAS NOT FUCKEN JOKING ABOUT #THISTHREAD ,,, I AM STILL CACKLING SO HARD. an abundance of yellow sweetarts mailed across the skies!!!!! 😭💛🍬 ty @sevarix.bsky.social for blorbos and specifically lemon candy
essentially any time you run "pip install mypackage" you're creating a problem. the only question is whose problem will it end up being
January 14, 2025 at 10:50 PM
essentially any time you run "pip install mypackage" you're creating a problem. the only question is whose problem will it end up being
#neovim Development News
The 0.12 version makes `:packadd` interact with cached value of 'runtimepath' in order to not retrigger its parsing.
This makes `:packadd` visibly faster to the benefit of users and plugin managers like `vim.pack`.
PR:
- github.com/neovim/neovi...
The 0.12 version makes `:packadd` interact with cached value of 'runtimepath' in order to not retrigger its parsing.
This makes `:packadd` visibly faster to the benefit of users and plugin managers like `vim.pack`.
PR:
- github.com/neovim/neovi...
perf(runtime): hardware accelerated "packadd opt_package" by bfredl · Pull Request #37722 · neovim/neovim
looking into addressing #37586
when doing packadd mypackage up to two exact paths are added to &rtp. Instead of recalculating runtime_search_path from scratch, we can "just" splice th...
github.com
June 8, 2026 at 4:57 PM
#neovim Development News
The 0.12 version makes `:packadd` interact with cached value of 'runtimepath' in order to not retrigger its parsing.
This makes `:packadd` visibly faster to the benefit of users and plugin managers like `vim.pack`.
PR:
- github.com/neovim/neovi...
The 0.12 version makes `:packadd` interact with cached value of 'runtimepath' in order to not retrigger its parsing.
This makes `:packadd` visibly faster to the benefit of users and plugin managers like `vim.pack`.
PR:
- github.com/neovim/neovi...
my package has allegedly been delivered but there is nothing at my door and i have to wait for my mom to get home to check our mail #mypackage
April 10, 2026 at 8:24 PM
my package has allegedly been delivered but there is nothing at my door and i have to wait for my mom to get home to check our mail #mypackage
Day 11: NEWS.md and Semantic Versioning
Keep users informed about package changes.
Create NEWS.md:
usethis::use_news_md()
Pro Tip: Follow semantic versioning: MAJOR.MINOR.PATCH for breaking.feature.bugfix changes.
#rstats #RPackageAdvent2025
Keep users informed about package changes.
Create NEWS.md:
usethis::use_news_md()
Pro Tip: Follow semantic versioning: MAJOR.MINOR.PATCH for breaking.feature.bugfix changes.
#rstats #RPackageAdvent2025
December 11, 2025 at 11:01 AM
Day 11: NEWS.md and Semantic Versioning
Keep users informed about package changes.
Create NEWS.md:
usethis::use_news_md()
Pro Tip: Follow semantic versioning: MAJOR.MINOR.PATCH for breaking.feature.bugfix changes.
#rstats #RPackageAdvent2025
Keep users informed about package changes.
Create NEWS.md:
usethis::use_news_md()
Pro Tip: Follow semantic versioning: MAJOR.MINOR.PATCH for breaking.feature.bugfix changes.
#rstats #RPackageAdvent2025
You can install from the file system instead of a registry to test in another project.
e.g. instead of 1.0.0
use: file://../../myPackage
Where myPackage/package.json exists
e.g. instead of 1.0.0
use: file://../../myPackage
Where myPackage/package.json exists
March 12, 2025 at 1:22 AM
You can install from the file system instead of a registry to test in another project.
e.g. instead of 1.0.0
use: file://../../myPackage
Where myPackage/package.json exists
e.g. instead of 1.0.0
use: file://../../myPackage
Where myPackage/package.json exists
Fun fact. I used to be sponsored by BN3TH before they did the name change from MyPackage to BN3TH.
October 29, 2025 at 1:45 AM
Fun fact. I used to be sponsored by BN3TH before they did the name change from MyPackage to BN3TH.
4/ Key Functions You'll Use Daily:
usethis::create_package("~/mypackage") # Perfect structure
usethis::use_mit_license() # Legal protection
usethis::use_github_action("check-standard") # Auto-testing
usethis::use_testthat(3) # Testing framework
usethis::create_package("~/mypackage") # Perfect structure
usethis::use_mit_license() # Legal protection
usethis::use_github_action("check-standard") # Auto-testing
usethis::use_testthat(3) # Testing framework
December 1, 2025 at 11:01 AM
4/ Key Functions You'll Use Daily:
usethis::create_package("~/mypackage") # Perfect structure
usethis::use_mit_license() # Legal protection
usethis::use_github_action("check-standard") # Auto-testing
usethis::use_testthat(3) # Testing framework
usethis::create_package("~/mypackage") # Perfect structure
usethis::use_mit_license() # Legal protection
usethis::use_github_action("check-standard") # Auto-testing
usethis::use_testthat(3) # Testing framework
And then
conda install MyPackage
(Fill in your package)
Environments are really helpful bc you can start with a clean slate, which makes debugging easier!
docs.anaconda.com/working-with...
conda install MyPackage
(Fill in your package)
Environments are really helpful bc you can start with a clean slate, which makes debugging easier!
docs.anaconda.com/working-with...
Installing conda packages — Anaconda documentation
docs.anaconda.com
December 12, 2024 at 12:58 PM
And then
conda install MyPackage
(Fill in your package)
Environments are really helpful bc you can start with a clean slate, which makes debugging easier!
docs.anaconda.com/working-with...
conda install MyPackage
(Fill in your package)
Environments are really helpful bc you can start with a clean slate, which makes debugging easier!
docs.anaconda.com/working-with...
honestly there should be a MyPackage app that I can sign into with some sort of proof of tenancy so that I can just see all packages addressed to my house since everything gets dropped in the paper bin and if I don’t know I might put the bin out with a pkg still in
June 5, 2025 at 11:17 AM
honestly there should be a MyPackage app that I can sign into with some sort of proof of tenancy so that I can just see all packages addressed to my house since everything gets dropped in the paper bin and if I don’t know I might put the bin out with a pkg still in
3/ NEWS.md Structure:
markdown# mypackage 1.2.0
## New features
* Added `new_function()` (#15)
## Bug fixes
* Fixed missing values (#12)
## Breaking changes
* Renamed parameter
markdown# mypackage 1.2.0
## New features
* Added `new_function()` (#15)
## Bug fixes
* Fixed missing values (#12)
## Breaking changes
* Renamed parameter
NEWS.md
December 11, 2025 at 11:01 AM
3/ NEWS.md Structure:
markdown# mypackage 1.2.0
## New features
* Added `new_function()` (#15)
## Bug fixes
* Fixed missing values (#12)
## Breaking changes
* Renamed parameter
markdown# mypackage 1.2.0
## New features
* Added `new_function()` (#15)
## Bug fixes
* Fixed missing values (#12)
## Breaking changes
* Renamed parameter
Okay.... just.... just to be sure, there is no way to teach nix shell or other nix commands to know about overlays if i use flakes? So i can do nix shell nixpkgs#MyPackage and it will work?
And what maybe even more important, there is no way to do it in sane, understandable way?
And what maybe even more important, there is no way to do it in sane, understandable way?
November 23, 2025 at 4:00 PM
Okay.... just.... just to be sure, there is no way to teach nix shell or other nix commands to know about overlays if i use flakes? So i can do nix shell nixpkgs#MyPackage and it will work?
And what maybe even more important, there is no way to do it in sane, understandable way?
And what maybe even more important, there is no way to do it in sane, understandable way?
June 20, 2026 at 1:37 AM
📦 devicaro16/microservices-common 1.0.1
Package Files Utils Microservices Courses
🔗 https://github.com/DevIcaro16/laravel-mypackage-microservice-common
Package Files Utils Microservices Courses
🔗 https://github.com/DevIcaro16/laravel-mypackage-microservice-common
August 24, 2025 at 5:59 PM
📦 devicaro16/microservices-common 1.0.1
Package Files Utils Microservices Courses
🔗 https://github.com/DevIcaro16/laravel-mypackage-microservice-common
Package Files Utils Microservices Courses
🔗 https://github.com/DevIcaro16/laravel-mypackage-microservice-common
📦 devicaro16/microservices-common 1.0.0
Package Files Utils Microservices Courses
🔗 https://github.com/DevIcaro16/laravel-mypackage-microservice-common
Package Files Utils Microservices Courses
🔗 https://github.com/DevIcaro16/laravel-mypackage-microservice-common
August 24, 2025 at 4:58 PM
📦 devicaro16/microservices-common 1.0.0
Package Files Utils Microservices Courses
🔗 https://github.com/DevIcaro16/laravel-mypackage-microservice-common
Package Files Utils Microservices Courses
🔗 https://github.com/DevIcaro16/laravel-mypackage-microservice-common