declare dependency on sqlite when on py2.4 #728
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#728
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Zooko and I agreed to add a metadata dependency on one of the sqlite bindings
(used by Tahoe's backupdb feature). This means:
be importable
py2.4)
If
python -c "import sqlite3"
works, it must not attempt todownload+build pysqlite2 or sqlite3.
does not include an .egg-info file, and so setuptools might not believe
that it exists.
only when sys.version says 2.4, or try the import before adding the
dependency.
Python2.4 users will have an extra dependency to deal with, which may or may
not be satisfiable automatically. In exchange for this, we can remove the
--no-backupdb option from "tahoe backup". I think we might want to retain the
"here's advice for getting pysqlite" message in the ImportError handler,
because we'll be removing the alternative (running without sqlite and without
a backupdb).
Fixed by changeset:81b0e1382d9dd391. Oh, I guess I shouldn't close this ticket til I remove the
--no-backupdb
option.Fixed by changeset:8c18ac38a9b71d43.
See #745 for a possible problem with this change.