The Wayback Machine - https://web.archive.org/web/20201215181107/https://github.com/python/pythondotorg/issues/893
Skip to content
Sign up
Sign in Sign up

/ pythondotorg

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Upgrade waffle to 0.11 #893

Closed
CarlFK opened this issue Feb 27, 2016 · 5 comments
Closed

Upgrade waffle to 0.11 #893

CarlFK opened this issue Feb 27, 2016 · 5 comments

Comments

@CarlFK
Copy link
Contributor

@CarlFK CarlFK commented Feb 27, 2016

(I think that's the proper description)

vagrant up, ssh in,
cd pythondotorg
source venv/bin/activate
(venv) vagrant@vagrant-ubuntu-trusty-64:~/pythondotorg$ ./manage.py migrate

(venv) vagrant@vagrant-ubuntu-trusty-64:~/pythondotorg$ ./manage.py migrate
/home/vagrant/pythondotorg/venv/lib/python3.4/site-packages/django/contrib/comments/__init__.py:13: RemovedInDjango18Warning: django.contrib.comments is deprecated and will be removed before Django 1.8.
  warnings.warn("django.contrib.comments is deprecated and will be removed before Django 1.8.", RemovedInDjango18Warning)

/home/vagrant/pythondotorg/venv/lib/python3.4/site-packages/tastypie/resources.py:2210: RemovedInDjango18Warning: commit_on_success is deprecated in favor of atomic.
  @transaction.commit_on_success()

Operations to perform:
  Synchronize unmigrated apps: jsonfield, haystack, imagekit, peps, pipeline, comments, timedelta, allauth, django_comments_xtd, debug_toolbar, cms
  Apply all migrations: blogs, successstories, downloads, events, jobs, sites, community, companies, pages, sitetree, admin, codesamples, waffle, sponsors, minutes, contenttypes, socialaccount, users, auth, sessions, feedbacks, account, redirects, boxes, tastypie, work_groups
Synchronizing apps without migrations:
  Creating tables...
  Installing custom SQL...
  Installing indexes...
Running migrations:
  No migrations to apply.
  Your models have changes that are not yet reflected in a migration, and so won't be applied.
  Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them.
(venv) vagrant@vagrant-ubuntu-trusty-64:~/pythondotorg$
@berkerpeksag
Copy link
Member

@berkerpeksag berkerpeksag commented Feb 27, 2016 

  Your models have changes that are not yet reflected in a migration, and so won't be applied.
  Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them.

Did you try to create new migration and run manage.py makemigrations as described in the output?
@CarlFK
Copy link
Contributor Author

@CarlFK CarlFK commented Feb 27, 2016 

(venv) vagrant@vagrant-ubuntu-trusty-64:~/pythondotorg$ ./manage.py
makemigrations
/home/vagrant/pythondotorg/venv/lib/python3.4/site-packages/django/contrib/comments/__init__.py:13:
RemovedInDjango18Warning: django.contrib.comments is deprecated and will be
removed before Django 1.8.
  warnings.warn("django.contrib.comments is deprecated and will be removed
before Django 1.8.", RemovedInDjango18Warning)

/home/vagrant/pythondotorg/venv/lib/python3.4/site-packages/tastypie/resources.py:2210:
RemovedInDjango18Warning: commit_on_success is deprecated in favor of
atomic.
  @transaction.commit_on_success()

Migrations for 'waffle':
  0002_auto_20160227_2155.py:
    - Alter field authenticated on flag
    - Alter field created on flag
    - Alter field everyone on flag
    - Alter field groups on flag
    - Alter field languages on flag
    - Alter field modified on flag
    - Alter field name on flag
    - Alter field note on flag
    - Alter field percent on flag
    - Alter field rollout on flag
    - Alter field staff on flag
    - Alter field superusers on flag
    - Alter field testing on flag
    - Alter field users on flag
    - Alter field created on sample
    - Alter field modified on sample
    - Alter field name on sample
    - Alter field note on sample
    - Alter field percent on sample
    - Alter field active on switch
    - Alter field created on switch
    - Alter field modified on switch
    - Alter field name on switch
    - Alter field note on switch

(venv) vagrant@vagrant-ubuntu-trusty-64:~/pythondotorg$ ./manage.py
migrate/home/vagrant/pythondotorg/venv/lib/python3.4/site-packages/django/contrib/comments/__init__.py:13:
RemovedInDjango18Warning: django.contrib.comments is deprecated and will be
removed before Django 1.8.
  warnings.warn("django.contrib.comments is deprecated and will be removed
before Django 1.8.", RemovedInDjango18Warning)

/home/vagrant/pythondotorg/venv/lib/python3.4/site-packages/tastypie/resources.py:2210:
RemovedInDjango18Warning: commit_on_success is deprecated in favor of
atomic.
  @transaction.commit_on_success()

Operations to perform:
  Synchronize unmigrated apps: allauth, imagekit, comments,
django_comments_xtd, timedelta, peps, debug_toolbar, pipeline, jsonfield,
haystack, cms
  Apply all migrations: boxes, socialaccount, companies, users, pages,
sites, waffle, admin, account, sitetree, jobs, codesamples, sessions,
tastypie, contenttypes, feedbacks, work_groups, minutes, downloads,
successstories, redirects, events, sponsors, community, auth, blogs
Synchronizing apps without migrations:
  Creating tables...
  Installing custom SQL...
  Installing indexes...
Running migrations:
  Applying waffle.0002_auto_20160227_2155... OK

On Sat, Feb 27, 2016 at 4:16 PM, Berker Peksag notifications@github.com
wrote:

Your models have changes that are not yet reflected in a migration, and so won't be applied.
Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them.

Did you try to create new migration and run manage.py makemigrations as
described in the output?

—
Reply to this email directly or view it on GitHub
#893 (comment)
.

Carl K
@berkerpeksag
Copy link
Member

@berkerpeksag berkerpeksag commented Feb 28, 2016

So it worked? Did you get any OperationalErrors when you ran manage.py runserver?
@CarlFK
Copy link
Contributor Author

@CarlFK CarlFK commented Feb 28, 2016

looks like creating/doing the migrations worked.
I don;t see any OperationalErrors when you ran manage.py runserver.

On Sat, Feb 27, 2016 at 6:03 PM, Berker Peksag notifications@github.com
wrote:

So it worked? Did you get any OperationalErrors when you ran manage.py
runserver?

—
Reply to this email directly or view it on GitHub
#893 (comment)
.

Carl K
@berkerpeksag
Copy link
Member

@berkerpeksag berkerpeksag commented Apr 1, 2016

I believe this is a bug in waffle. A migration was created in Python 2 with b'' strings. And fortunately it has already been fixed in django-waffle/django-waffle@31c0037. We will need to upgrade waffle to 0.11. I will update the issue title.
@berkerpeksag berkerpeksag changed the title migrations not checked in Upgrade waffle to 0.11 Apr 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@CarlFK @berkerpeksag
You can’t perform that action at this time.
Morty Proxy This is a proxified and sanitized view of the page, visit original site.