eons - pypi Package Compare versions

Comparing version 3.0.12 to 3.1.0

PKG-INFO

 Metadata-Version: 2.1
 Name: eons
-Version: 3.0.12
+Version: 3.1.0
 Summary: Eons Python Framework
@@ -15,8 +15,8 @@ Home-page: https://github.com/eons-dev/eons.lib
 Description-Content-Type: text/markdown
+Requires-Dist: pyyaml
+Requires-Dist: eot
+Requires-Dist: requests
+Requires-Dist: requests_futures
 Requires-Dist: jsonpickle
 Requires-Dist: tqdm
-Requires-Dist: requests_futures
-Requires-Dist: requests
-Requires-Dist: eot
-Requires-Dist: pyyaml
 
@@ -33,3 +33,3 @@ # Eons Python Framework
 
-Eons provides an easy plug-and-play style of development by melding the myriad Python packages we all love with our own custom syntax. We aim to provide you with something that is familiar when you want it to be, and powerful when you need it to be.
+Eons provides an easy plug-and-play style of development by mElderlanging the myriad Python packages we all love with our own custom syntax. We aim to provide you with something that is familiar when you want it to be, and powerful when you need it to be.
 
@@ -66,12 +66,12 @@ The most condensed form of our syntax is as follows:
 
-This language style derives from the [Eons Language of Development](https://github.com/develop-biology/language.development) (ELD). The only real features missing, besides some nicer character choices (e.g. use of `{}` for Execution Blocks) are Space Autofill, and the ability to define functions, classes, and Functors in Parameter Blocks (i.e. `()`). So, for now, you're restricted to just lambdas or breaking your larger logic out into a separate Functor. 
+This language style derives from the [Eons Language of Development for Entropic Reduction](https://github.com/elderlang/elderlang) (Elderlang). The only real features missing, besides some nicer character choices (e.g. use of `{}` for Execution Blocks) are Space Autofill, and the ability to define functions, classes, and Functors in Parameter Blocks (i.e. `()`). So, for now, you're restricted to just lambdas or breaking your larger logic out into a separate Functor. 
 
 The main differences between the Kind syntax and the Eons Language of Development are:
 * The `@eons.kind` decorator is used to declare a Type Block.
-* `this` is used instead of `$` (or `self` in Python).
-* `caller` is used instead of `$$`.
+* `this` is used instead of `./` (or `self` in Python).
+* `epidef` is used instead of `../`.
 * Spatial Separation is big endian, rather than how domains are named (i.e. LSB..TLD).
 * Sequences are built by `eons.Flow()`s (still under development).
 * Python STILL does not have multiline comments >:(
-* Python has both dictionaries and lists, vs just Containers in ELD
+* Python has both dictionaries and lists, vs just Containers in Elderlang
 * `def` is required to start a Parameter Block & `:` is required to start an Execution Block, both of which must always happen in that order (and be preceded by a Type Block).
@@ -89,8 +89,8 @@ * Convenient type casting is not fully implemented in Kind.
 
-To answer this question, ELD introduces the keyword `$$`. In Kind, we simply call this `caller`.
+To answer this question, Elderlang introduces the keyword `./`. In Kind, we simply call this `epidef`.
 
-So, you can use `caller.someMember` to share access across Functors composed by the same class, and `this.someMember` to access the Functor's own members.
+So, you can use `epidef.someMember` to share access across Functors composed by the same class, and `this.someMember` to access the Functor's own members.
 
 ### Access Control
-There is no true access control in Python. So, implementing it via Biology has been slow going. However, for now, you can use something akin to ELD's `public(...)` Functor to make defining method injection easier.
+There is no true access control in Python. So, implementing it via Biology has been slow going. However, for now, you can use something akin to Elderlang's `public(...)` Functor to make defining method injection easier.
 
@@ -97,0 +97,0 @@ Instead of saying:

pkg/eons.egg-info/PKG-INFO

 Metadata-Version: 2.1
 Name: eons
-Version: 3.0.12
+Version: 3.1.0
 Summary: Eons Python Framework
@@ -15,8 +15,8 @@ Home-page: https://github.com/eons-dev/eons.lib
 Description-Content-Type: text/markdown
+Requires-Dist: pyyaml
+Requires-Dist: eot
+Requires-Dist: requests
+Requires-Dist: requests_futures
 Requires-Dist: jsonpickle
 Requires-Dist: tqdm
-Requires-Dist: requests_futures
-Requires-Dist: requests
-Requires-Dist: eot
-Requires-Dist: pyyaml
 
@@ -33,3 +33,3 @@ # Eons Python Framework
 
-Eons provides an easy plug-and-play style of development by melding the myriad Python packages we all love with our own custom syntax. We aim to provide you with something that is familiar when you want it to be, and powerful when you need it to be.
+Eons provides an easy plug-and-play style of development by mElderlanging the myriad Python packages we all love with our own custom syntax. We aim to provide you with something that is familiar when you want it to be, and powerful when you need it to be.
 
@@ -66,12 +66,12 @@ The most condensed form of our syntax is as follows:
 
-This language style derives from the [Eons Language of Development](https://github.com/develop-biology/language.development) (ELD). The only real features missing, besides some nicer character choices (e.g. use of `{}` for Execution Blocks) are Space Autofill, and the ability to define functions, classes, and Functors in Parameter Blocks (i.e. `()`). So, for now, you're restricted to just lambdas or breaking your larger logic out into a separate Functor. 
+This language style derives from the [Eons Language of Development for Entropic Reduction](https://github.com/elderlang/elderlang) (Elderlang). The only real features missing, besides some nicer character choices (e.g. use of `{}` for Execution Blocks) are Space Autofill, and the ability to define functions, classes, and Functors in Parameter Blocks (i.e. `()`). So, for now, you're restricted to just lambdas or breaking your larger logic out into a separate Functor. 
 
 The main differences between the Kind syntax and the Eons Language of Development are:
 * The `@eons.kind` decorator is used to declare a Type Block.
-* `this` is used instead of `$` (or `self` in Python).
-* `caller` is used instead of `$$`.
+* `this` is used instead of `./` (or `self` in Python).
+* `epidef` is used instead of `../`.
 * Spatial Separation is big endian, rather than how domains are named (i.e. LSB..TLD).
 * Sequences are built by `eons.Flow()`s (still under development).
 * Python STILL does not have multiline comments >:(
-* Python has both dictionaries and lists, vs just Containers in ELD
+* Python has both dictionaries and lists, vs just Containers in Elderlang
 * `def` is required to start a Parameter Block & `:` is required to start an Execution Block, both of which must always happen in that order (and be preceded by a Type Block).
@@ -89,8 +89,8 @@ * Convenient type casting is not fully implemented in Kind.
 
-To answer this question, ELD introduces the keyword `$$`. In Kind, we simply call this `caller`.
+To answer this question, Elderlang introduces the keyword `./`. In Kind, we simply call this `epidef`.
 
-So, you can use `caller.someMember` to share access across Functors composed by the same class, and `this.someMember` to access the Functor's own members.
+So, you can use `epidef.someMember` to share access across Functors composed by the same class, and `this.someMember` to access the Functor's own members.
 
 ### Access Control
-There is no true access control in Python. So, implementing it via Biology has been slow going. However, for now, you can use something akin to ELD's `public(...)` Functor to make defining method injection easier.
+There is no true access control in Python. So, implementing it via Biology has been slow going. However, for now, you can use something akin to Elderlang's `public(...)` Functor to make defining method injection easier.
 
@@ -97,0 +97,0 @@ Instead of saying:

pkg/eons.egg-info/requires.txt

@@ -0,6 +1,6 @@
+pyyaml
+eot
+requests
+requests_futures
 jsonpickle
 tqdm
-requests_futures
-requests
-eot
-pyyaml

pkg/eons/method/External.py

 import logging
 import eons
 
-# External Methods replace a function with a Functor retrieved from outside the caller's module.
+# External Methods replace a function with a Functor retrieved from outside the epidef's module.
 # The function's name should match the name of the Functor that will replace it.
@@ -23,3 +23,3 @@ # The function need not take any arguments beyond *this.
 		try:
-			this.functor = eons.ExecutorTracker.GetLatest().GetRegistered(this.functorName, this.type, namespace = this.caller.name)
+			this.functor = eons.ExecutorTracker.GetLatest().GetRegistered(this.functorName, this.type, namespace = this.epidef.name)
 		except:
@@ -46,3 +46,3 @@ this.functor = eons.ExecutorTracker.GetLatest().GetRegistered(this.functorName, this.type)
 		})
-		this.functor.caller = this.caller
+		this.functor.epidef = this.epidef
 		return kwargs
@@ -49,0 +49,0 @@

README.md

@@ -11,3 +11,3 @@ # Eons Python Framework
 
-Eons provides an easy plug-and-play style of development by melding the myriad Python packages we all love with our own custom syntax. We aim to provide you with something that is familiar when you want it to be, and powerful when you need it to be.
+Eons provides an easy plug-and-play style of development by mElderlanging the myriad Python packages we all love with our own custom syntax. We aim to provide you with something that is familiar when you want it to be, and powerful when you need it to be.
 
@@ -44,12 +44,12 @@ The most condensed form of our syntax is as follows:
 
-This language style derives from the [Eons Language of Development](https://github.com/develop-biology/language.development) (ELD). The only real features missing, besides some nicer character choices (e.g. use of `{}` for Execution Blocks) are Space Autofill, and the ability to define functions, classes, and Functors in Parameter Blocks (i.e. `()`). So, for now, you're restricted to just lambdas or breaking your larger logic out into a separate Functor. 
+This language style derives from the [Eons Language of Development for Entropic Reduction](https://github.com/elderlang/elderlang) (Elderlang). The only real features missing, besides some nicer character choices (e.g. use of `{}` for Execution Blocks) are Space Autofill, and the ability to define functions, classes, and Functors in Parameter Blocks (i.e. `()`). So, for now, you're restricted to just lambdas or breaking your larger logic out into a separate Functor. 
 
 The main differences between the Kind syntax and the Eons Language of Development are:
 * The `@eons.kind` decorator is used to declare a Type Block.
-* `this` is used instead of `$` (or `self` in Python).
-* `caller` is used instead of `$$`.
+* `this` is used instead of `./` (or `self` in Python).
+* `epidef` is used instead of `../`.
 * Spatial Separation is big endian, rather than how domains are named (i.e. LSB..TLD).
 * Sequences are built by `eons.Flow()`s (still under development).
 * Python STILL does not have multiline comments >:(
-* Python has both dictionaries and lists, vs just Containers in ELD
+* Python has both dictionaries and lists, vs just Containers in Elderlang
 * `def` is required to start a Parameter Block & `:` is required to start an Execution Block, both of which must always happen in that order (and be preceded by a Type Block).
@@ -67,8 +67,8 @@ * Convenient type casting is not fully implemented in Kind.
 
-To answer this question, ELD introduces the keyword `$$`. In Kind, we simply call this `caller`.
+To answer this question, Elderlang introduces the keyword `./`. In Kind, we simply call this `epidef`.
 
-So, you can use `caller.someMember` to share access across Functors composed by the same class, and `this.someMember` to access the Functor's own members.
+So, you can use `epidef.someMember` to share access across Functors composed by the same class, and `this.someMember` to access the Functor's own members.
 
 ### Access Control
-There is no true access control in Python. So, implementing it via Biology has been slow going. However, for now, you can use something akin to ELD's `public(...)` Functor to make defining method injection easier.
+There is no true access control in Python. So, implementing it via Biology has been slow going. However, for now, you can use something akin to Elderlang's `public(...)` Functor to make defining method injection easier.
 
@@ -75,0 +75,0 @@ Instead of saying:

setup.cfg

 [metadata]
 name = eons
-version = 3.0.12
+version = 3.1.0
 author = Eons
@@ -25,8 +25,8 @@ author_email = [e-mail]
 install_requires = 
+	pyyaml
+	eot
+	requests
+	requests_futures
 	jsonpickle
 	tqdm
-	requests_futures
-	requests
-	eot
-	pyyaml
 
@@ -33,0 +33,0 @@ [options.packages.find]

Alert delta unavailable

Currently unable to show alert delta for PyPI packages.

Improved metrics

Total package byte prevSize

208312

0.32%

Lines of code

2903

0.35%