Ah. Hmm, while the Crossbow releases do include wheels, they don't include the source (the source link there is for the CI scripts, not Arrow itself). I'm not sure if there's anything else that packages the Python sources.
On Thu, Jul 7, 2022, at 11:10, Li Jin wrote: > Thanks David - I am currently using [1]. A slight issue is that I don't > have the corresponding sdist for "pyarrow" so I'm wondering if there is an > easy way for me to grab matching [1] source and pyarrow source tarball. > > Not a big issue, I can create the pyarrow dist from [1] > > On Thu, Jul 7, 2022 at 11:03 AM David Li <lidav...@apache.org> wrote: > >> Does it work to just use the HEAD [1]? >> >> Otherwise, the nightly CI jobs do generate releases, but I don't think >> there's much of a guarantee around the naming/format being stable [2]. >> >> I'm not sure if there's an explicit/dedicated "nightly source release" >> (I'm not aware of one), or how that would differ significantly from just >> using HEAD (unless there's particular breakage you're concerned won't be >> caught by the regular CI?) >> >> [1]: https://github.com/apache/arrow/archive/refs/heads/master.tar.gz >> [2]: https://github.com/ursacomputing/crossbow/releases >> >> On Thu, Jul 7, 2022, at 10:39, Li Jin wrote: >> > Hello, >> > >> > I wonder if we have nightly source tarball published somewhere? >> > >> > Li >>
