Consult the django-project-template on how to use it.
Upgrade from 1.7 to 1.8
In 1.8 there is a new username column introduced which removes unique identification responsibility from the email column. To migrate existing users and populate the DB sucessfully add the following script to your migrations. Fix the model name as needed and update the dependency to the last previous migration.
Afterwards run makemigrations as usual to update other fields.
populate username migration:
import django.contrib.auth.validators
from django.db import migrations, models
from django.db.models import Count
def populate_usernames(apps, schema_editor):
User = apps.get_model('app', 'User')
for grp in User.objects.exclude(um_id__isnull=True).values('um_id').annotate(ct=Count('um_id')):
if grp['ct'] > 1:
User.objects.filter(um_id=grp['um_id']).update(um_id=None)
for u in User.objects.all():
if u.um_id:
u.username = 'um_%s' % u.um_id
else:
u.username = 'user_%s' % u.id
u.save()
class Migration(migrations.Migration):
dependencies = [
('app', '0009_auto_20180208_1339'),
]
operations = [
migrations.AddField(
model_name='user',
name='username',
field=models.CharField(null=True,
help_text='Required. 150 characters or fewer. Letters, digits and @/./+/-/_ only.',
max_length=150, unique=False,
validators=[django.contrib.auth.validators.UnicodeUsernameValidator()],
verbose_name='username'),
),
migrations.RunPython(populate_usernames),
migrations.AlterField(
model_name='user',
name='username',
field=models.CharField(error_messages={'unique': 'A user with that username already exists.'},
help_text='Required. 150 characters or fewer. Letters, digits and @/./+/-/_ only.',
max_length=150, unique=True,
validators=[django.contrib.auth.validators.UnicodeUsernameValidator()],
verbose_name='username'),
)
]
Metadata
Release files for django-slxauth 1.16.2
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 |
|---|---|---|---|---|
| django-slxauth-1.16.2.tar.gz | 15.4 kB | Without provenance | Details for django-slxauth-1.16.2.tar.gz |
Release files / django-slxauth-1.16.2.tar.gz
| Download URL | django-slxauth-1.16.2.tar.gz |
|---|---|
| Size | 15.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fda33e318ef21291c925faf0a6d34e2bf0d3c2856734ee1f3670911c2b28961b
|
|
BLAKE2b-256 checksum How to use checksums |
b89e12e491d07973b584a4217e99c1709e140420fa317cdfb9fcd18cd728a4ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.6.15
|
Security for django-slxauth 1.16.2
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.