semvec/pypi-packages huggingface dataset:
seq2ftr 0.1.7
A Nice and Convenient Feature Engineering Tool on Sequential Data

This project handles series data


Support Series data Feature Calculation.


Installation
==============

You need Python installed on your system to able to use seq2ftr.

This package contains many feature extraction methods.

Support different type (continues/class) features calculation.

>>> $ pip install seq2ftr

Install Requirements
 * numpy
 * pandas
 * sklearn


Feature Calculation
^^^^^^^^^^^^^^^^^^^^^^^^
 Support Function

 - mean
 - max
 - min
 - freq_of_max
 - freq_of_min
 - median
 - median_mean_distance
 - percentage_below_mean
 - var
 - std
 - uniqueCount
 - ...

Support Type
^^^^^^^^^^^^^^^^^
 - 0 - boolean
 - 1 - numericla
 - 2 - categorical


Example
^^^^^^^^^^^^^
To start , we load data to python

>>>
import pandas as pd
df = pd.DataFrame([[1,200,"1"],[1,500,"2"],[2,300,"2"],[2,600,"2"]],columns=['id','stock_price',"type"])
df = df.set_index("id")

>>>
from seq2ftr import SequenceTransformer
st_num = SequenceTransformer()
st_num.transformer(df['stock_price']）
# output all features
testing-upload 0.0.1
A small example package

**Edit a file, create a new file, and clone from Bitbucket in under 2 minutes**

When you're done, you can delete the content in this README and update the file with details for others getting started with your repository.

*We recommend that you open this README in another tab as you perform the tasks below. You can [watch our video](https://youtu.be/0ocf7u76WSo) for a full demo of all the steps in this tutorial. Open the video in a new tab to avoid leaving Bitbucket.*

---

## Edit a file

You’ll start by editing this README file to learn how to edit a file in Bitbucket.

1. Click **Source** on the left side.
2. Click the README.md link from the list of files.
3. Click the **Edit** button.
4. Delete the following text: *Delete this line to make a change to the README from Bitbucket.*
5. After making your change, click **Commit** and then **Commit** again in the dialog. The commit page will open and you’ll see the change you just made.
6. Go back to the **Source** page.

---

## Create a file

Next, you’ll add a new file to this repository.

1. Click the **New file** button at the top of the **Source** page.
2. Give the file a filename of **contributors.txt**.
3. Enter your name in the empty file space.
4. Click **Commit** and then **Commit** again in the dialog.
5. Go back to the **Source** page.

Before you move on, go ahead and explore the repository. You've already seen the **Source** page, but check out the **Commits**, **Branches**, and **Settings** pages.

---

## Clone a repository

Use these steps to clone from SourceTree, our client for using the repository command-line free. Cloning allows you to work on your files locally. If you don't yet have SourceTree, [download and install first](https://www.sourcetreeapp.com/). If you prefer to clone from the command line, see [Clone a repository](https://confluence.atlassian.com/x/4whODQ).

1. You’ll see the clone button under the **Source** heading. Click that button.
2. Now click **Check out in SourceTree**. You may need to create a SourceTree account or log in.
3. When you see the **Clone New** dialog in SourceTree, update the destination path and name if you’d like to and then click **Clone**.
4. Open the directory you just created to see your repository’s files.

Now that you're more familiar with your Bitbucket repository, go ahead and add a new file locally. You can [push your change back to Bitbucket with SourceTree](https://confluence.atlassian.com/x/iqyBMg), or you can [add, commit,](https://confluence.atlassian.com/x/8QhODQ) and [push from the command line](https://confluence.atlassian.com/x/NQ0zDQ).
dualtest 1.0.1
Easily test both Python and C versions of modules.
Requires Python: >= 3.6

When you write a C extension, you can provide a Python version as a backup. A
problem with this is that only one of these modules will be tested, while the
other is neglected.

DualTest provides a class that, when inherited from, imports a list of modules
and attributes from modules and makes them available as globals during tests.
Allowing you to easily test both versions of a module and write just one set of
tests.

=====
Usage
=====

Create a test case class derived from DualTestCase and set the `import_names`
or `import_from_names` class attributes.

`import_names` should be set to a list of the names of modules with Python
source and C extension versions to import:

.. code:: python

    class ImportTestCase(DualTestCase):
        import_names = ['mod1', 'mod2']

        def test_something(self):
            # mod1 and mod2 will be available here.

`import_from_names` causes attributes to be imported from modules just like
`from module import attribute` would. It should be set to a list of tuples
containing the name of the module to import from, and a list of attribute names
to import. If one of the attribute names is "*", then all public attributes are
imported:

.. code:: python

    class ImportFromTestCase(DualTestCase):
        import_from_names = [
            ('mod1', ['attr1', 'attr2']),
            # "*" causes all public attributes to be imported.
            ('mod2', ['*']),
            ]

        def test_something(self):
            # attr1, attr2 and everything from mod2 will be available here.

============
Full Example
============

.. code:: python

    from dualtest import DualTestCase


    class ImportTestCase(DualTestCase):
        import_names = ['mod1', 'mod2']

        def test_something(self):
            # mod1 and mod2 will be available here.


    class ImportFromTestCase(DualTestCase):
        import_from_names = [
            ('mod1', ['attr1', 'attr2']),
            # "*" causes all public attributes to be imported.
            ('mod2', ['*']),
            ]

        def test_something(self):
            # attr1, attr2 and everything from mod2 will be available here.

=========
Changelog
=========

1.0.1
-----

* Patch imported modules into "sys.modules" during tests.
* Fix error when "import_from_names" references a non-existing module.
* Fix bug when importing '*' from a module.
* Add module type context when "subTest" is called.