This website requires JavaScript.
Explore
Help
Sign In
altf4arnold
/
datatracker
Watch
1
Star
0
Fork
You've already forked datatracker
0
Code
Issues
Pull requests
Actions
3
Packages
Projects
Releases
Wiki
Activity
2d7c9629aa
datatracker
/
ietf
/
community
History
Henrik Levkowetz
2d7c9629aa
Added 'from __future__' imports all over the place, to bring code behaviour into closer alignment between python2 and python3
...
- Legacy-Id: 16446
2019-07-15 15:40:51 +00:00
..
migrations
Added 'from __future__' imports all over the place, to bring code behaviour into closer alignment between python2 and python3
2019-07-15 15:40:51 +00:00
__init__.py
Added in the community app, which wasn't included properly in the previous commit.
2012-06-27 08:26:18 +00:00
admin.py
Added 'from __future__' imports all over the place, to bring code behaviour into closer alignment between python2 and python3
2019-07-15 15:40:51 +00:00
forms.py
Added 'from __future__' imports all over the place, to bring code behaviour into closer alignment between python2 and python3
2019-07-15 15:40:51 +00:00
models.py
Changed all model __unicode__() methods to __str__()
2019-06-28 21:07:08 +00:00
resources.py
Added 'from __future__' imports all over the place, to bring code behaviour into closer alignment between python2 and python3
2019-07-15 15:40:51 +00:00
tests.py
Added 'from __future__' imports all over the place, to bring code behaviour into closer alignment between python2 and python3
2019-07-15 15:40:51 +00:00
urls.py
Updated all urlpatterns to use ietf.utils.urls.url() instead of django's,
2017-02-11 14:43:01 +00:00
utils.py
Added 'from __future__' imports all over the place, to bring code behaviour into closer alignment between python2 and python3
2019-07-15 15:40:51 +00:00
views.py
Corrected the content type for some JSON responses.
2019-07-07 12:39:22 +00:00