formencode-discuss — General discussion list

[FE-discuss] New releases?

[Neil M. <drn...@gm...>]

It's been a long time since the 2.0 alpha release, and there seems to
be no current ongoing development work, and there are a number of
issues and PR's piling up on the github repo.

How can we get this unstuck? Is there any way for the community to get
involved here? Would having more people review PRs and look at issues
be useful?

-- 
Neil Muller

[FE-discuss] Requesting formencode == 1.3 on anaconda

[Umar P. <uma...@gm...>]

Hi,

I was asking if the formencode version 1.3 can be package on
https://anaconda.org it will helpful to me and my GSoC 2018 project, if
there was no one who can do it i will like to do build and package it and
continue to maintain it for new updates.



thank you

[FE-discuss] formencode.org domain name is not resolving

[Chris L. <ch...@ka...>]

Hi Everyone,

It looks like the registration has lapsed on the formencode.org domain name
but is still available for Ian to renew. I've sent an email to Ian to try
and get it sorted out.

-Chris

-- 
Christopher Lambacher
ch...@ka...

[FE-discuss] Relicense status update

[Chris L. <ch...@ka...>]

Hello everyone,

We're down to 4 contributors that I haven't heard from. I've found new ways
to contact each of the missing contributors today, so hopefully I'll hear
from them soon. I've created a pull request which includes the updated
LICENSE.txt file and new CONTRIBUTORS.txt file.

Pull request here:
https://github.com/formencode/formencode/pull/99

After that is merged then new contributors will be required to add
themselves to the CONTRIBUTORS.txt file.

-Chris

-- 
Christopher Lambacher
ch...@ka...

[FE-discuss] License change status update

[Chris L. <ch...@ka...>]

Hello Everyone,

I have heard from 47 of the contributors and all the responses have been in
agreement with changing the license. Here is the list of people I have not
heard back from yet:

68 S    test ? http://sourceforge.net/u/test/profile/
24 E    W. Mark Kubacki https://github.com/wmark
 6 T    Patrick Hunt, phunt, https://github.com/phunt,
https://twitter.com/phunt
 6 T    Chris George: https://github.com/chrisgeo
 5 E    jab Jeff Breidenbach, jab.org
 2 E    Bo Du: https://www.linkedin.com/pub/bo-du-pharmd/71/293/76b
 1 E    Ryan P. Kelly: https://github.com/f0rk
 1 E    Remco Verhoef: https://plus.google.com/u/0/+RemcoVerhoef/posts
 1 E    Oleg Broytman: http://phdru.name/
 1 E    Nina Plakalovic: https://plus.google.com/109547421364597999170/posts
 1 E    Martin Martimeo: https://plus.google.com/102119635750966644221/posts
 1 E    Ira Lun (tried 2 email addresses)
 1 B    silver_: https://bitbucket.org/silver_/

The first column is how many commits are attributed to that person, the
second column is how I attempted to contact them (S: Sourceforge Send
message button, T: twitter mention, B: bitbucket message, E: direct email).

If anyone knows of a more reliable way to reach these people I would very
much appreciate it.

Thanks,
Chris

-- 
Christopher Lambacher
ch...@ka...

Re: [FE-discuss] Changing the license to MIT

[David S. <ds...@ds...>]

I don't have any problem with this.

On Wed, Sep 9, 2015 at 10:03 AM, Chris Lambacher <ch...@ka...>
wrote:

> Hi everyone,
>
> I'd like to try and get sign off from all contributors to change the
> license from PSF, which is what is in setup.py to MIT because the PSF
> license isn't really suitable for anything but Python itself. If you have
> ever contributed to formencode could you please email me with your consent
> for the license change. I'll try to figure out how to contact anyone who
> was ever a committer that hasn't contacted me after 2 weeks.
>
> Thanks for your help,
> Chris
>
> --
> Christopher Lambacher
> ch...@ka...
>
>
> ------------------------------------------------------------------------------
> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> Get real-time metrics from all of your servers, apps and tools
> in one place.
> SourceForge users - Click here to start your Free Trial of Datadog now!
> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
> _______________________________________________
> FormEncode-discuss mailing list
> For...@li...
> https://lists.sourceforge.net/lists/listinfo/formencode-discuss
>
>


-- 
David
blog: http://www.traceback.org
twitter: http://twitter.com/dstanek
www: http://dstanek.com

[FE-discuss] Changing the license to MIT

[Chris L. <ch...@ka...>]

Hi everyone,

I'd like to try and get sign off from all contributors to change the
license from PSF, which is what is in setup.py to MIT because the PSF
license isn't really suitable for anything but Python itself. If you have
ever contributed to formencode could you please email me with your consent
for the license change. I'll try to figure out how to contact anyone who
was ever a committer that hasn't contacted me after 2 weeks.

Thanks for your help,
Chris

-- 
Christopher Lambacher
ch...@ka...

Re: [FE-discuss] Formencode 1.3.0 Released

[Christoph Z. <ci...@on...>]

Am 07.02.2015 um 19:49 schrieb Chris Lambacher:
> After a very long incubation period. I have released FormEncode 1.3.0
> on pypi. Lots of features, documentation fixes and bug fixes went
> into this release.

Great - thanks a lot for working on this.

-- Christoph

[FE-discuss] Formencode 1.3.0 Released

[Chris L. <ch...@ka...>]

Hello Everyone,

After a very long incubation period. I have released FormEncode 1.3.0 on
pypi. Lots of features, documentation fixes and bug fixes went into this
release. Thanks to all who contributed.

-Chris

-- 
Christopher Lambacher
ch...@ka...

Re: [FE-discuss] Status of formencode 1.3 ?

[Mike O. <slu...@gm...>]

On Thu, Dec 11, 2014 at 10:15 PM, Neil Muller
<drn...@gm...> wrote:
> On 12 December 2014 at 01:16, Chris Lambacher <ch...@ka...> wrote:
>> The major blocker is my time. I think there are 2 or 3 pull requests that
>> should be merged. Is anyone using the 1.3 alpha yet? I am not sure I have
>> had much feedback about it but maybe that is an indication of it working.
>
> While it's purely ancedotal, I've used 1.3 without any issues with the
> projects that interest me, so it's working fine for at least my use
> cases.

I used it a couple weeks ago and didn't have any problem.

Re: [FE-discuss] Status of formencode 1.3 ?

[Neil M. <drn...@gm...>]

On 12 December 2014 at 01:16, Chris Lambacher <ch...@ka...> wrote:
> The major blocker is my time. I think there are 2 or 3 pull requests that
> should be merged. Is anyone using the 1.3 alpha yet? I am not sure I have
> had much feedback about it but maybe that is an indication of it working.

While it's purely ancedotal, I've used 1.3 without any issues with the
projects that interest me, so it's working fine for at least my use
cases.

Re: [FE-discuss] Status of formencode 1.3 ?

[Chris L. <ch...@ka...>]

The major blocker is my time. I think there are 2 or 3 pull requests that
should be merged. Is anyone using the 1.3 alpha yet? I am not sure I have
had much feedback about it but maybe that is an indication of it working.
Probably PRs #72 and #61 should be merged and a release made. Then we can
start working on merging some of the other PRs.

-Chris

On Wed, Dec 10, 2014 at 2:49 AM, Neil Muller <
drn...@gm...> wrote:

> It's been quite a while since the 1.3 alpha was released, so what
> issues are blocking a final 1.3 release, and what would be the best
> way to help make it happen?
>
> Looking at the issues and pull requests on github, nothing stands out
> as a major obstacle, so it's not clear to me what the blockers are.
>
> --
> Neil Muller
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
>
> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
> _______________________________________________
> FormEncode-discuss mailing list
> For...@li...
> https://lists.sourceforge.net/lists/listinfo/formencode-discuss
>



-- 
Christopher Lambacher
ch...@ka...

[FE-discuss] Status of formencode 1.3 ?

[Neil M. <drn...@gm...>]

It's been quite a while since the 1.3 alpha was released, so what
issues are blocking a final 1.3 release, and what would be the best
way to help make it happen?

Looking at the issues and pull requests on github, nothing stands out
as a major obstacle, so it's not clear to me what the blockers are.

-- 
Neil Muller

[FE-discuss] validators.RequireIfMatching missing from pypi package

[Egidijus <egi...@de...>]

Hello,

I'm not sure if it's the right place, but I just want to inform - pypi
package (https://pypi.python.org/pypi/FormEncode/1.3.0a1) differs from
one in github repository (https://github.com/formencode/formencode).
At least validators.RequireIfMatching class is missing in pypi package.

[FE-discuss] ★ Formencode Discuss, Richie left a message for you

[Richie <nor...@ba...>]

Richie left a message for you

Its sender and content will be shown only to you and you can delete it at any time. You can instantly reply to it, using the message exchange system. To find out what was written to you, just follow this link:
http://eu1.badoo.com/richie.ward/in/BgyYY.nE-SQ/?lang_id=3&g=57-0-4&m=63&mid=53dd3a81000000000003004d03eda78100f0ed7b0074


If clicking the links in this message does not work,
copy and paste them into the address bar of your browser.


This email is a part of delivering a message sent by Richie on the system. If you received this email by mistake, please just ignore it. After a short time the message will be removed from the system.


Have fun!
The Badoo Team

You have received this email from Badoo Trading Limited (postal address below).
If you do not wish to receive further email communications from Badoo click here to opt out: https://eu1.badoo.com/impersonation.phtml?lang_id=3&email=formencode-discuss%40lists.sf.net&block_code=cf4a41&m=63&mid=53dd3a81000000000003004d03eda78100f0ed7b0074&g=0-0-4.
Badoo Trading Limited is a limited company registered in England and Wales
under CRN 7540255 with its registered office at Media Village, 131 - 151 Great Titchfield Street, London, W1W 5BB.

[FE-discuss] Can formencode raise invalid for some valid value:

[deepak v. <yes...@gm...>]

Hi all,

The subject of this email may not seems obvious to some people but I could
resist myself from being asked this question. Please accept my apologies:

My Question is:

Is there any any support to raise Invalid exception for some values when
validation them ?


For e.g.
Suppose I have to validate email using email validatior.
Then want to raise Invalid exception to some emails like:
no...@ex...or some emails like these.


example:
*    from formencode import validators*
*    from formencode.api import Invalid*
*    invalid_emails = ['no...@ex... <no...@ex...>',
'bl...@gm... <bl...@gm...>']*
*    email = 'no...@ex... <no...@ex...>'*
*    try:*
*        email_validator = validators.Email(invalidate=invalid_emails)*
*        email_validator.to_python(email)*
*    except Invalid, e:*
*        logger.log("An Invalid Exception Occurred", e)*
*        raise e*

In the above code, this should raise Invalid exception the we try to
validate invalid_emails.
Do we have support for this in future release.

In order to achieve this I have to do something like this:
*    from formencode import validators*
*    from formencode.api import Invalid*
*    invalid_emails = ['no...@ex... <no...@ex...>',
'bl...@gm... <bl...@gm...>']*
*    email = 'no...@ex... <no...@ex...>'*
*    try:*
*        if email in invalid_emails:*
*             raise Invalid*
*        email_validator = validators.Email(invalidate=invalid_emails)*
*        email_validator.to_python(email)*
*    except Invalid, e:*
*        logger.log("An Invalid Exception Occurred", e)*
*        raise e*

But I have to do this for all validators.

-- 


Thanks & Regards

Deepak Verma

Re: [FE-discuss] Testing FormEncode 1.3.0a1

[Chris L. <ch...@ka...>]

On Wed, Dec 11, 2013 at 12:18 PM, Sebastien Douche <sd...@gm...>wrote:

> On Wed, Dec 11, 2013 at 6:13 PM, Chris Lambacher <ch...@ka...>
> wrote:
> >> Exact, we use iterator. It's work now with FormEncode 1.2.6. I will
> >> try later with 1.3.0a1.  Thanks Chris.
> >
> > Was  it a custom validator or are we missing a built in one that should
> > accept an iterator that does not have the flag set?
>
> We use the Constant Validator on an iterator value.


I think it is reasonable that Constant Validator should accept an iterator
by default. I'll make that change.

-Chris

-- 
Christopher Lambacher
ch...@ka...

Re: [FE-discuss] Testing FormEncode 1.3.0a1

[Sebastien D. <sd...@gm...>]

On Wed, Dec 11, 2013 at 6:04 PM, Sebastien Douche <sd...@gm...> wrote:
> On Thu, Dec 5, 2013 at 6:12 PM, Chris Lambacher <ch...@ka...> wrote:
>>> Right, same broken tests with the 1.2.5.
>>
>> That narrows things down. Do you have a custom validator that expects a
>> sequence that doesn't derive from a formencode validator that expects as
>> sequence (list, dict, tuple, etc)? If so you will need to add an
>> accept_iterator = True property to your validator. You can do a quick test
>> for that by adding it to the instantiation args somewhere you use the
>> validator.
>
> Exact, we use iterator. It's work now with FormEncode 1.2.6. I will
> try later with 1.3.0a1.  Thanks Chris.

Tests pass with 1.3.0a1 :).


-- 
Sebastien Douche <sd...@gm...>
Twitter: @sdouche / G+: +sdouche

Re: [FE-discuss] Testing FormEncode 1.3.0a1

[Sebastien D. <sd...@gm...>]

On Wed, Dec 11, 2013 at 6:13 PM, Chris Lambacher <ch...@ka...> wrote:
>> Exact, we use iterator. It's work now with FormEncode 1.2.6. I will
>> try later with 1.3.0a1.  Thanks Chris.
>
> Was  it a custom validator or are we missing a built in one that should
> accept an iterator that does not have the flag set?

We use the Constant Validator on an iterator value.

-- 
Sebastien Douche <sd...@gm...>
Twitter: @sdouche / G+: +sdouche

Re: [FE-discuss] Testing FormEncode 1.3.0a1

[Chris L. <ch...@ka...>]

On Wed, Dec 11, 2013 at 12:04 PM, Sebastien Douche <sd...@gm...>wrote:

>
> Exact, we use iterator. It's work now with FormEncode 1.2.6. I will
> try later with 1.3.0a1.  Thanks Chris.


Was  it a custom validator or are we missing a built in one that should
accept an iterator that does not have the flag set?

Thanks,
Chris

-- 
Christopher Lambacher
ch...@ka...

Re: [FE-discuss] Testing FormEncode 1.3.0a1

[Sebastien D. <sd...@gm...>]

On Thu, Dec 5, 2013 at 6:12 PM, Chris Lambacher <ch...@ka...> wrote:
>> Right, same broken tests with the 1.2.5.
>
> That narrows things down. Do you have a custom validator that expects a
> sequence that doesn't derive from a formencode validator that expects as
> sequence (list, dict, tuple, etc)? If so you will need to add an
> accept_iterator = True property to your validator. You can do a quick test
> for that by adding it to the instantiation args somewhere you use the
> validator.

Exact, we use iterator. It's work now with FormEncode 1.2.6. I will
try later with 1.3.0a1.  Thanks Chris.


-- 
Sebastien Douche <sd...@gm...>
Twitter: @sdouche / G+: +sdouche

Re: [FE-discuss] Testing FormEncode 1.3.0a1

[Chris L. <ch...@ka...>]

Hi Sebastien,

>
> > Also the 1.2.5
> > release had some backwards incompatible changes that might cause a
> problem
> > if you have custom validators that expect sequences to be passed to them
> > from a Schema. Details can be found here:
> > http://www.formencode.org/en/latest/whatsnew-1.2.5.html.
>
> Right, same broken tests with the 1.2.5.


That narrows things down. Do you have a custom validator that expects a
sequence that doesn't derive from a formencode validator that expects as
sequence (list, dict, tuple, etc)? If so you will need to add
an accept_iterator = True property to your validator. You can do a quick
test for that by adding it to the instantiation args somewhere you use the
validator.

-Chris

-- 
Christopher Lambacher
ch...@ka...

Re: [FE-discuss] Testing FormEncode 1.3.0a1

[Sebastien D. <sd...@gm...>]

On Thu, Dec 5, 2013 at 5:37 PM, Chris Lambacher <ch...@ka...> wrote:
> Hi Sebastien,

Hi Chris

> Also the 1.2.5
> release had some backwards incompatible changes that might cause a problem
> if you have custom validators that expect sequences to be passed to them
> from a Schema. Details can be found here:
> http://www.formencode.org/en/latest/whatsnew-1.2.5.html.

Right, same broken tests with the 1.2.5.




-- 
Sebastien Douche <sd...@gm...>
Twitter: @sdouche / G+: +sdouche

Re: [FE-discuss] Testing FormEncode 1.3.0a1

[Chris L. <ch...@ka...>]

Hi Sebastien,

1.3 is mostly compatible but there are a few changes that are backward in
compatible. They should all be listed here
http://www.formencode.org/en/latest/whatsnew-1.3.html but I readily admit
that one of the things holding back a full 1.3 release is documentation.
There *may* be something that is inadvertently backwards incompatible and
if you find something like that please submit a bug to
https://github.com/formencode/formencode/issues?state=open . Also the 1.2.5
release had some backwards incompatible changes that might cause a problem
if you have custom validators that expect sequences to be passed to them
from a Schema. Details can be found here:
http://www.formencode.org/en/latest/whatsnew-1.2.5.html.

-Chris


On Thu, Dec 5, 2013 at 11:27 AM, Sebastien Douche <sd...@gm...> wrote:

> Hi,
> i'm testing the new version (we are porting our 120KSLOC app on Python
> 3) and I have a question about it, because some tests are broken. Is
> the new version strictly compatible with the 1.2.4 version?
>
> --
> Sebastien Douche <sd...@gm...>
> Twitter: @sdouche / G+: +sdouche
>
>
> ------------------------------------------------------------------------------
> Sponsored by Intel(R) XDK
> Develop, test and display web and hybrid apps with a single code base.
> Download it for free now!
>
> http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
> _______________________________________________
> FormEncode-discuss mailing list
> For...@li...
> https://lists.sourceforge.net/lists/listinfo/formencode-discuss
>



-- 
Christopher Lambacher
ch...@ka...

[FE-discuss] Testing FormEncode 1.3.0a1

[Sebastien D. <sd...@gm...>]

Hi,
i'm testing the new version (we are porting our 120KSLOC app on Python
3) and I have a question about it, because some tests are broken. Is
the new version strictly compatible with the 1.2.4 version?

-- 
Sebastien Douche <sd...@gm...>
Twitter: @sdouche / G+: +sdouche