Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

aio-libs / yarl Public

Notifications You must be signed in to change notification settings
Fork 169
Star 1.4k

Code
Issues 30
Pull requests 6
Discussions
Actions
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Security
Insights

proposal: use meson-python as build backend#1452

Closed

trim21 wants to merge 8 commits intoaio-libs:masteraio-libs/yarl:masterfrom trim21:use-mesontrim21/yarl:use-mesonCopy head branch name to clipboard

+312-957

Conversation Commits8 (8)Checks Files changed

Commits

Commits on Dec 7, 2024

use meson
trim21
committed
make test job always run without ext
trim21
committed
add changelog
trim21
committed
fix typo and yaml error
trim21
committed
revert some unnecessary change
trim21
committed
typo
trim21
committed
add meson feature flag cython-trace
trim21
committed
update cython so we do not need to patch generated file
trim21
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.