pinax / pinax-eventlog Goto Github PK

I can't get the override of the extra_data property to work on a CBV view. It complains about view object is not JSON serializable.

This is what I am trying to do to override it.

 class  ApplicationUpdateView(EventLogMixin, UpdateView):
     ....
     def extra_data(self):      
         return super(ApplicationUpdateView, self).extra_data({"TEST": "TEST"})

Looking for maintainers!

There is a lot of pull requests and open issues that the current maintainers, myself included, are just not finding the time to properly get to.

Maybe you've submitted some PRs and are frustrated with the lack of attention. Maybe you use this project in one or more of your projects and want to see that it is properly carried forward.

Whatever you reasons may be, let me know if you have interest and I'll add you to the repo and to PyPI (will need your PyPI name).

Preference will go to those who have commits on this repo and/or have shown an active interest in the issues.

Thanks!
Patrick

Patch is missing for this repo

Maintain log instances even if the related object is deleted.

Change CASCADE to SET_NULL in https://github.com/pinax/pinax-eventlog/blob/master/pinax/eventlog/models.py#L21.

don't let exceptions from pusher bubble up to the end user, breaking sites if pusher happens to be down

I would like to use jsonfield instead of django-jsonfield which works fine once it is installed but when I install eventlog after I installed jsonfield django-jsonfield will overwrite the package. This is more of a django-jsonfield issue but I was wondering if maybe eventlog could provide an option to install jsonfield instead of django-jsonfield.

I think I would change the setup.py to include an "extra" option to use jsonfield instead. What do you think?

the docs suggest jsonfield must be installed separately but pip install eventlog will actually do it for you

Im getting this error, i have installed using:
sudo pip install pinax-eventlog

Also i have added 'pinax.eventlog' to the installed apps but nothing.

Anyway to solve this?
PD: Solve it.
This problem was due to i had installed 'Pinax' and also 'pinax-eventlog', so i uninstalled both and then installing only 'pinax-eventlog'.

Describe the bug
I tried to upgrade to new version pinax-eventlog for my app with djangoV3.0.8, Python 3.8,Mysql 5.7.22 and when trying to launch the instance i see this following error. When I looked at the migration file
eventlog.0004_auto_20191205_2033 that is failing on it trying to grab a postgres field/variable (field=django.contrib.postgres.fields.jsonb.JSONField()) which my app doesn't have
I see this issue with both 3.0.1 and 4.0.1 version and currently i was on v2 which did not had a problem. is there a work around for this?

Applying eventlog.0001_initial... OK
Applying eventlog.0002_auto_20150113_1450... OK
Applying eventlog.0003_auto_20160111_0208... OK
Applying eventlog.0004_auto_20191205_2033...Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/django/db/backends/utils.py", line 86, in _execute
   return self.cursor.execute(sql, params)
File "/usr/local/lib/python3.8/site-packages/django/db/backends/mysql/base.py", line 74, in execute
    return self.cursor.execute(query, args)
   File "/usr/local/lib/python3.8/site-packages/MySQLdb/cursors.py", line 209, in execute
    res = self._query(query)
   File "/usr/local/lib/python3.8/site-packages/MySQLdb/cursors.py", line 315, in _query
     db.query(q)
  File "/usr/local/lib/python3.8/site-packages/MySQLdb/connections.py", line 239, in query
    _mysql.connection.query(self, query)
 MySQLdb._exceptions.ProgrammingError: (1064, "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'jsonb NOT NULL' at line 1")

Reproduce behavior

1. Upgrade to new version 4.0.1 build and start the instance and when applying migrations the error occurs

Expected behavior
All migrations should apply correctly

Desktop

• Mac

I get this error when trying to add logs manually via admin. I am using Python 3.4 and Django 1.7

maybe instead of a view or in addition to a view, a django-rest-framework api endpoint

When using the template tags and retrieve the calls with the following line
{% user_event_log user as logs %}
I got an error saying "global name 'Event' is not defined."

And, when I changed eventlog_tags.py to get the logs from Log model, everything looks fine. So I either missing something or the library has a dependency that can not be resolved.

Django version is 1.6.1
Database is Postgres

As discussed in #32, #33 drops Django 2.2 support.

Since Django 2.2 is an LTS release, the co-author of the new JSONField added in 3.1 actually created a backport package:

https://github.com/laymonage/django-jsonfield-backport#why-create-another-one

Django's release process does not backport new features to previous feature releases. However, the current LTS release is 2.2 which is still supported until April 2022. The next LTS release is Django 3.2 in April 2021 that happens to be the end of extended support for Django 3.1.

Some projects only use LTS releases of Django. There are also incompatibilities between Django 3.0 and 3.1. Therefore, using Django 3.1 may not be an option for some people at the moment

Since JSONField seems to be in popular demand and that it works well as a standalone package, I decided to create a backport.

I'd like to propose we introduce a small shim to the 5.x release that:

• adds django-jsonfield-backport as an optional dependency
• modifies models.py and the initial migration to work with the shim'd field
• provides documentation to site developers on how to use eventlog in Django~2.2 projects via django-jsonfield-backport

As part of this work, we would update the tox test matrix to prove out this support.

@paltman and @KatherineMichel: Does this seem reasonable to you? This would allow us to leverage the awesome JSONField while still keeping Django 2.2 compatibility as outlined in https://github.com/pinax/pinax/wiki/Pinax-20.XX-Release-Plan#pinax-20xx-release-overview.

If so, I can prepare a PR within the next week or so.

Thanks!

We are finding it difficult to use this in our Mysql-based project because of the reliance in release 3.0.1 because of the reliance on django.contrib.postgres.fields to define the "extra" field.

When will the next release on pypi be?

Thanks.

Should this file exist?

Documentation Quickstart section should mention that the migrations should be run.

I get the following error when trying to install eventlog in a virtualenv with Python 3:

» pip install eventlog
Downloading/unpacking eventlog
  Downloading eventlog-0.6.6.tar.gz
  Running setup.py egg_info for package eventlog
    Traceback (most recent call last):
      File "<string>", line 16, in <module>
      File "/home/totte/virtual_environments/webenv/build/eventlog/setup.py", line 138, in <module>
        zip_safe=False
      File "/usr/lib/python3.3/distutils/core.py", line 148, in setup
        dist.run_commands()
      File "/usr/lib/python3.3/distutils/dist.py", line 917, in run_commands
        self.run_command(cmd)
      File "/usr/lib/python3.3/distutils/dist.py", line 936, in run_command
        cmd_obj.run()
      File "<string>", line 13, in replacement_run
      File "/home/totte/virtual_environments/webenv/lib/python3.3/site-packages/setuptools/command/egg_info.py", line 415, in write_pkg_info
        metadata.write_pkg_info(cmd.egg_info)
      File "/usr/lib/python3.3/distutils/dist.py", line 1015, in write_pkg_info
        self.write_pkg_file(pkg_info)
      File "/usr/lib/python3.3/distutils/dist.py", line 1036, in write_pkg_file
        long_desc = rfc822_escape(self.get_long_description())
      File "/usr/lib/python3.3/distutils/util.py", line 490, in rfc822_escape
        lines = header.split('\n')
    TypeError: Type str doesn't support the buffer API
...