andrewbihl / bsed Goto Github PK

PyPI has 0.2.4 , with tests in the sdist, but no *.json test data files, so all tests pass when installing and testing from the sdist.

btw, you could pypi install and run check-manifest to build a complete MANIFEST.in.

GitHub has no tags at https://github.com/andrewbihl/bsed/releases, so I cant use that for fetching a usable tarball.

Would you be able to tag v0.2.4 in GitHub, so I can use it to get a complete archive, and finish packaging for openSUSE at https://build.opensuse.org/package/show/home:jayvdb:py-new/python-bsed . Or we can fix MANIFEST.in if you are intending to do a new release soon.

perl -nl -e "s/Jack/Jill/g; print;" file.txt

Is a slightly odd way to do this. The usual one-liner would be

perl -p -i -e 's/Jack/Jill/g' file.txt

As this edits the file in place

I'd like to be able to run commands on all lines of a file. For example, bsed wrap lines with " should execute on all lines of the file. Current workaround is to include some trivial filter like wrap lines containing '.' with "

I'd like to have a syntax for word boundaries. For example:

select lines containing word sock

would return:

I am only wearing one sock today.

but not:

The socket opened but no connection was made.

In packaging .spec files, there are a few very common tasks which are normally done with sed/awk/etc.

Most could be expressed as a bsed command which would be nice.

e.g. equiv of dos2unix, removing hashbang, replacing hashbangs.

i.e. https://python-rpm-porting.readthedocs.io/en/latest/applications.html#fixing-shebangs really recommends people write those commands. Surely we can do better than that before 2020 lands ;-)

Packaging python has a few others like replace == with >= inside setup.py strings.

It would be useful if these could be stored commands somehow.

they could be scripts which use bsed as their interpreter, or named aliases like 'bsed run foo', with details in a config.