image-embedding-api's People
image-embedding-api's Issues
Suggest to loosen the dependency on uvicorn
Hi, your project image-embedding-api requires "uvicorn==0.13.4" in its dependency. After analyzing the source code, we found that the following versions of uvicorn can also be suitable without affecting your project, i.e., uvicorn 0.13.0, 0.13.1, 0.13.2, 0.13.3. Therefore, we suggest to loosen the dependency on uvicorn from "uvicorn==0.13.4" to "uvicorn>=0.13.0,<=0.13.4" to avoid any possible conflict for importing more packages or for downstream projects that may use image-embedding-api.
May I pull a request to further loosen the dependency on uvicorn?
By the way, could you please tell us whether such dependency analysis may be potentially helpful for maintaining dependencies easier during your development?
We also give our detailed analysis as follows for your reference:
Your project image-embedding-api directly uses 1 APIs from package uvicorn.
uvicorn.main.run
Beginning from the 1 APIs above, 37 functions are then indirectly called, including 19 uvicorn's internal APIs and 18 outsider APIs. The specific call graph is listed as follows (neglecting some repeated function occurrences).
[/FadeoN/image-embedding-api]
+--uvicorn.main.run
| +--uvicorn.config.Config.__init__
| | +--uvicorn.config.Config.configure_logging
| | | +--logging.config.dictConfig
| | | +--json.load
| | | +--logging.config.fileConfig
| | | +--yaml.safe_load
| | +--os.getcwd
| | +--dotenv.load_dotenv
| | +--os.environ.get
| +--uvicorn.server.Server.__init__
| | +--uvicorn.server.ServerState.__init__
| +--sys.exit
| +--uvicorn.config.Config.bind_socket
| | +--socket.socket
| | +--sys.exit
| | +--click.style
| +--uvicorn.supervisors.watchgodreload.WatchGodReload.__init__
| | +--uvicorn.supervisors.basereload.BaseReload.__init__
| | | +--threading.Event
| | | +--os.getpid
| | +--pathlib.Path
| | +--uvicorn.supervisors.watchgodreload.CustomWatcher.__init__
| | | +--re.compile
| | | +--watchgod.DefaultWatcher.__init__
| +--uvicorn.supervisors.basereload.BaseReload.run
| | +--uvicorn.supervisors.basereload.BaseReload.startup
| | | +--click.style
| | | +--signal.signal
| | | +--uvicorn.subprocess.get_subprocess
| | | | +--sys.stdin.fileno
| | +--uvicorn.supervisors.basereload.BaseReload.should_restart
| | +--uvicorn.supervisors.basereload.BaseReload.restart
| | | +--uvicorn.subprocess.get_subprocess
| | +--uvicorn.supervisors.basereload.BaseReload.shutdown
| | | +--click.style
| +--uvicorn.supervisors.multiprocess.Multiprocess.__init__
| | +--threading.Event
| | +--os.getpid
| +--uvicorn.supervisors.multiprocess.Multiprocess.run
| | +--uvicorn.supervisors.multiprocess.Multiprocess.startup
| | | +--click.style
| | | +--signal.signal
| | | +--uvicorn.subprocess.get_subprocess
| | +--uvicorn.supervisors.multiprocess.Multiprocess.shutdown
| | | +--click.style
| +--uvicorn.server.Server.run
| | +--asyncio.get_event_loop
We scan uvicorn's versions and observe that during its evolution between any version from [0.13.0, 0.13.1, 0.13.2, 0.13.3] and 0.13.4, the changing functions (diffs being listed below) have none intersection with any function or API we mentioned above (either directly or indirectly called by this project).
diff: 0.13.4(original) 0.13.0
['uvicorn.protocols.http.httptools_impl.RequestResponseCycle', 'uvicorn.logging.AccessFormatter.get_client_addr', 'uvicorn.protocols.http.h11_impl.RequestResponseCycle', 'uvicorn.server.Server', 'uvicorn.protocols.websockets.websockets_impl.WebSocketProtocol', 'uvicorn.protocols.http.httptools_impl.HttpToolsProtocol', 'uvicorn.logging.AccessFormatter.formatMessage', 'uvicorn.logging.AccessFormatter.get_full_path', 'uvicorn.protocols.http.httptools_impl.HttpToolsProtocol.data_received', 'uvicorn.protocols.websockets.wsproto_impl.WSProtocol', 'uvicorn.workers.UvicornWorker.init_signals', 'uvicorn.logging.AccessFormatter.get_status_code', 'uvicorn.protocols.websockets.websockets_impl.WebSocketProtocol.__init__', 'uvicorn.config.Config', 'uvicorn.config.Config.load', 'uvicorn.protocols.websockets.websockets_impl.WebSocketProtocol.send_500_response', 'uvicorn.workers.UvicornWorker', 'uvicorn.logging.AccessFormatter', 'uvicorn.logging.AccessFormatter.get_path', 'uvicorn.server.Server._log_started_message', 'uvicorn.protocols.http.h11_impl.H11Protocol', 'uvicorn.protocols.http.h11_impl.H11Protocol.handle_events', 'uvicorn.middleware.wsgi.build_environ']
diff: 0.13.4(original) 0.13.1
['uvicorn.protocols.http.httptools_impl.RequestResponseCycle', 'uvicorn.protocols.websockets.websockets_impl.WebSocketProtocol', 'uvicorn.protocols.http.httptools_impl.HttpToolsProtocol', 'uvicorn.workers.UvicornWorker.init_signals', 'uvicorn.config.Config', 'uvicorn.protocols.websockets.websockets_impl.WebSocketProtocol.__init__', 'uvicorn.protocols.http.h11_impl.RequestResponseCycle', 'uvicorn.config.Config.load', 'uvicorn.protocols.http.h11_impl.H11Protocol.handle_events', 'uvicorn.protocols.websockets.websockets_impl.WebSocketProtocol.send_500_response', 'uvicorn.workers.UvicornWorker', 'uvicorn.middleware.wsgi.build_environ', 'uvicorn.server.Server', 'uvicorn.protocols.http.httptools_impl.HttpToolsProtocol.data_received', 'uvicorn.server.Server._log_started_message', 'uvicorn.protocols.http.h11_impl.H11Protocol']
diff: 0.13.4(original) 0.13.2
['uvicorn.protocols.http.httptools_impl.RequestResponseCycle', 'uvicorn.protocols.websockets.websockets_impl.WebSocketProtocol', 'uvicorn.workers.UvicornWorker.init_signals', 'uvicorn.config.Config', 'uvicorn.protocols.websockets.websockets_impl.WebSocketProtocol.__init__', 'uvicorn.protocols.http.h11_impl.RequestResponseCycle', 'uvicorn.config.Config.load', 'uvicorn.protocols.websockets.websockets_impl.WebSocketProtocol.send_500_response', 'uvicorn.workers.UvicornWorker', 'uvicorn.middleware.wsgi.build_environ', 'uvicorn.server.Server', 'uvicorn.server.Server._log_started_message']
diff: 0.13.4(original) 0.13.3
['uvicorn.protocols.http.httptools_impl.RequestResponseCycle', 'uvicorn.protocols.websockets.websockets_impl.WebSocketProtocol', 'uvicorn.protocols.websockets.websockets_impl.WebSocketProtocol.__init__', 'uvicorn.protocols.http.h11_impl.RequestResponseCycle', 'uvicorn.middleware.wsgi.build_environ', 'uvicorn.server.Server', 'uvicorn.server.Server._log_started_message']
As for other packages, the APIs of sys, os, dotenv, socket, click, pathlib, threading, asyncio, logging, json, yaml, re, watchgod and signal are called by uvicorn in the call graph and the dependencies on these packages also stay the same in our suggested versions, thus avoiding any outside conflict.
Therefore, we believe that it is quite safe to loose your dependency on uvicorn from "uvicorn==0.13.4" to "uvicorn>=0.13.0,<=0.13.4". This will improve the applicability of image-embedding-api and reduce the possibility of any further dependency conflict with other projects.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ๐๐๐
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google โค๏ธ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.