Re: Open Source IDE to start with Django Web development

[Fabio Caritas Barrionuevo da Luz]

>
> But free edition of PyCharm expires after 1 month or so.
>

This is not entirely true. The Pycharm has two versions: Pycharm 
Professional and Pycharm Community

Pycharm Professional has a free trial that expires after 1 month.  After 
the trial time, you must purchase a license to continue to use Pycharm 
Professional.

Pycharm Community is open-source, free and never expires.

see the comparison:

https://www.jetbrains.com/pycharm/features/editions_comparison_matrix.html

If you are a student you can get licenses of Professional versions for 
free:  https://www.jetbrains.com/student/

Github also has a student package: https://education.github.com/pack




> On Wed, 6 Nov, 2019, 6:52 PM Jasim Ak, > 
> wrote:
>
>> PyCharm is fantastic in terms of code completion, linting etc and if 
>> you're a student, you might get their professional edition for free as 
>> well. Please note that they have a community edition that is open source.
>>
>> On Wed, 6 Nov 2019, 18:26 Kasper Laudrup, > > wrote:
>>
>>> Hi Himanshu,
>>>
>>> On 06/11/2019 11.52, himanshu goyal wrote:
>>> > To Community,
>>> > 
>>> > Greetings!
>>> > 
>>> > Could you suggest a good open source IDE for Django? URL to download 
>>> > will be helpful.
>>> > 
>>>
>>> What is considered "good" is highly subjective, so you will get widely 
>>> different answers depending on who you ask.
>>>
>>> I personally use Emacs like I do for almost everything else, so of 
>>> course that is the best ;-)
>>>
>>> You should at least try to clarify a bit more what your requirements are 
>>> apart from just "open source" (platform, features required, language 
>>> support etc.).
>>>
>>> Kind regards,
>>>
>>> Kasper Laudrup
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Django users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to django...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/django-users/58ec109a-494b-16b1-123d-c2a1079cd547%40stacktrace.dk
>>> .
>>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Django users" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/django-users/rG4-e5gAX3A/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> django...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/CABh2F57G1x77Q%3D1i%3DOBNsqTVDgHBq4nMSWhq3GbMNWYAhCRYbQ%40mail.gmail.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/6d21de7d-ba10-4377-8dc4-cc14ae37899f%40googlegroups.com.

Re: Introduction to Pulpo-Forms

[Fabio Caritas Barrionuevo da Luz]

interesting, thanks for sharing.

personally, I think that the organization of files on package is somewhat 
confusing.

said that, you can use a template (skeleton) as a base to create and better 
organize the package.
I like these two

for a django package:

https://github.com/pydanny/cookiecutter-djangopackage

or more generic to any python package:

https://github.com/ionelmc/cookiecutter-pylibrary

It is quite easy to generate a new project skeleton:

pip install cookiecutter

cookiecutter https://github.com/pydanny/cookiecutter-djangopackage

or

cookiecutter https://github.com/ionelmc/cookiecutter-pylibrary



Em quinta-feira, 30 de julho de 2015 18:46:12 UTC-3, Luciano Ferrari 
escreveu:
>
> Last April we finished the development of a dynamic form builder, called 
> pulpo-forms, to use within a Django Project. Today we’re excited to 
> announce that we’re making the source code available on GitHub 
> .
>
> Here is a short list with the most important features of this new open 
> source tool:
>
>- Enable users to create forms with an easy drag UI
>- Angular directives to render the form  
>and the dashboard
>- Multi pages forms.
>- RESTful API
>- Customizable fields validations such as required, length,etc.
>- Conditional enable for fields based on other field values (e.g. in a 
>food preferences survey, hide the *‘How do you like your steak?’ *question 
>to someone that previously answered that’s a vegetarian).
>- Conditional enable for form pages based on other field values.
>- Versions and drafts.
>- Integration for Django models.
>- Signals.
>- Configurable actions – show a thank you screen, send an email, etc.
>- Built-in statistics in the dashboard
>- Basic field types answers can be filtered in the dashboard
>
> Since it was made to be flexible from the beginning, this can be extended 
> to add new fields, validations and so on.
>
> We hope you enjoy it, and of coursed we are open to comments, questions 
> and pull requests !
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/cf0e43ee-3484-41e4-8f32-35112eed7ca2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANNOUNCE] Django 1.8 alpha 1 released

[Fabio Caritas Barrionuevo da Luz]

Em sexta-feira, 16 de janeiro de 2015 20:10:37 UTC-3, Tim Graham escreveu:
>
> We've made the first release on the way to Django's next long-term support 
> release, Django 1.8! With only two and a half months until the scheduled 
> final release, we'll need prompt testing from the community to ensure a 
> timely and stable release. Check out the blog post:
>
>
> https://www.djangoproject.com/weblog/2015/jan/16/django-18-alpha-1-released/
>


Wow, many new things. Very good.

I have not seen in the release-notes that the inspectdb now supports 
inspect "database views" to the backends where it is supported.

This change was made in this commit:

https://github.com/django/django/commit/b8cdc7dcc3fc6897fb2a75f90023f5c67aad327f
 

See the "get_table_list" function in introspection.py file, in each 
database backend

I look forward a day, that Django has support for inspecting "multiple 
database schemas" and work properly with an official api to do this.

https://code.djangoproject.com/ticket/22673
https://code.djangoproject.com/ticket/6148

I was trying to figure out ways to solve this old problem of django.
Also i know that adding support for multiple database schemas is not 
something trivial for Django, because if it was, I'm sure that would be 
already been implemented.

https://gist.github.com/luzfcb/e5f67e9c940e4833b798
http://dba.stackexchange.com/questions/87463/in-oracle-how-to-get-a-list-with-the-names-of-schemas-that-a-user-has-read-perm



-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/8e1efdd2-b8d4-4f7d-a498-188f06ff8999%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: dashboard for user profile

[Fabio Caritas Barrionuevo da Luz]

Em sexta-feira, 13 de julho de 2012 09h14min21s UTC-3, psychok7 escreveu:
>
> yes i understand that, but i am asking if there is a pluggable app that 
> does that for us with some jquery and stuff. 
>
> as i said theres is django-profiles, but i think its poorly documented and 
> i am not able to figure it out
>

see if any of those suits your need:

https://www.djangopackages.com/grids/g/profiles/

https://www.djangopackages.com/grids/g/profiles-2/  

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/2d99d256-a429-48ec-822a-88d550253775%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: create unmanaged model to oracle view/synonym

[Fabio Caritas Barrionuevo da Luz]

Hello, Shai and Edgar

yes, I've tried using *inspectdb*, however, it only generates models for 
database tables, but not for database View[1] and database Synonym[2].

The Django documentation is currently not explicit in showing that the 
specific database features are supported by Django database backends.

*inspectdb *does not support "database schemas"[3][4].

Any other ideas how to solve this?


[1] 
http://docs.oracle.com/cd/B19306_01/server.102/b14200/statements_8004.htm
[2] 
http://docs.oracle.com/cd/B19306_01/server.102/b14200/statements_8004.htm
[3] https://groups.google.com/d/msg/django-users/jsoDvI7DipU/CYOdstKeTYcJ 
[4] https://code.djangoproject.com/ticket/22673


-- 
Fábio C. Barrionuevo da Luz
Acadêmico de Sistemas de Informação na Faculdade Católica do Tocantins - 
FACTO
Palmas - Tocantins - Brasil - América do Sul

http://pythonclub.com.br/


Em quinta-feira, 1 de janeiro de 2015 16h57min38s UTC-3, Edgar Gabaldi 
escreveu:
>
> Fabio,
>
> Django ORM support Oracle Database[1].
>
> If you want connect an existing oracle database, i recomend you see the 
> inspectdb management command.
>
> [1] https://docs.djangoproject.com/en/1.7/ref/databases/#oracle-notes
> [2] https://docs.djangoproject.com/en/1.7/howto/legacy-databases/
>
>
> On Thu, Jan 1, 2015 at 2:40 PM, Shai <sh...@platonix.com > 
> wrote:
>
>> Hi Fábio,
>>
>> On Wednesday, December 31, 2014 6:05:05 PM UTC+2, Fabio Caritas 
>> Barrionuevo da Luz wrote:
>>>
>>> Hello, is possible with Django 1.7 create a unmanaged Django model for 
>>> Oracle database View?
>>>
>>>
>>>
>> Yes. In your model's Meta, set managed to False and db_table to the view 
>> name:
>>
>> class MyUnManagedModel(models.Model):
>> # ...
>> # fields
>> # ...
>> class Meta:
>> managed = False
>> db_table = 'view_name'
>>
>> Have you run into difficulties?
>>
>> HTH,
>> Shai.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to django-users...@googlegroups.com .
>> To post to this group, send email to django...@googlegroups.com 
>> .
>> Visit this group at http://groups.google.com/group/django-users.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/bf043f16-043a-4f0f-a6bf-2856c405be43%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/django-users/bf043f16-043a-4f0f-a6bf-2856c405be43%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/5791366f-bf4d-4ab9-b1de-8a15b63d5f54%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: create unmanaged model to oracle view/synonym

[Fabio Caritas Barrionuevo da Luz]

Hello, Shai and Edgar

yes, I've tried using *inspectdb*, however, it only generates models for 
database tables, but not for database View[1] and database Synonym[2].

The Django documentation is currently not explicit in showing that the 
specific database features are supported by Django database backends.

*inspectdb *does not support "database schemas"[3][4].

Any other ideas how to solve this?


-- 
Fábio C. Barrionuevo da Luz
Acadêmico de Sistemas de Informação na Faculdade Católica do Tocantins - 
FACTO
Palmas - Tocantins - Brasil - América do Sul

http://pythonclub.com.br/


Em quinta-feira, 1 de janeiro de 2015 16h57min38s UTC-3, Edgar Gabaldi 
escreveu:
>
> Fabio,
>
> Django ORM support Oracle Database[1].
>
> If you want connect an existing oracle database, i recomend you see the 
> inspectdb management command.
>
> [1] https://docs.djangoproject.com/en/1.7/ref/databases/#oracle-notes
> [2] https://docs.djangoproject.com/en/1.7/howto/legacy-databases/
>
>
> On Thu, Jan 1, 2015 at 2:40 PM, Shai <sh...@platonix.com > 
> wrote:
>
>> Hi Fábio,
>>
>> On Wednesday, December 31, 2014 6:05:05 PM UTC+2, Fabio Caritas 
>> Barrionuevo da Luz wrote:
>>>
>>> Hello, is possible with Django 1.7 create a unmanaged Django model for 
>>> Oracle database View?
>>>
>>>
>>>
>> Yes. In your model's Meta, set managed to False and db_table to the view 
>> name:
>>
>> class MyUnManagedModel(models.Model):
>> # ...
>> # fields
>> # ...
>> class Meta:
>> managed = False
>> db_table = 'view_name'
>>
>> Have you run into difficulties?
>>
>> HTH,
>> Shai.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to django-users...@googlegroups.com .
>> To post to this group, send email to django...@googlegroups.com 
>> .
>> Visit this group at http://groups.google.com/group/django-users.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/bf043f16-043a-4f0f-a6bf-2856c405be43%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/django-users/bf043f16-043a-4f0f-a6bf-2856c405be43%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/ce022ea9-dd02-47e0-a6bd-29a66ff089c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: create unmanaged model to oracle view/synonym

[Fabio Caritas Barrionuevo da Luz]

Hello, Shai and Edgar

yes, I've tried using *inspectdb*, however, it only generates models for 
database tables, but not for database View[1] and database Synonym[2].

The Django documentation is currently not explicit in showing that the 
specific database features are supported by Django database backends.

*inspectdb *does not support "database schemas"[3][4].

Any other ideas how to solve this?


[1] 
http://docs.oracle.com/cd/B19306_01/server.102/b14200/statements_8004.htm
[2] http://docs.oracle.com/cd/B19306_01/server.102/b14200/statements_8004.htm
[3] https://groups.google.com/d/msg/django-users/jsoDvI7DipU/CYOdstKeTYcJ 
[4] https://code.djangoproject.com/ticket/22673


Em quinta-feira, 1 de janeiro de 2015 16h57min38s UTC-3, Edgar Gabaldi 
escreveu:
>
> Fabio,
>
> Django ORM support Oracle Database[1].
>
> If you want connect an existing oracle database, i recomend you see the 
> inspectdb management command.
>
> [1] https://docs.djangoproject.com/en/1.7/ref/databases/#oracle-notes
> [2] https://docs.djangoproject.com/en/1.7/howto/legacy-databases/
>
>
> On Thu, Jan 1, 2015 at 2:40 PM, Shai <sh...@platonix.com > 
> wrote:
>
>> Hi Fábio,
>>
>> On Wednesday, December 31, 2014 6:05:05 PM UTC+2, Fabio Caritas 
>> Barrionuevo da Luz wrote:
>>>
>>> Hello, is possible with Django 1.7 create a unmanaged Django model for 
>>> Oracle database View?
>>>
>>>
>>>
>> Yes. In your model's Meta, set managed to False and db_table to the view 
>> name:
>>
>> class MyUnManagedModel(models.Model):
>> # ...
>> # fields
>> # ...
>> class Meta:
>> managed = False
>> db_table = 'view_name'
>>
>> Have you run into difficulties?
>>
>> HTH,
>> Shai.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to django-users...@googlegroups.com .
>> To post to this group, send email to django...@googlegroups.com 
>> .
>> Visit this group at http://groups.google.com/group/django-users.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/bf043f16-043a-4f0f-a6bf-2856c405be43%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/django-users/bf043f16-043a-4f0f-a6bf-2856c405be43%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/bfb315be-bbab-4704-85e6-5b8efadb7f4a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: not thread-safe function can break a django application?

[Fabio Caritas Barrionuevo da Luz]

Collin, Thanks for the explanation.


Em segunda-feira, 24 de novembro de 2014 20h01min55s UTC-3, Collin Anderson 
escreveu:
>
>
>
> On Saturday, November 22, 2014 4:46:56 AM UTC-5, Fabio Caritas Barrionuevo 
> da Luz wrote:
>>
>> I was trying to answer a question in a Brazilian forum about django.
>>
>> one of the proposed solutions utilized the function locale.setlocale() 
>> from locale module.
>>
>> according to the documentation[1] locale.setlocale() function is not 
>> thread-safe
>>
>> the question is: 
>>
>> not thread-safe function can break a django application?
>>
>  Yes
>
> If so, how? 
>>
> You can have "race conditions" where _sometimes_ you get unpredictable 
> results.
>
> Which scenario I would have problems? 
>>
> One request in one thread could set locale to English and then use the 
> locale, meanwhile, another thread could set it to Spanish and then use the 
> locale. If they did that at the same time, the English request might get 
> the Spanish locale, or the Spanish request might get the English locale.
>
> some easily reproducible example of problems using not thread-safe 
>> function?
>>
> import threading
> state = {}
>
> def english():
> state['locale'] = 'english'
> assert state['locale'] == 'english'
>
> def spanish():
> state['locale'] = 'spanish'
> assert state['locale'] == 'spanish'
>
> while 1:
> threading.Thread(target=english).start()
> threading.Thread(target=spanish).start()
>  
> (press ctrl+c to stop)
>
> Also, note that it says "If the locale is not changed thereafter, using 
> multithreading should not cause problems." So, if you only set it once and 
> never change it, you should be fine.
>
> Collin
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/30559735-cf14-4e67-8db5-7587e6a96073%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: django-allauth--"cannot import name SignupForm"

[Fabio Caritas Barrionuevo da Luz]

Please, show me the code. put the code and all traceback of the error on 
gist.github.com and send gist reference link here.


Em quinta-feira, 12 de junho de 2014 11h15min37s UTC-3, willyhakim escreveu:
>
> Good morning the good people of django.
>
>
> I customized django-allauth signup page with following this advice 
> 
>  
> from the author himself.
>
> https://stackoverflow.com/questions/12303478/how-to-customize-user-profile-when-using-django-allauth
>
> but I keep getting an error: Error importing form class myusers.forms: 
> "cannot import name SignupForm"
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/de6fea6f-f531-4eea-886c-aef8d9bf3f7b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to install psycopg2 using Pip?

[Fabio Caritas Barrionuevo da Luz]

If Ubuntu 12.04 or higher

do:

sudo apt-get install libpq-dev




Em quinta-feira, 24 de março de 2011 12h01min43s UTC-3, Andre Lopes 
escreveu:
>
> Hi,
>
> This question is not directly related with Django, but with Python.
>
> I have installed "virtualenv" to have a virtual environment. Now I
> need to instal "psycopg2" in my virtual environment, but I have not
> successfully installed.
>
> My steps:
>
> [quote]
> pip install
>
> http://pypi.python.org/packages/source/p/psycopg2/psycopg2-2.4.tar.gz#md5=24f4368e2cfdc1a2b03282ddda814160
> [/quote]
>
> And I got this message with an error:
>
> [quote]
> Downloading/unpacking
> http://pypi.python.org/packages/source/p/psycopg2/psycopg2
> -2.4.tar.gz#md5=24f4368e2cfdc1a2b03282ddda814160
>   Downloading psycopg2-2.4.tar.gz (607Kb): 607Kb downloaded
>   Running setup.py egg_info for package from
> http://pypi.python.org/packages/sou
>
> 
> rce/p/psycopg2/psycopg2-2.4.tar.gz#md5=24f4368e2cfdc1a2b03282ddda814160
> Error: pg_config executable not found.
>
> Please add the directory containing pg_config to the PATH
> or specify the full executable path with the option:
>
> python setup.py build_ext --pg-config 
> /path/to/pg_config build ...
>
> or with the pg_config option in 'setup.cfg'.
> Complete output from command python setup.py egg_info:
> running egg_info
>
> creating pip-egg-info\psycopg2.egg-info
>
> writing pip-egg-info\psycopg2.egg-info\PKG-INFO
>
> writing top-level names to 
> pip-egg-info\psycopg2.egg-info\top_level.txt
>
> writing dependency_links to 
> pip-egg-info\psycopg2.egg-info\dependency_links.txt
>
> writing manifest file 'pip-egg-info\psycopg2.egg-info\SOURCES.txt'
>
> warning: manifest_maker: standard file '-c' not found
>
> Error: pg_config executable not found.
>
> Please add the directory containing pg_config to the PATH
>
> or specify the full executable path with the option:
>
> python setup.py build_ext --pg-config /path/to/pg_config 
> build ...
>
> or with the pg_config option in 'setup.cfg'.
>
> 
> Command python setup.py egg_info failed with error code 1
> Storing complete log in C:\Documents and 
> Settings\anlopes\Application
> Data\pip\p
> ip.log
> [/quote]
>
> My question:
>
> How can I tell to "pip" where is my pg_config?
>
> Best Regards,
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/772ac1dc-e7c2-415c-bc6e-21a1e5b0ec4c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

inspectdb and postgresql schemas support - ticket #22673

[Fabio Caritas Barrionuevo da Luz]

*Django not provides way to use inspectdb in a postgresql schema with name 
different of "public"*

If you think this is an important feature and should be included in django, 
Please send your considerations and use cases to the topic:

https://groups.google.com/forum/#!topic/django-developers/lSHrDFZM4lQ

If you do not know the concept of postgresql schema, please read:

​http://www.postgresql.org/docs/9.3/static/ddl-schemas.html

This is an especially useful feature if you have to deal with the legacy 
database and perhaps also for multiple-tenant

This is a feature requested for 8 years[1][2].

I think now is a good time to include it (into Django 1.8) due to the new 
migration system (by Andrew Godwin [3]) and improved support for postgresql 
(by Marc Tamlyn[4])

I think this is also valid for Oracle and MSSQL

I opened the new ticket to handle this specific feature:

https://code.djangoproject.com/ticket/22673

Excuse me for english, I'm still learning.

[1] https://code.djangoproject.com/ticket/1051
[2] https://code.djangoproject.com/ticket/6148
[3] 
https://www.kickstarter.com/projects/andrewgodwin/schema-migrations-for-django
[4] 
https://www.kickstarter.com/projects/mjtamlyn/improved-postgresql-support-in-django


-- 
Fábio C. Barrionuevo da Luz
Acadêmico de Sistemas de Informação na Faculdade Católica do Tocantins - 
FACTO
Palmas - Tocantins - Brasil - América do Sul

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/40e995cb-fe97-44ae-a3b0-255df4942a49%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: FormWizard confirmation step logic and Allow dynamic form classes with WizardView

[Fabio Caritas Barrionuevo da Luz]

Apparently nobody is interested in WizardView and related features, much 
less with the proposed[1][3] improvements.


[1] https://code.djangoproject.com/ticket/21644
[2] https://code.djangoproject.com/ticket/21667
[3] https://github.com/thenewguy/django_formwizard_mixins
[4] https://github.com/thenewguy/django_formwizard_mixins/pull/2


Em quarta-feira, 7 de maio de 2014 17h43min57s UTC-3, Fabio Caritas 
Barrionuevo da Luz escreveu:
>
> Hello django users.
>
> About the ticket 21644[1] - "FormWizard needs confirmation step logic" 
> and ticket 21667[2] - "Allow dynamic form classes with WizardView"
>
> I would like your opinions about the proposed implementation by user 
> nickname123[3].
>
> Remember that an implementation is in very early stage.
>
> I added two more classes to at least to me, are useful
>
> see: https://github.com/thenewguy/django_formwizard_mixins/pull/2
>
>
> [1] https://code.djangoproject.com/ticket/21644
> [2] https://code.djangoproject.com/ticket/21667
> [3] https://github.com/thenewguy/django_formwizard_mixins
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/19369e7b-cddf-470d-b1c3-ee5a95273ae3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

FormWizard confirmation step logic and Allow dynamic form classes with WizardView

[Fabio Caritas Barrionuevo da Luz]

Hello django users.

About the ticket 21644[1] - "FormWizard needs confirmation step logic" 
and ticket 21667[2] - "Allow dynamic form classes with WizardView"

I would like your opinions about the proposed implementation by user 
nickname123[3].

Remember that an implementation is in very early stage.

I added two more classes to at least to me, are useful

see: https://github.com/thenewguy/django_formwizard_mixins/pull/2


[1] https://code.djangoproject.com/ticket/21644
[2] https://code.djangoproject.com/ticket/21667
[3] https://github.com/thenewguy/django_formwizard_mixins

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/72955561-b8a1-4e3e-b78d-a7f5975123cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: error in "makemessages" command on latest django version (1.8dev)

[Fabio Caritas Barrionuevo da Luz]

Sorry, I did not see there was already an open issue to handle this problem 

https://code.djangoproject.com/ticket/22328



Em quarta-feira, 30 de abril de 2014 18h52min41s UTC-3, Fabio Caritas 
Barrionuevo da Luz escreveu:
>
> hello, was testing in the latest version of Django[1] directly from Github 
> and am having this problem
>
>
> *optparse.OptionConflictError: option -e/--extension: conflicting option 
> string(s): -e*
>
> That would be a bug or am I doing something wrong
>
> In this link you can see all the steps I did to get this error
>
> https://asciinema.org/a/9213
>
>
> [1] 
> https://github.com/django/django/tree/8f6dff372b174e772920de6d82bd085f1a74eaf2
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/df90a6d3-a56a-4d61-8465-3c5ce6453065%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: error in "makemessages" command on latest django version (1.8dev)

[Fabio Caritas Barrionuevo da Luz]

it was really a bug


fixed in
https://github.com/django/django/commit/d1799233f46c39379fe429a4ece128d96b128006


Thanks

Em quarta-feira, 30 de abril de 2014 18h52min41s UTC-3, Fabio Caritas 
Barrionuevo da Luz escreveu:
>
> hello, was testing in the latest version of Django[1] directly from Github 
> and am having this problem
>
>
> *optparse.OptionConflictError: option -e/--extension: conflicting option 
> string(s): -e*
>
> That would be a bug or am I doing something wrong
>
> In this link you can see all the steps I did to get this error
>
> https://asciinema.org/a/9213
>
>
> [1] 
> https://github.com/django/django/tree/8f6dff372b174e772920de6d82bd085f1a74eaf2
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/1314b024-dec6-4de2-b2d1-38b6bd417ff1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

error in "makemessages" command on latest django version (1.8dev)

[Fabio Caritas Barrionuevo da Luz]

hello, was testing in the latest version of Django[1] directly from Github 
and am having this problem


*optparse.OptionConflictError: option -e/--extension: conflicting option 
string(s): -e*

That would be a bug or am I doing something wrong

In this link you can see all the steps I did to get this error

https://asciinema.org/a/9213


[1] 
https://github.com/django/django/tree/8f6dff372b174e772920de6d82bd085f1a74eaf2

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/afcfaea9-145c-4abd-8cde-99022da9c2db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: validate answers from a detail view

[Fabio Caritas Barrionuevo da Luz]

I think this would be facilitated if the FormWizard possessed a 
confirmation step. There is a ticket open on this exact feature

https://code.djangoproject.com/ticket/21644



Em sábado, 12 de abril de 2014 14h28min01s UTC-3, Brad Rice escreveu:
>
> I'm using a Class based Generic Detail View to show end users their 
> answers to previous mulit-page forms. How can I use that final detail view 
> to validate the answers? Should I not be using a Detail view or can I 
> somehow do a conditional get to the next view based upon those answers? 
> Right now I just have a link to the next page where they can submit all 
> their answers from the forms. If they haven't filled out a field, I want to 
> take them back to the form they need to go to to fix that. All it does on 
> that final page after the datail is set a true value in the db that they 
> are done updating their application form.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/fff50189-cf9f-4c8f-927d-575f9d38173a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Extended profile not being saved django-allauth

[Fabio Caritas Barrionuevo da Luz]

Voyager, Have you tried putting related_name in the Foreign Key?
 

> class UserProfile(models.Model): 
>  # This line is required. Links UserProfile to a User model instance. 
>  user = models.ForeignKey(User, unique=True, 
> *related_name='userprofile'*) 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/f78b228e-e759-441d-8005-862e21143fdc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

What do you think django-pony-forms

[Fabio Caritas Barrionuevo da Luz]

Hello everyone, 
I found django-pony-forms[1] recently. 
I found it very interesting proposal by adding the possibility of better 
defining how a form is rendered without having to use a templatetag or 
something, and also because it can make an individual customization of the 
form a little more "simple".

I have two questions: 

1) If I use django-pony-forms lose much performance, compared with the 
standard form. 

2) Is there another possible problem in addressing django-pony-forms used?



[1] https://github.com/mbraak/django_pony_forms
[2] http://django-pony-forms.readthedocs.org/en/latest/

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/5e5f8526-85ee-491a-b46f-de624dab157a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Using a paginator with two models in the same view

[Fabio Caritas Barrionuevo da Luz]

Please, if you can solve, create a post on a blog or a gist.github.com to 
resolution, and send to this topic. 
This can be useful for other people. XD

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/479bc862-74cb-4feb-91e9-1542278ddda4%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Django and default permissions?

[Fabio Caritas Barrionuevo da Luz]

Why of the core developers of Django does not include a "view only" 
permission by default?

Django creates by default has permissions add, change and delete, but does 
not include permission to view.

for example, the user can only view a form, but can not edit it, ie, the 
save will be disabled, and input fields generated by the form will be 
read-only

It seems that in django 1.7 will be simpler to modify[1] the default 
permissions

[1] https://docs.djangoproject.com/en/dev/releases/1.7/#models

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/9e8e73d7-0ee7-4730-b084-607b4c427d04%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Where exactly in the django source code, the default permissions are created?

[Fabio Caritas Barrionuevo da Luz]

Thanks Felipe, this is exactly what I was looking for.
My goal is to create a new default permission for all my models without 
having to declare it explicitly at all.

It would be something like:
permissions = (
 ('view_model_class_name', _ ('View model_class_name')),
)

I wonder why the developers chose to put the nucleus only the permissions 
add, change and delete and do not include default permission for display 
only.

-- 
Fábio C. Barrionuevo da Luz
Acadêmico de Sistemas de Informação na Faculdade Católica do Tocantins - 
FACTO
Palmas - Tocantins - Brasil - América do Sul

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/e1d3baf8-f17b-4c8f-bbfc-df4e7cfaa51e%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Where exactly in the django source code, the default permissions are created?

[Fabio Caritas Barrionuevo da Luz]

Have had looked Those classes, However, Still Could Not see Which line or 
lines in the source code the default permissions are created.

Is there anybody from the Core Developers that could explain where exactly 
they are created?


Sorry for English, I speak Portuguese, it was translated by Google 
Translator. 
Not the best thing in the world, but it works minimally, while also study 
the English language.


Fábio C. Barrionuevo da Luz
Acadêmico de Sistemas de Informação na Faculdade Católica do Tocantins - 
FACTO
Palmas - Tocantins - Brasil - América do Sul

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/eef0ff84-4cb3-4cf1-8896-868559c37a93%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Django Site/Docs/Tutorials translation

[Fabio Caritas Barrionuevo da Luz]

The translation project is hosted in Transifex.com [1][2]

[1] https://www.transifex.com/projects/p/django-docs/language/pt_BR/
[2] https://www.transifex.com/projects/p/django/language/pt_BR/members/

Em segunda-feira, 16 de dezembro de 2013 09h20min40s UTC-3, Lucas Infante 
escreveu:
>
> Hello guys!
>
> Sorry if my question is not being asked in the right place (I hope it is).
>
> I am interested in translating Django official site/docs/tutorials into 
> brazilian portuguese. Does anyone know who would I have to contact (to get 
> information on how to do this) or how could I be able to contribute to 
> Django Project in that way?
>
> Thanks in advance!
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/58850947-f8f6-4ede-9f3a-b8216c9a36cd%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Class-based app (like AdminSite) idea

[Fabio Caritas Barrionuevo da Luz]

Omoshiroi.

Register your app in django-packages[1]

[1] https://www.djangopackages.com

Em terça-feira, 17 de dezembro de 2013 13h44min11s UTC-3, Shinya Okano 
escreveu:
>
> I have implemented the idea to create a class-based applications (like 
> AdminSite).
>
> https://pypi.python.org/pypi/django-edamame
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/33d444b4-7918-484e-8f78-a3afe5d7b0ca%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Announce] Django Graphos - Django charting made *really* easy

[Fabio Caritas Barrionuevo da Luz]

These modifications made by "anentropic" are good too.


https://github.com/anentropic/django-graphos/tree/a7bae2c0e67d6f8deda1a75fac8c1574ab1b884c

 

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/ebc73d92-4b7e-4e25-8962-e7cd80ea9bf0%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

CookieWizardView / SessionWizardView + extra fields + dynamic steps + formset and/or inlineformset?

[Fabio Caritas Barrionuevo da Luz]

Hello everyone
 
Does anyone have any idea or any example to create a CookieWizard that the 
first step has some extra fields and the next steps based on the same extra 
fields, are created or updated automatically steps with formset or 
inlineformset?

I am a relatively new django User.

My current challenge:
I have the following class models to my Gas station manager django app: 
diagram:
https://dl.dropboxusercontent.com/u/66970738/arq_p_foruns/posto.png
models:
https://gist.github.com/luzfcb/7168187

I need to create a WizzardView Gas Station(Posto), and create related 
models , and some models related models related to Gas Station(Posto) .

In the initial step , the User shall inform the name of the Gas 
Station(Posto) and the number of pumps(Bomba) and tanks(Tanque) of Gas 
Station(Posto).

In the second step , based on number of pumps(Bomba) and tanks(Tanque) set 
in an initial step, the amount of displayed forms pumps(Bomba) and 
tanks(Tanque).

For each pump(Bomba), the User should inline insert nozzle(Bico).

I found a project to nested inlines formset. I made a fork and applied 
modifications, but still not good.
https://github.com/luzfcb/nested-formset.git

for me , the ideal solution would be that the django have its " simple " to 
do so , within and outside the django admin .

Maybe something like described in issue 9025 and comment of the silverfix

https://code.djangoproject.com/ticket/9025#comment:163

ps.: Sorry for my horrible English. I'm still learning. I am Brazilian. 
Short life to google translator, I hope I can survive without it as fast as 
possible. :-)

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/f4cf576b-a44e-49b9-8c61-1e49dee63f1c%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: How to insert a inline form inside a form wizard?

[Fabio Caritas Barrionuevo da Luz]

Hello Russel. 
First, sorry for reviving this topic.
Thanks for the comment on this topic, however, this matter is still not 
clear to me.
 
You will also create a blog post explaining the details of CookieWizardView 
/ SessionWizardView + formset and inlineformset?

I am a relatively new django User.

My current challenge:
I have the following class models to my Gas station manager django app: 
https://dl.dropboxusercontent.com/u/66970738/arq_p_foruns/posto.png

I need to create a WizzardView Gas Station(Posto), and create related 
models , and some models related models related to Gas Station(Posto) .

In the initial step , the User shall inform the name of the Gas 
Station(Posto) and the number of pumps(Bomba) and tanks(Tanque) of Gas 
Station(Posto).

In the second step , based on number of pumps(Bomba) and tanks(Tanque) set 
in an initial step, the amount of displayed forms pumps(Bomba) and 
tanks(Tanque).

For each pump(Bomba), the User should inline insert nozzle(Bico).

for me , the ideal solution would be that the django have its " simple " to 
do so , within and outside the django admin .

Maybe something like described in issue 9025 and comment of the silverfix

https://code.djangoproject.com/ticket/9025#comment:163

ps.: Sorry for my horrible English. I'm still learning. I am Brazilian. 
Short life to google translator, I hope I can survive without it as fast as 
possible. :-)

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/538e5dac-8845-4ed5-a3be-751135906c0c%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

status of multiple database schemas in Django

[Fabio Caritas Barrionuevo da Luz]

Hi, this[1][2] is the best solution to the problem of multiple database 
schemas?

Is there any idea when this feature will be supported by Django's ORM?


ps:
Sorry for my ugly english.

[1] https://code.djangoproject.com/ticket/6148
[2] 
https://github.com/cbmi/django/commit/4dccd11d927898523e4edfa0379b8b0530cd987f

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.