<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>GitHub on Boyang Yue</title><link>http://blog.boyangyue.com/tags/github/</link><description>Recent content in GitHub on Boyang Yue</description><generator>Hugo</generator><language>en-us</language><copyright>A Good Year Ahead</copyright><lastBuildDate>Sat, 09 Aug 2025 10:00:00 +0900</lastBuildDate><atom:link href="http://blog.boyangyue.com/tags/github/index.xml" rel="self" type="application/rss+xml"/><item><title>Sharing a Confidential Python Library Without PyPI</title><link>http://blog.boyangyue.com/2025/08/sharing-a-confidential-python-library-without-pypi/</link><pubDate>Sat, 09 Aug 2025 10:00:00 +0900</pubDate><guid>http://blog.boyangyue.com/2025/08/sharing-a-confidential-python-library-without-pypi/</guid><description>&lt;p&gt;A quantitative trading system is rarely a single program. A backtester, a live execution engine, and a pile of research notebooks all need the same calculations: volatility scaling, a Sharpe ratio, a handful of instrument models. Copying those functions into each program means fixing every bug several times while the definitions slowly drift apart. A shared library gives them one implementation.&lt;/p&gt;
&lt;p&gt;Two constraints shape how this library should be distributed. The strategy code should not go to the public package index, and the Git host should not receive the implementation in readable form.&lt;/p&gt;</description></item></channel></rss>