aisk commented on code in PR #8053:
URL: https://github.com/apache/paimon/pull/8053#discussion_r3459626533


##########
paimon-python/pyproject.toml:
##########
@@ -0,0 +1,129 @@
+################################################################################
+#  Licensed to the Apache Software Foundation (ASF) under one
+#  or more contributor license agreements.  See the NOTICE file
+#  distributed with this work for additional information
+#  regarding copyright ownership.  The ASF licenses this file
+#  to you under the Apache License, Version 2.0 (the
+#  "License"); you may not use this file except in compliance
+#  with the License.  You may obtain a copy of the License at
+#
+#      http://www.apache.org/licenses/LICENSE-2.0
+#
+#  Unless required by applicable law or agreed to in writing, software
+#  distributed under the License is distributed on an "AS IS" BASIS,
+#  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+#  See the License for the specific language governing permissions and
+#  limitations under the License.
+################################################################################
+
+[build-system]
+requires = [
+    "setuptools>=61",
+    "wheel",
+]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "pypaimon"
+version = "1.5.dev"

Review Comment:
   Hi, I'm not sure how we currently use nightly builds. AFAIK, Python users 
can install PyPaimon directly from Git, for example:
   
   `pip install 
"git+https://github.com/apache/paimon.git#subdirectory=paimon-python"`
   
   If we want to publish nightly or snapshot builds, we can tag the related 
commit and let users install that tag with `pip install 
"git+https://github.com/apache/paimon.git@<tag>#subdirectory=paimon-python"`.
   
   In principle, nightly or snapshot builds should have a tag or at least a 
clear revision. So unless an existing publishing workflow depends on the 
dynamic version, I think we can remove this behavior.
   



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to