----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/52884/#review152706 -----------------------------------------------------------
Ship it! We do build sdists but we don't upload them to PyPI. We did once in the past and we could make that apart of our release cycle (like creating binary packages). - Zameer Manji On Oct. 14, 2016, 8:03 a.m., David McLaughlin wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/52884/ > ----------------------------------------------------------- > > (Updated Oct. 14, 2016, 8:03 a.m.) > > > Review request for Aurora, Joshua Cohen, Giulio Eulisse, and Zameer Manji. > > > Repository: aurora > > > Description > ------- > > Document how to create a custom pex that you can use to put > deployment-specific customizations. > > I think the dependency section needs some work, but I'm not an expert on > pants and how it resolves dependencies. Currently we just have the forked > sources in the same repo, so we can point directly to the OSS build target. I > don't think we upload the aurora CLI to PyPi? So it's mostly an exercise left > to the user to make that dependency available in their repo. Can anyone help > fill out that section? > > > Diffs > ----- > > docs/development/client.md 079c4712885a615716c3ecbd9a48581fc1bcee14 > > Diff: https://reviews.apache.org/r/52884/diff/ > > > Testing > ------- > > > Thanks, > > David McLaughlin > >
