You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While lamin load and ln.setup.load() should keep writing ~/.lamin/current_instance.env, I think that ln.connect() should not persist anything to disk (should not write .env files).
The text was updated successfully, but these errors were encountered:
Can you also add the ability to pass None, @Koncopd
Meaning we enable the same behavior as in R:
import lamindb as ln
ln.connect() # <-- this populates ln.setup.settings.instance for just this user session from `current_instance.env`; it errors if this file doesn't exit
This is relevant if people prefer to work with auto-connect switched off.
falexwolf
changed the title
ln.connect should not write any .env filesln.connect should not write any .env files and accept NoneJan 10, 2025
falexwolf
changed the title
ln.connect should not write any .env files and accept None
🚸 ln.connect() should not write any .env files and accept NoneJan 10, 2025
While
lamin load
andln.setup.load()
should keep writing~/.lamin/current_instance.env
, I think thatln.connect()
should not persist anything to disk (should not write.env
files).The text was updated successfully, but these errors were encountered: