========================================
It allows you to keep PEP8 naming style, using libraries like `Twisted` or `unittest`.
Here is example:
#!/usr/bin/python
import unittest
from namalizer import pep8
class MyTests(unittest.TestCase):
def set_up(self):
self.a = 'blah'
def test_example(self):
self.assert_equal(self.a, 'blah')
pep8(**locals())
# or
pep8(MyTests)
if __name__ == '__main__':
unittest.main()
Namalizer creates aliases for method with wrong names. In this case,
it will create aliazes in `unittest.TestCase` for methods like `setUp`,
`assertEqual`, etc..
Then, it will see that you created method `set_up` to override base class's
functionality and will create alias `setUp` for this method, this way
when `unittest` will call `setUp`, you version will be called.
Migration
---------
If you use some library with ugly naming method, this regex will help you to
find all places where wrong names are used:
git grep -e '\(\.\|def \)[a-z]\+[A-Z]'
Credits
-------
* Alexander Artemenko <<svetlyak.40wt@gmail.com>> — original author.
Fork the project, contribute and send me patches.
Metadata
Release files for namalizer 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| namalizer-0.1.1.tar.gz | 2.6 kB | Without provenance | Details for namalizer-0.1.1.tar.gz |
Release files / namalizer-0.1.1.tar.gz
| Download URL | namalizer-0.1.1.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
409ecc0476e992b1c2c493207daa98e2ebee8476c214c5a40d5e0edad01608d4
|
|
BLAKE2b-256 checksum How to use checksums |
8fd61c0bec28dfd226b7f4dae4d268b2ef27d5a75e558abd42ca8096d7b9067e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for namalizer 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.