> But I take it that you're also not expecting that I would need to manually > install the python driver?
Correct. You shouldn't be installing the driver to run the cqllib tests. > Also don't see the python driver as an explicit dependency in build.xml, > only as something not to delete in the "realclean" target. Should it have > been downloaded as a transitive dep of something else? It used to be listed in .build/build-resolver.xml Because of CASSANDRA-16599 it is now in lib/ again. While it is there under the tag in git, it is not found in the source release artefact. The build script removes it when creating the artefacts, see build.xml:1170. We are still ironing out the wrinkles here, sorry. A lot of this was done in a hurry for the last release, and a few fixes have followed on from this change. The ASF release policy has been reported to now be accurate. It states that "A source release SHOULD not contain compiled code." Presuming that python dependencies are not compiled, and it only says SHOULD, it seems to make sense that we include the zip in the source release artefact again. Although the same logic applies to all the jar files, so it's a big IDK 🤷🏻♀️ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
