mirror of
https://github.com/UpsilonNumworks/Upsilon.git
synced 2026-05-09 08:25:44 +02:00
[GH-ISSUE #17] [python] Add a escher-like module #4
Labels
No labels
bug
duplicate
easy
enhancement
enhancement
fixed
fixed
good first issue
hard
invalid
pull-request
wontfix
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Upsilon#4
Loading…
Add table
Add a link
Reference in a new issue
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?
Originally created by @FaustinM on GitHub (Sep 18, 2021).
Original GitHub issue: https://github.com/UpsilonNumworks/Upsilon/issues/17
Card link : https://github.com/Lauryy06/Upsilon/projects/1#card-68577430
I open this issue for discussion about the Escher module
@FaustinM commented on GitHub (Sep 18, 2021):
I think we can create a branch "python-escher", because a lot of the work is not very easy, and we need to create little tasks (like Agile method), so if we have a branch where we can pr without make some trouble in the master branch it's a cool thing. When the module is ready for production, we can merge the branch to upsilon-dev :)
What do you think about that method?
@Lauryy06 commented on GitHub (Sep 23, 2021):
I have created a branch called upsilon-dev-escher-mpy. I'm not going to work on it right now, but if you want to start adding the module, you can.
@lolocomotive commented on GitHub (Oct 1, 2021):
Is anyone working on this?
@FaustinM commented on GitHub (Oct 2, 2021):
No but i think we need to divide the issue in smaller issues
@Yaya-Cout commented on GitHub (Feb 28, 2022):
What do you want in the Escher module ?