tbar4 commented on PR #1100:
URL: 
https://github.com/apache/datafusion-ballista/pull/1100#issuecomment-2453242893

   @milenkovicm @andygrove  I can't create tasks, so I am just cutting new 
feature requests. 
   
   As for the following:
   
   > can we make standalone optional feature in python as well?
   
   The pyo3 docs weren't very clear on how to do this, but from what I can tell 
looking at polars as an example, looks like the package their structs into a 
module than define the module as a feature. I think this is an option for a 
future task, but since we are still in pre-alpha for python ballista I think 
just getting more of it built out first, then organizing the code into features 
will be ideal for a true 0.0.1 release. I will continue to look into this, but 
will probably focus more on the scheduler/executor deployment from python as a 
higher priority. 
   
   > does py3o/python support trait extensions (like in rust), something like
   
   I am not the biggest python user (actively avoided in Spark and preferred 
Scala), but I think this should be possible. Again, will probably put this 
lower priority than the executor/scheduler, but still important.
   
   I am up for discussion on prioritization of tasks. We can knock it out here, 
or I am pretty sure I can call into the meeting on Wednesday and we can discuss 
then.


-- 
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: github-unsubscr...@datafusion.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org
For additional commands, e-mail: github-h...@datafusion.apache.org

Reply via email to