Bug: sqlite3 does not depend on nltk and regex
See original GitHub issueIn 0.21.1 deployment, when running import sqlite3
in the REPL it would load nltk and regex which is wrong.
It looks like for sqlite3 depends
and imports
fields are switched, between the repodata.json and the meta.yaml
but then other packages seem to be fine.
This is serious enough to probably warrant a 0.21.2 release, as it adds an extra MB for apps that load sqlite3.
Version which reproduces: 0.20.0, 0.21.1 (and probably those in between) Version which don’t reproduce: dev
cc @ryanking13
Issue Analytics
- State:
- Created a year ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Problem with regexp python and sqlite - Stack Overflow
I try to check a string with a pattern using a regex with python on a sqlite database. I have problem ...
Read more >Use REGEXP with SQLITE? (regular expressions) : r/godot
I'm programming a game that relies heavily on a database I've built. The issue is - my current method (GDSQLITE) not allowing the...
Read more >Problem with packaged Python libraries - Alfred forum
Hi! I've put together a workflow to interact with Obsidian. It relies heavily on some Python libraries like NLTK and Gensim, and I've...
Read more >SQL Language Expressions - SQLite
The REGEXP operator is a special syntax for the regexp() user function. No regexp() user function is defined by default and so use...
Read more >Python sqlite and regex. - Bytes
Hi, I'd like to use regular expressions in sqlite query, I using apsw module but it doesn't work...Can you help me ? My...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Also mkpkg should substitute
-
for_
in the imports field since this often is enough to give a correct result.We should add a new key
top-level
in meta.yaml or something similar and should not usetest/imports
for calculating the top level import name. It’s so easy to make a mistake…