Yes, running pip on requiremenst.txt is the standard way. I also know that currently requirements.txt does not contain the actual dependencies (which can be changed, of course). I was just thinking about whether a new user would have a problem with using pip this way, having already manually downloaded and unpacked the Leo distro.
On Saturday, January 20, 2024 at 5:14:11 PM UTC-5 Edward K. Ream wrote: > On Sat, Jan 20, 2024 at 3:23 PM Thomas Passin <tbp1...@gmail.com> wrote: > >> I think that would be all right, although sometimes I have trouble >> finding the release files when I want to get an app from GitHub. My main >> concern would be how to make it painless for a new user to get the >> dependencies installed. >> > > There is an easy answer. See #3767 > <https://github.com/leo-editor/leo-editor/issues/3767>: > (requirements.txt). > > Leo already has a requirements.txt file, but it delegates everything to > setup.py. > > The remaining question is whether Leo needs setup.py at all. > > Edward > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/c5d866d3-83d3-45c6-9c8e-4c5f185a463fn%40googlegroups.com.
