func2stream 0.0.0.dev20240519__tar.gz → 0.0.1__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {func2stream-0.0.0.dev20240519 → func2stream-0.0.1}/PKG-INFO +18 -3
- {func2stream-0.0.0.dev20240519 → func2stream-0.0.1}/README.md +17 -2
- {func2stream-0.0.0.dev20240519 → func2stream-0.0.1}/func2stream.egg-info/PKG-INFO +18 -3
- {func2stream-0.0.0.dev20240519 → func2stream-0.0.1}/setup.py +8 -3
- {func2stream-0.0.0.dev20240519 → func2stream-0.0.1}/LICENSE +0 -0
- {func2stream-0.0.0.dev20240519 → func2stream-0.0.1}/func2stream.egg-info/SOURCES.txt +0 -0
- {func2stream-0.0.0.dev20240519 → func2stream-0.0.1}/func2stream.egg-info/dependency_links.txt +0 -0
- {func2stream-0.0.0.dev20240519 → func2stream-0.0.1}/func2stream.egg-info/requires.txt +0 -0
- {func2stream-0.0.0.dev20240519 → func2stream-0.0.1}/func2stream.egg-info/top_level.txt +0 -0
- {func2stream-0.0.0.dev20240519 → func2stream-0.0.1}/pyproject.toml +0 -0
- {func2stream-0.0.0.dev20240519 → func2stream-0.0.1}/setup.cfg +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.1
|
|
2
2
|
Name: func2stream
|
|
3
|
-
Version: 0.0.
|
|
3
|
+
Version: 0.0.1
|
|
4
4
|
Summary: Effortlessly transform functions into asynchronous elements for building high-performance pipelines
|
|
5
5
|
Home-page: https://github.com/BICHENG/func2stream
|
|
6
6
|
Author: BI CHENG
|
|
@@ -26,8 +26,23 @@ Inspired by Gstreamer's pipeline architecture, `func2stream` provides a clean an
|
|
|
26
26
|
|
|
27
27
|
`func2stream` is currently in early development and is being actively worked on. While it shows promise, it is not yet recommended for production use. The following areas are being prioritized for improvement:
|
|
28
28
|
|
|
29
|
-
|
|
30
|
-
|
|
29
|
+
- [ ] 🎯 Strive towards a decorator-free solution
|
|
30
|
+
|
|
31
|
+
- [x] Implement automatic conversion of SISO functions to Elements and connect them in `Pipeline([fn1, fn2...])`
|
|
32
|
+
|
|
33
|
+
*Decorators are aesthetically unpleasing and may not provide a foolproof solution. As other projects have attempted and abandoned.*
|
|
34
|
+
|
|
35
|
+
- [ ] Eliminate the need for decorators in MIMO functions
|
|
36
|
+
- [ ] Introduce implicit Context construction using AST parsing
|
|
37
|
+
- [ ] Simplify the process for users while maintaining necessary control and flexibility
|
|
38
|
+
|
|
39
|
+
- [ ] 🧩 Implement implicit Context
|
|
40
|
+
|
|
41
|
+
- [ ] Extend the automation to MIMO functions
|
|
42
|
+
- [ ] Use AST to parse function input and output parameters
|
|
43
|
+
- [ ] Automatically convert parameters into variable keys
|
|
44
|
+
- [ ] Enable users to build Context mode by ensuring consistent naming in function parameter lists and return statements
|
|
45
|
+
- [ ] Simplify the process for users while maintaining necessary control and flexibility
|
|
31
46
|
|
|
32
47
|
## Key Features
|
|
33
48
|
|
|
@@ -8,8 +8,23 @@ Inspired by Gstreamer's pipeline architecture, `func2stream` provides a clean an
|
|
|
8
8
|
|
|
9
9
|
`func2stream` is currently in early development and is being actively worked on. While it shows promise, it is not yet recommended for production use. The following areas are being prioritized for improvement:
|
|
10
10
|
|
|
11
|
-
|
|
12
|
-
|
|
11
|
+
- [ ] 🎯 Strive towards a decorator-free solution
|
|
12
|
+
|
|
13
|
+
- [x] Implement automatic conversion of SISO functions to Elements and connect them in `Pipeline([fn1, fn2...])`
|
|
14
|
+
|
|
15
|
+
*Decorators are aesthetically unpleasing and may not provide a foolproof solution. As other projects have attempted and abandoned.*
|
|
16
|
+
|
|
17
|
+
- [ ] Eliminate the need for decorators in MIMO functions
|
|
18
|
+
- [ ] Introduce implicit Context construction using AST parsing
|
|
19
|
+
- [ ] Simplify the process for users while maintaining necessary control and flexibility
|
|
20
|
+
|
|
21
|
+
- [ ] 🧩 Implement implicit Context
|
|
22
|
+
|
|
23
|
+
- [ ] Extend the automation to MIMO functions
|
|
24
|
+
- [ ] Use AST to parse function input and output parameters
|
|
25
|
+
- [ ] Automatically convert parameters into variable keys
|
|
26
|
+
- [ ] Enable users to build Context mode by ensuring consistent naming in function parameter lists and return statements
|
|
27
|
+
- [ ] Simplify the process for users while maintaining necessary control and flexibility
|
|
13
28
|
|
|
14
29
|
## Key Features
|
|
15
30
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.1
|
|
2
2
|
Name: func2stream
|
|
3
|
-
Version: 0.0.
|
|
3
|
+
Version: 0.0.1
|
|
4
4
|
Summary: Effortlessly transform functions into asynchronous elements for building high-performance pipelines
|
|
5
5
|
Home-page: https://github.com/BICHENG/func2stream
|
|
6
6
|
Author: BI CHENG
|
|
@@ -26,8 +26,23 @@ Inspired by Gstreamer's pipeline architecture, `func2stream` provides a clean an
|
|
|
26
26
|
|
|
27
27
|
`func2stream` is currently in early development and is being actively worked on. While it shows promise, it is not yet recommended for production use. The following areas are being prioritized for improvement:
|
|
28
28
|
|
|
29
|
-
|
|
30
|
-
|
|
29
|
+
- [ ] 🎯 Strive towards a decorator-free solution
|
|
30
|
+
|
|
31
|
+
- [x] Implement automatic conversion of SISO functions to Elements and connect them in `Pipeline([fn1, fn2...])`
|
|
32
|
+
|
|
33
|
+
*Decorators are aesthetically unpleasing and may not provide a foolproof solution. As other projects have attempted and abandoned.*
|
|
34
|
+
|
|
35
|
+
- [ ] Eliminate the need for decorators in MIMO functions
|
|
36
|
+
- [ ] Introduce implicit Context construction using AST parsing
|
|
37
|
+
- [ ] Simplify the process for users while maintaining necessary control and flexibility
|
|
38
|
+
|
|
39
|
+
- [ ] 🧩 Implement implicit Context
|
|
40
|
+
|
|
41
|
+
- [ ] Extend the automation to MIMO functions
|
|
42
|
+
- [ ] Use AST to parse function input and output parameters
|
|
43
|
+
- [ ] Automatically convert parameters into variable keys
|
|
44
|
+
- [ ] Enable users to build Context mode by ensuring consistent naming in function parameter lists and return statements
|
|
45
|
+
- [ ] Simplify the process for users while maintaining necessary control and flexibility
|
|
31
46
|
|
|
32
47
|
## Key Features
|
|
33
48
|
|
|
@@ -2,9 +2,14 @@ import os
|
|
|
2
2
|
from setuptools import setup, find_packages
|
|
3
3
|
from datetime import datetime
|
|
4
4
|
|
|
5
|
-
date_suffix = datetime.now().strftime("%
|
|
6
|
-
base_version = '0.0.
|
|
7
|
-
|
|
5
|
+
date_suffix = datetime.now().strftime("%y%m%d%H%M%S")
|
|
6
|
+
base_version = '0.0.1'
|
|
7
|
+
|
|
8
|
+
# Determine the version based on environment variable
|
|
9
|
+
if os.getenv('RELEASE_VERSION'):
|
|
10
|
+
full_version = base_version
|
|
11
|
+
else:
|
|
12
|
+
full_version = f"{base_version}.dev{date_suffix}"
|
|
8
13
|
|
|
9
14
|
setup(
|
|
10
15
|
name='func2stream',
|
|
File without changes
|
|
File without changes
|
{func2stream-0.0.0.dev20240519 → func2stream-0.0.1}/func2stream.egg-info/dependency_links.txt
RENAMED
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|