havenstd06 / attestation22

Simple générateur d'attestation de déplacement dérogatoire à l'aide de fichier configuration.

Hi 👋, I'm Thomas

A passionate front/back end developer from France

• 🔭 I’m currently working on Social Link 👀

• 🌱 I’m currently learning Laravel, VueJS, React, Symfony

• 👨‍💻 All of my projects are available at https://thomas.drumont.dev

• 💬 Ask me about Laravel & VueJS

• 📫 How to reach me [email protected]

Connect with me:

Languages and Tools:

 

attestation22's Issues

Suggest to loosen the dependency on halo

Hi, your project Attestation22 requires "halo==0.0.30" in its dependency. After analyzing the source code, we found that the following versions of halo can also be suitable without affecting your project, i.e., halo 0.0.31. Therefore, we suggest to loosen the dependency on halo from "halo==0.0.30" to "halo>=0.0.30,<=0.0.31" to avoid any possible conflict for importing more packages or for downstream projects that may use Attestation22.

May I pull a request to further loosen the dependency on halo?

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 Attestation22 directly uses 4 APIs from package halo.

halo.halo.Halo.succeed, halo.halo.Halo.start, halo.halo.Halo.__init__, halo.halo.Halo.fail

Beginning from the 4 APIs above, 28 functions are then indirectly called, including 17 halo's internal APIs and 11 outsider APIs. The specific call graph is listed as follows (neglecting some repeated function occurrences).

[/Havenstd06/Attestation22]
+--halo.halo.Halo.succeed
|      +--halo.halo.Halo.stop_and_persist
|      |      +--halo._utils.decode_utf_8_text
|      |      |      +--codecs.decode
|      |      +--halo._utils.colored_frame
|      |      |      +--termcolor.colored
|      |      +--halo.halo.Halo.stop
|      |      |      +--halo.halo.Halo.clear
|      |      |      |      +--halo.halo.Halo._write
|      |      |      |      |      +--halo.halo.Halo._check_stream
|      |      |      +--halo.halo.Halo._show_cursor
|      |      |      |      +--halo.halo.Halo._check_stream
|      |      |      |      +--halo.cursor.show
|      |      |      |      |      +--halo.cursor._CursorInfo.__init__
|      |      |      |      |      +--ctypes.windll.kernel32.GetStdHandle
|      |      |      |      |      +--ctypes.windll.kernel32.GetConsoleCursorInfo
|      |      |      |      |      +--ctypes.windll.kernel32.SetConsoleCursorInfo
|      |      |      |      |      +--ctypes.byref
|      |      +--halo.halo.Halo._write
|      |      +--halo._utils.encode_utf_8_text
|      |      |      +--codecs.encode
+--halo.halo.Halo.start
|      +--halo.halo.Halo._check_stream
|      +--halo.halo.Halo._hide_cursor
|      |      +--halo.halo.Halo._check_stream
|      |      +--halo.cursor.hide
|      |      |      +--halo.cursor._CursorInfo.__init__
|      |      |      +--ctypes.windll.kernel32.GetStdHandle
|      |      |      +--ctypes.windll.kernel32.GetConsoleCursorInfo
|      |      |      +--ctypes.windll.kernel32.SetConsoleCursorInfo
|      |      |      +--ctypes.byref
|      +--threading.Event
|      +--threading.Thread
|      +--halo.halo.Halo._render_frame
|      |      +--halo.halo.Halo.clear
|      |      +--halo.halo.Halo.frame
|      |      |      +--halo._utils.colored_frame
|      |      |      +--halo.halo.Halo.text_frame
|      |      |      |      +--halo._utils.colored_frame
|      |      +--halo.halo.Halo._write
|      |      +--halo._utils.encode_utf_8_text
+--halo.halo.Halo.__init__
|      +--halo._utils.get_environment
|      |      +--IPython.get_ipython
|      +--halo.halo.Halo.stop
|      +--IPython.get_ipython
|      +--atexit.register
+--halo.halo.Halo.fail
|      +--halo.halo.Halo.stop_and_persist

We scan halo's versions and observe that during its evolution between any version from [0.0.31] and 0.0.30, 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.0.30(original) 0.0.31
[](no clear difference between the source codes of two versions)

As for other packages, the APIs of threading, IPython, atexit, codecs, termcolor and ctypes are called by halo 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 halo from "halo==0.0.30" to "halo>=0.0.30,<=0.0.31". This will improve the applicability of Attestation22 and reduce the possibility of any further dependency conflict with other projects.